From: "Cédric Le Goater" <clg@redhat.com>
To: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"Sun, Yi Y" <yi.y.sun@intel.com>,
"Peng, Chao P" <chao.p.peng@intel.com>
Subject: Re: [PATCH 1/4] vfio/pci: Move VFIODevice initializations in vfio_instance_init
Date: Thu, 16 Nov 2023 08:28:59 +0100 [thread overview]
Message-ID: <2da90861-3f10-47cf-9f6e-39d52b8c929f@redhat.com> (raw)
In-Reply-To: <SJ0PR11MB6744ED3C5F3F828BECBDC6FD92B0A@SJ0PR11MB6744.namprd11.prod.outlook.com>
On 11/16/23 03:16, Duan, Zhenzhong wrote:
>
>
>> -----Original Message-----
>> From: Cédric Le Goater <clg@redhat.com>
>> Sent: Wednesday, November 15, 2023 9:12 PM
>> Subject: Re: [PATCH 1/4] vfio/pci: Move VFIODevice initializations in
>> vfio_instance_init
>>
>> On 11/15/23 09:32, Zhenzhong Duan wrote:
>>> Some of the VFIODevice initializations is in vfio_realize,
>>> move all of them in vfio_instance_init.
>>>
>>> No functional change intended.
>>>
>>> Suggested-by: Cédric Le Goater <clg@redhat.com>
>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> ---
>>> hw/vfio/pci.c | 10 ++++++----
>>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
>>> index b23b492cce..5a2b7a2d6b 100644
>>> --- a/hw/vfio/pci.c
>>> +++ b/hw/vfio/pci.c
>>> @@ -2969,9 +2969,6 @@ static void vfio_realize(PCIDevice *pdev, Error **errp)
>>> if (vfio_device_get_name(vbasedev, errp)) {
>>> return;
>>> }
>>> - vbasedev->ops = &vfio_pci_ops;
>>> - vbasedev->type = VFIO_DEVICE_TYPE_PCI;
>>> - vbasedev->dev = DEVICE(vdev);
>>>
>>> /*
>>> * Mediated devices *might* operate compatibly with discarding of RAM,
>> but
>>> @@ -3320,6 +3317,7 @@ static void vfio_instance_init(Object *obj)
>>> {
>>> PCIDevice *pci_dev = PCI_DEVICE(obj);
>>> VFIOPCIDevice *vdev = VFIO_PCI(obj);
>>> + VFIODevice *vbasedev = &vdev->vbasedev;
>>>
>>> device_add_bootindex_property(obj, &vdev->bootindex,
>>> "bootindex", NULL,
>>> @@ -3328,7 +3326,11 @@ static void vfio_instance_init(Object *obj)
>>> vdev->host.bus = ~0U;
>>> vdev->host.slot = ~0U;
>>> vdev->host.function = ~0U;
>>> - vdev->vbasedev.fd = -1;
>>> +
>>> + vbasedev->type = VFIO_DEVICE_TYPE_PCI;
>>> + vbasedev->ops = &vfio_pci_ops;
>>> + vbasedev->dev = DEVICE(vdev);
>>> + vbasedev->fd = -1;
>>
>> VFIODevice is similar to a base QOM parent. Could we introduce an helper
>> routine like we did with vfio_device_set_fd() ?
>
> Sure, will do.
Since this series is reviewed, could you please consolidate with an extra
patch on top of this v1 ?
Thanks,
C.
next prev parent reply other threads:[~2023-11-16 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 8:32 [PATCH 0/4] VFIO device init cleanup Zhenzhong Duan
2023-11-15 8:32 ` [PATCH 1/4] vfio/pci: Move VFIODevice initializations in vfio_instance_init Zhenzhong Duan
2023-11-15 13:11 ` Cédric Le Goater
2023-11-16 2:16 ` Duan, Zhenzhong
2023-11-16 7:28 ` Cédric Le Goater [this message]
2023-11-16 7:46 ` Duan, Zhenzhong
2023-11-15 8:32 ` [PATCH 2/4] vfio/platform: Move VFIODevice initializations in vfio_platform_instance_init Zhenzhong Duan
2023-11-15 8:32 ` [PATCH 3/4] vfio/ap: Move VFIODevice initializations in vfio_ap_instance_init Zhenzhong Duan
2023-11-15 19:27 ` Eric Farman
2023-11-15 8:32 ` [PATCH 4/4] vfio/ccw: Move VFIODevice initializations in vfio_ccw_instance_init Zhenzhong Duan
2023-11-15 19:19 ` Eric Farman
2023-11-15 12:10 ` [PATCH 0/4] VFIO device init cleanup Philippe Mathieu-Daudé
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=2da90861-3f10-47cf-9f6e-39d52b8c929f@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=chao.p.peng@intel.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=kevin.tian@intel.com \
--cc=nicolinc@nvidia.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.com \
--cc=zhenzhong.duan@intel.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).