[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250113191817.GA540878@nvidia.com>
Date: Mon, 13 Jan 2025 15:18:17 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Nicolin Chen <nicolinc@...dia.com>
Cc: will@...nel.org, kevin.tian@...el.com, corbet@....net,
oe-kbuild-all@...ts.linux.dev, joro@...tes.org,
suravee.suthikulpanit@....com, robin.murphy@....com,
dwmw2@...radead.org, baolu.lu@...ux.intel.com, shuah@...nel.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org,
eric.auger@...hat.com, jean-philippe@...aro.org, mdf@...nel.org,
mshavit@...gle.com, shameerali.kolothum.thodi@...wei.com,
smostafa@...gle.com, ddutile@...hat.com, yi.l.liu@...el.com,
patches@...ts.linux.dev
Subject: Re: [PATCH v5 14/14] iommu/arm-smmu-v3: Report events that belong to
devices attached to vIOMMU
On Mon, Jan 13, 2025 at 11:15:21AM -0800, Nicolin Chen wrote:
> On Mon, Jan 13, 2025 at 03:06:41PM -0400, Jason Gunthorpe wrote:
> > On Mon, Jan 13, 2025 at 11:01:10AM -0800, Nicolin Chen wrote:
> >
> > > +/* This is basically iommu_vevent_arm_smmuv3 in u64 for conversion */
> > > +struct arm_vsmmu_evt {
> > > + union {
> > > + u64 evt[EVTQ_ENT_DWORDS];
> > > + struct iommu_vevent_arm_smmuv3 uevt;
> > > + };
> > > +};
> >
> > This doesn't seem right, don't make unions like this
>
> This is copied from the invalidate union though... Any reason why
> this is no longer good for evt v.s. cmd?
In that case it was trying to be really optimal and copy in place,
here we don't care so much..
Jason
Powered by blists - more mailing lists