From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Nicolin Chen <nicolinc@nvidia.com>,
Baolu Lu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
"Liu, Yi L" <yi.l.liu@intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Joel Granados <j.granados@samsung.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 06/10] iommufd: Add iommufd fault object
Date: Mon, 8 Jul 2024 13:22:55 -0300 [thread overview]
Message-ID: <20240708162255.GA14050@ziepe.ca> (raw)
In-Reply-To: <BN9PR11MB52760E55FE52C5B670AA75058CDF2@BN9PR11MB5276.namprd11.prod.outlook.com>
On Fri, Jul 05, 2024 at 12:49:10AM +0000, Tian, Kevin wrote:
> > > > > > > +enum iommu_fault_type {
> > > > > > > + IOMMU_FAULT_TYPE_HWPT_IOPF,
> > > > > > > + IOMMU_FAULT_TYPE_VIOMMU_IRQ,
> > > > > > > +};
> > > > > > >
> > > > > > > struct iommu_fault_alloc {
> > > > > > > __u32 size;
> > > > > > > __u32 flags;
> > > > > > > + __u32 type; /* enum iommu_fault_type */
> > > > > > > __u32 out_fault_id;
> > > > > > > __u32 out_fault_fd;
> > > > and need a new reserved field for alignment.
> >
> > Hmm, what's the reason for enforcing a 64-bit alignment to an
> > all-u32 struct though? I thought we need a reserved field only
> > for padding. The struct iommu_ioas_alloc has three u32 members
> > for example?
>
> yeah please ignore this comment.
Sometimes I encourage it so that people notice the if the structure is
changed later. Almost all structs here are 8 byte aligned. It is OK
like this too.
Jason
next prev parent reply other threads:[~2024-07-08 16:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 6:34 [PATCH v8 00/10] IOMMUFD: Deliver IO page faults to user space Lu Baolu
2024-07-02 6:34 ` [PATCH v8 01/10] iommu: Introduce domain attachment handle Lu Baolu
2024-07-02 6:34 ` [PATCH v8 02/10] iommu: Remove sva handle list Lu Baolu
2024-07-02 6:34 ` [PATCH v8 03/10] iommu: Add attach handle to struct iopf_group Lu Baolu
2024-07-02 6:34 ` [PATCH v8 04/10] iommu: Extend domain attach group with handle support Lu Baolu
2024-07-02 6:34 ` [PATCH v8 05/10] iommufd: Add fault and response message definitions Lu Baolu
2024-07-02 6:34 ` [PATCH v8 06/10] iommufd: Add iommufd fault object Lu Baolu
2024-07-03 23:06 ` Nicolin Chen
2024-07-04 2:59 ` Baolu Lu
2024-07-04 5:36 ` Nicolin Chen
2024-07-04 6:37 ` Tian, Kevin
2024-07-04 7:32 ` Baolu Lu
2024-07-04 23:18 ` Nicolin Chen
2024-07-05 0:49 ` Tian, Kevin
2024-07-08 16:22 ` Jason Gunthorpe [this message]
2024-07-08 16:29 ` Jason Gunthorpe
2024-07-08 18:36 ` Nicolin Chen
2024-07-09 17:00 ` Jason Gunthorpe
2024-07-09 17:33 ` Nicolin Chen
2024-07-12 13:00 ` Jason Gunthorpe
2024-07-02 6:34 ` [PATCH v8 07/10] iommufd: Fault-capable hwpt attach/detach/replace Lu Baolu
2024-10-15 3:19 ` Zhangfei Gao
2024-10-15 12:54 ` Jason Gunthorpe
2024-10-16 1:58 ` Zhangfei Gao
2024-10-16 15:25 ` Jason Gunthorpe
2024-10-17 1:44 ` Zhangfei Gao
2024-10-17 12:05 ` Jason Gunthorpe
2024-10-17 12:35 ` Zhangfei Gao
2024-10-17 12:58 ` Shameerali Kolothum Thodi
2024-10-17 13:08 ` Jason Gunthorpe
2024-10-18 1:58 ` Baolu Lu
2024-10-18 2:45 ` Zhangfei Gao
2024-10-27 14:12 ` Zhangfei Gao
2024-10-27 14:26 ` Baolu Lu
2024-10-28 9:56 ` Zhangfei Gao
2024-10-28 11:17 ` Baolu Lu
2024-10-18 14:33 ` Jason Gunthorpe
2024-10-18 13:53 ` Jason Gunthorpe
2024-10-22 14:30 ` Zhangfei Gao
2024-10-22 14:52 ` Jason Gunthorpe
2024-10-23 10:22 ` Zhangfei Gao
2024-07-02 6:34 ` [PATCH v8 08/10] iommufd: Associate fault object with iommufd_hw_pgtable Lu Baolu
2024-07-02 6:34 ` [PATCH v8 09/10] iommufd/selftest: Add IOPF support for mock device Lu Baolu
2024-07-02 6:34 ` [PATCH v8 10/10] iommufd/selftest: Add coverage for IOPF test Lu Baolu
2024-07-04 14:18 ` [PATCH v8 00/10] IOMMUFD: Deliver IO page faults to user space Will Deacon
2024-07-09 17:23 ` 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=20240708162255.GA14050@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=j.granados@samsung.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will@kernel.org \
--cc=yi.l.liu@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).