qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Tomáš Golembiovský" <tgolembi@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qga: add command guest-get-devices for reporting VirtIO devices
Date: Fri, 30 Aug 2019 10:37:30 +0200	[thread overview]
Message-ID: <20190830103730.37ab6833@fiorina> (raw)
In-Reply-To: <f30adddb-311b-acff-e6ec-a5418f70158f@redhat.com>

On Thu, 29 Aug 2019 11:13:53 -0500
Eric Blake <eblake@redhat.com> wrote:

> On 8/29/19 11:03 AM, Tomáš Golembiovský wrote:
> > Add command for reporting devices on Windows guest. The intent is not so
> > much to report the devices but more importantly the driver (and its
> > version) that is assigned to the device.
> > 
> > Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>  
> 
> > +++ b/qga/qapi-schema.json
> > @@ -1242,3 +1242,35 @@
> >  ##
> >  { 'command': 'guest-get-osinfo',
> >    'returns': 'GuestOSInfo' }
> > +
> > +##
> > +# @GuestDeviceInfo:
> > +#
> > +# @vendor-id: vendor ID as hexadecimal string in uper case without 0x prefix
> > +# @device-id: device ID as hexadecimal string in uper case without 0x prefix  
> 
> s/uper/upper/ twice

duh

> 
> Should these be ints instead of strings (yes, it means they would be
> decimal over the wire, which is not the typical representation)?

Yes, I'm also indecisive in this point too. Although I sort of planned
to switch it to `int` in v2 anyway.

> 
> > +# @driver-name: name of the associated driver
> > +# @driver-date: driver release date in format MM/DD/YY  
> 
> Why US-centric?  Better would be something like ISO, YYYY-MM-DD

I admit ISO form would be more fool proof (and I would like it better
too), but this is to stay consistent with format used in Windows
drivers[1].

> 
> > +# @driver-version: driver version
> > +#
> > +# Since: 4.1.1  
> 
> 4.2.  We don't tend to add features on stable backport branches (as this
> missed 4.1.0, we're unlikely to add it for 4.1.1).

Ah, ok.

Thanks,

    Tomas

[1] https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-driverver-directive

-- 
Tomáš Golembiovský <tgolembi@redhat.com>


  reply	other threads:[~2019-08-30  8:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 16:03 [Qemu-devel] [PATCH] qga: add command guest-get-devices for reporting VirtIO devices Tomáš Golembiovský
2019-08-29 16:13 ` Eric Blake
2019-08-30  8:37   ` Tomáš Golembiovský [this message]
2019-09-16  9:07 ` Tomáš Golembiovský
2019-09-16 12:31 ` Marc-André Lureau
2019-09-18 11:23   ` Tomáš Golembiovský
2019-09-18 12:01     ` Marc-André Lureau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190830103730.37ab6833@fiorina \
    --to=tgolembi@redhat.com \
    --cc=eblake@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).