From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 3/4] vfio: use __aligned_u64 in struct vfio_iommu_type1_info
Date: Thu, 10 Aug 2023 10:25:35 -0400 [thread overview]
Message-ID: <20230810142535.GD2931656@fedora> (raw)
In-Reply-To: <BN9PR11MB5276D1304E854E2AE7E8EFA18C13A@BN9PR11MB5276.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
On Thu, Aug 10, 2023 at 03:25:37AM +0000, Tian, Kevin wrote:
> > From: Stefan Hajnoczi <stefanha@redhat.com>
> > Sent: Thursday, August 10, 2023 5:03 AM
> >
> > @@ -1303,8 +1303,9 @@ struct vfio_iommu_type1_info {
> > __u32 flags;
> > #define VFIO_IOMMU_INFO_PGSIZES (1 << 0) /* supported page sizes info
> > */
> > #define VFIO_IOMMU_INFO_CAPS (1 << 1) /* Info supports caps */
> > - __u64 iova_pgsizes; /* Bitmap of supported page sizes */
> > + __aligned_u64 iova_pgsizes; /* Bitmap of supported page
> > sizes */
> > __u32 cap_offset; /* Offset within info struct of first cap */
> > + __u32 reserved;
>
> isn't this conflicting with the new 'pad' field introduced in your another
> patch " [PATCH v3] vfio: align capability structures"?
>
> @@ -1304,6 +1305,7 @@ struct vfio_iommu_type1_info {
> #define VFIO_IOMMU_INFO_CAPS (1 << 1) /* Info supports caps */
> __u64 iova_pgsizes; /* Bitmap of supported page sizes */
> __u32 cap_offset; /* Offset within info struct of first cap */
> + __u32 pad;
> };
Yes, I will rebase this series when "[PATCH v3] vfio: align capability
structures" is merged. I see the __aligned_u64 as a separate issue and
don't want to combine the patch series.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-10 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 21:02 [PATCH 0/4] vfio: use __aligned_u64 for ioctl structs Stefan Hajnoczi
2023-08-09 21:02 ` [PATCH 1/4] vfio: trivially " Stefan Hajnoczi
2023-08-14 17:47 ` Jason Gunthorpe
2023-08-09 21:02 ` [PATCH 2/4] vfio: use __aligned_u64 in struct vfio_device_gfx_plane_info Stefan Hajnoczi
2023-08-10 3:22 ` Tian, Kevin
2023-08-10 14:24 ` Stefan Hajnoczi
2023-08-15 12:38 ` Stefan Hajnoczi
2023-08-14 17:50 ` Jason Gunthorpe
2023-08-15 12:38 ` Stefan Hajnoczi
2023-08-15 15:23 ` David Laight
2023-08-16 13:36 ` Stefan Hajnoczi
2023-08-09 21:02 ` [PATCH 3/4] vfio: use __aligned_u64 in struct vfio_iommu_type1_info Stefan Hajnoczi
2023-08-10 3:25 ` Tian, Kevin
2023-08-10 14:25 ` Stefan Hajnoczi [this message]
2023-08-14 17:52 ` Jason Gunthorpe
2023-08-09 21:02 ` [PATCH 4/4] vfio: use __aligned_u64 in struct vfio_device_ioeventfd Stefan Hajnoczi
2023-08-14 17:52 ` Jason Gunthorpe
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=20230810142535.GD2931656@fedora \
--to=stefanha@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.