qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 1/7] tests: qgraph API for the qtest driver fram


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH 1/7] tests: qgraph API for the qtest driver framework
Date: Wed, 11 Jul 2018 16:58:41 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

On 11/07/2018 16:28, Stefan Hajnoczi wrote:
>> + * build_driver_cmd_line(): builds the command line for the driver
>> + * @node. The node name must be a valid qemu identifier, since it
>> + * will be used to build the command line.
>> + *
>> + * It is also possible to pass an optional @args that will be
>> + * concatenated to the command line.
>> + *
>> + * For drivers, prepend -device to the driver name.
>> + */
>> +static void build_driver_cmd_line(QOSGraphNode *node, const char *args)
> Why is this called "driver" instead of "device"?
> 

It's the command line that is needed for the driver to work; it can
include also e.g. a -netdev or -blockdev option, though the most common
case is to have just -device.

>> + *
>> + * QOSGraphObject also provides a destructor, used to deallocate the
>> + * after the test has been executed.
>> + */
>> +struct QOSGraphObject {
>> +    /* for produces, returns void * */
>> +    QOSGetDriver get_driver;
> 
> Unused?
> 
>> +    /* for contains, returns a QOSGraphObject * */
>> +    QOSGetDevice get_device;
> 
> Unused?

What is unused?

Thanks,

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]