qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: John Levon <john.levon@nutanix.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, Thanos Makatos <thanos.makatos@nutanix.com>
Subject: Re: [PATCH] hw/vfio-user: add x-pci-class-code
Date: Mon, 8 Sep 2025 16:15:52 +0200	[thread overview]
Message-ID: <60bb61bc-13bd-461b-a368-aa6753c15edf@redhat.com> (raw)
In-Reply-To: <20250827190810.1645340-1-john.levon@nutanix.com>

On 8/27/25 21:08, John Levon wrote:
> This new option was not added to vfio_user_pci_dev_properties, which
> caused an incorrect class code for vfio-user devices.
> 
> Fixes: a59d06305fff ("vfio/pci: Introduce x-pci-class-code option")
> Signed-off-by: John Levon <john.levon@nutanix.com>
> ---
>   hw/vfio-user/pci.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/hw/vfio-user/pci.c b/hw/vfio-user/pci.c
> index be71c77729..dfaa89498d 100644
> --- a/hw/vfio-user/pci.c
> +++ b/hw/vfio-user/pci.c
> @@ -406,6 +406,8 @@ static const Property vfio_user_pci_dev_properties[] = {
>                          sub_vendor_id, PCI_ANY_ID),
>       DEFINE_PROP_UINT32("x-pci-sub-device-id", VFIOPCIDevice,
>                          sub_device_id, PCI_ANY_ID),
> +    DEFINE_PROP_UINT32("x-pci-class-code", VFIOPCIDevice,
> +                       class_code, PCI_ANY_ID),
>       DEFINE_PROP_BOOL("x-send-queued", VFIOUserPCIDevice, send_queued, false),
>       DEFINE_PROP_UINT32("x-msg-timeout", VFIOUserPCIDevice, wait_time, 5000),
>       DEFINE_PROP_BOOL("x-no-posted-writes", VFIOUserPCIDevice, no_post, false),


Applied to vfio-next.

Thanks,

C.




      parent reply	other threads:[~2025-09-08 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 19:08 [PATCH] hw/vfio-user: add x-pci-class-code John Levon
2025-09-01  7:04 ` Cédric Le Goater
2025-09-08 14:15 ` Cédric Le Goater [this message]

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=60bb61bc-13bd-461b-a368-aa6753c15edf@redhat.com \
    --to=clg@redhat.com \
    --cc=john.levon@nutanix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=thanos.makatos@nutanix.com \
    /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).