[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230505210900.0764fa83@jacob-builder>
Date: Fri, 5 May 2023 21:09:00 -0700
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Jason Gunthorpe <jgg@...pe.ca>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
jacob.jun.pan@...ux.intel.com
Subject: Re: [git pull] IOMMU Updates for Linux v6.4
Hi Jason,
On Sun, 30 Apr 2023 20:06:30 -0300, Jason Gunthorpe <jgg@...pe.ca> wrote:
> We've had this longstanding confusion in the iommu layer that SVA and
> PASID are one and the same thing, we are slowly reorganizing it.. For
> now it is fine for IOMMU_SVA to cover the PASID allocator as the only
> drivers that support PASID also support SVA.
>
> Arguably the design is backwards and IOMMU_SVA should be user
> selectable and it should turn off the SVA code entirely including the
> driver code.
>
> > Somebody should double-check my result, in other words.
>
> I didn't notice anything wrong, I'm sure Lu and Yi will test it!
FWIW, I did a quick test with SVA ENQCMD on an Intel Data Streaming
Accelerator (DSA) shared work queue, seems to work fine. Code looks good to
me too.
Thanks,
Jacob
Powered by blists - more mailing lists