public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
	jacob.jun.pan@linux.intel.com
Subject: Re: [git pull] IOMMU Updates for Linux v6.4
Date: Fri, 5 May 2023 21:09:00 -0700	[thread overview]
Message-ID: <20230505210900.0764fa83@jacob-builder> (raw)
In-Reply-To: <ZE70doFi8X3KgfrV@ziepe.ca>

Hi Jason,

On Sun, 30 Apr 2023 20:06:30 -0300, Jason Gunthorpe <jgg@ziepe.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

  reply	other threads:[~2023-05-06  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 11:13 [git pull] IOMMU Updates for Linux v6.4 Joerg Roedel
2023-04-30 20:07 ` Linus Torvalds
2023-04-30 23:06   ` Jason Gunthorpe
2023-05-06  4:09     ` Jacob Pan [this message]
2023-05-05 14:02   ` Joerg Roedel
2023-05-05 18:03     ` Linus Torvalds
2023-05-05 19:57       ` Jason Gunthorpe
2023-05-05 20:10         ` Linus Torvalds
2023-05-06  2:58           ` Tian, Kevin
2023-04-30 20:08 ` pr-tracker-bot

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=20230505210900.0764fa83@jacob-builder \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox