From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Longpeng(Mike)" <longpeng2@huawei.com>
Cc: stefanha@redhat.com, jasowang@redhat.com, sgarzare@redhat.com,
cohuck@redhat.com, pbonzini@redhat.com, arei.gonglei@huawei.com,
yechuan@huawei.com, huangzhichao@huawei.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v5 2/4] virtio: get class_id and pci device id by the virtio id
Date: Thu, 12 May 2022 02:56:05 -0400 [thread overview]
Message-ID: <20220512025113-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220512062103.1875-3-longpeng2@huawei.com>
On Thu, May 12, 2022 at 02:21:01PM +0800, Longpeng(Mike) wrote:
> From: Longpeng <longpeng2@huawei.com>
>
> Add helpers to get the "Transitional PCI Device ID" and "class_id"
> of the device specified by the "Virtio Device ID".
>
> These helpers will be used to build the generic vDPA device later.
>
> Signed-off-by: Longpeng <longpeng2@huawei.com>
Except, the IDs in the current header a broken. I just fixed them
and they will be hopefully OK in the next version.
> ---
> hw/virtio/virtio-pci.c | 77 ++++++++++++++++++++++++++++++++++++++++++
> hw/virtio/virtio-pci.h | 5 +++
> 2 files changed, 82 insertions(+)
>
> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> index 7cf1231c1c..fdfa205cee 100644
> --- a/hw/virtio/virtio-pci.c
> +++ b/hw/virtio/virtio-pci.c
> @@ -19,6 +19,7 @@
>
> #include "exec/memop.h"
> #include "standard-headers/linux/virtio_pci.h"
> +#include "standard-headers/linux/virtio_ids.h"
> #include "hw/boards.h"
> #include "hw/virtio/virtio.h"
> #include "migration/qemu-file-types.h"
> @@ -212,6 +213,79 @@ static int virtio_pci_load_queue(DeviceState *d, int n, QEMUFile *f)
> return 0;
> }
>
> +typedef struct VirtIOPCIIDInfo {
> + /* virtio id */
> + uint16_t vdev_id;
> + /* pci device id for the transitional device */
> + uint16_t trans_devid;
> + uint16_t class_id;
> +} VirtIOPCIIDInfo;
> +
> +#define VIRTIO_TRANS_DEV_ID_INFO(name, class) \
> + { \
> + .vdev_id = VIRTIO_ID_##name, \
> + .trans_devid = PCI_DEVICE_ID_VIRTIO_##name, \
> + .class_id = class, \
> + }
> +
> +#define VIRTIO_MODERN_DEV_ID_NFO(name, class) \
> + { \
> + .vdev_id = VIRTIO_ID_##name, \
> + .class_id = class, \
> + }
> +
No, I think I liked the original approach in the RFC better, even though
it duplicates a tiny bit of code.
This trick does not save a lot of typing and obscures the ID
use in case it's wrong (as was the case just recently).
> +static const VirtIOPCIIDInfo virtio_pci_id_info[] = {
> + /* Non-transitional devices */
> + VIRTIO_MODERN_DEV_ID_NFO(CRYPTO, PCI_CLASS_OTHERS),
> + VIRTIO_MODERN_DEV_ID_NFO(FS, PCI_CLASS_STORAGE_OTHER),
> + /* Transitional devices */
> + VIRTIO_TRANS_DEV_ID_INFO(NET, PCI_CLASS_NETWORK_ETHERNET),
> + VIRTIO_TRANS_DEV_ID_INFO(BLOCK, PCI_CLASS_STORAGE_SCSI),
> + VIRTIO_TRANS_DEV_ID_INFO(CONSOLE, PCI_CLASS_COMMUNICATION_OTHER),
> + VIRTIO_TRANS_DEV_ID_INFO(SCSI, PCI_CLASS_STORAGE_SCSI),
> + VIRTIO_TRANS_DEV_ID_INFO(9P, PCI_BASE_CLASS_NETWORK),
> + VIRTIO_TRANS_DEV_ID_INFO(BALLOON, PCI_CLASS_OTHERS),
> + VIRTIO_TRANS_DEV_ID_INFO(RNG, PCI_CLASS_OTHERS),
> +};
> +
> +static const VirtIOPCIIDInfo *virtio_pci_get_id_info(uint16_t vdev_id)
> +{
> + const VirtIOPCIIDInfo *info = NULL;
> + int i;
> +
> + for (i = 0; i < ARRAY_SIZE(virtio_pci_id_info); i++) {
> + if (virtio_pci_id_info[i].vdev_id == vdev_id) {
> + info = &virtio_pci_id_info[i];
> + break;
> + }
> + }
> +
> + if (!info) {
> + /* The device id is invalid or not added to the id_info yet. */
> + error_report("Invalid virtio device(id %u)", vdev_id);
> + abort();
> + }
> +
> + return info;
> +}
> +
> +/*
> + * Get the Transitional Device ID for the specific device, return
> + * zero if the device is non-transitional.
> + */
> +uint16_t virtio_pci_get_trans_devid(uint16_t device_id)
> +{
> + return virtio_pci_get_id_info(device_id)->trans_devid;
> +}
> +
> +/*
> + * Get the Class ID for the specific device.
> + */
> +uint16_t virtio_pci_get_class_id(uint16_t device_id)
> +{
> + return virtio_pci_get_id_info(device_id)->class_id;
> +}
> +
> static bool virtio_pci_ioeventfd_enabled(DeviceState *d)
> {
> VirtIOPCIProxy *proxy = to_virtio_pci_proxy(d);
> @@ -1675,6 +1749,9 @@ static void virtio_pci_device_plugged(DeviceState *d, Error **errp)
> * is set to PCI_SUBVENDOR_ID_REDHAT_QUMRANET by default.
> */
> pci_set_word(config + PCI_SUBSYSTEM_ID, virtio_bus_get_vdev_id(bus));
> + if (proxy->trans_devid) {
> + pci_config_set_device_id(config, proxy->trans_devid);
> + }
> } else {
> /* pure virtio-1.0 */
> pci_set_word(config + PCI_VENDOR_ID,
> diff --git a/hw/virtio/virtio-pci.h b/hw/virtio/virtio-pci.h
> index 2446dcd9ae..f08665cd1b 100644
> --- a/hw/virtio/virtio-pci.h
> +++ b/hw/virtio/virtio-pci.h
> @@ -146,6 +146,8 @@ struct VirtIOPCIProxy {
> bool disable_modern;
> bool ignore_backend_features;
> OnOffAuto disable_legacy;
> + /* Transitional device id */
> + uint16_t trans_devid;
> uint32_t class_code;
> uint32_t nvectors;
> uint32_t dfselect;
> @@ -158,6 +160,9 @@ struct VirtIOPCIProxy {
> VirtioBusState bus;
> };
>
> +uint16_t virtio_pci_get_trans_devid(uint16_t device_id);
> +uint16_t virtio_pci_get_class_id(uint16_t device_id);
> +
> static inline bool virtio_pci_modern(VirtIOPCIProxy *proxy)
> {
> return !proxy->disable_modern;
> --
> 2.23.0
next prev parent reply other threads:[~2022-05-12 6:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 6:20 [PATCH v5 0/4] add generic vDPA device support Longpeng(Mike) via
2022-05-12 6:21 ` [PATCH v5 1/4] linux-headers: Update headers to Linux 5.18-rc6 Longpeng(Mike) via
2022-05-12 6:21 ` [PATCH v5 2/4] virtio: get class_id and pci device id by the virtio id Longpeng(Mike) via
2022-05-12 6:56 ` Michael S. Tsirkin [this message]
2022-05-13 3:17 ` longpeng2--- via
2022-05-12 6:21 ` [PATCH v5 3/4] vdpa: add vdpa-dev support Longpeng(Mike) via
2022-05-12 14:36 ` Stefano Garzarella
2022-05-13 2:17 ` longpeng2--- via
2022-05-13 6:34 ` Stefano Garzarella
2022-05-12 6:21 ` [PATCH v5 4/4] vdpa: add vdpa-dev-pci support Longpeng(Mike) via
2022-05-12 14:49 ` Stefano Garzarella
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=20220512025113-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=cohuck@redhat.com \
--cc=huangzhichao@huawei.com \
--cc=jasowang@redhat.com \
--cc=longpeng2@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=yechuan@huawei.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).