From: Jason Gunthorpe <jgg@ziepe.ca>
To: Joonwon Kang <joonwonkang@google.com>
Cc: kevin.tian@intel.com, Alexander.Grest@microsoft.com,
alexander.shishkin@linux.intel.com, amhetre@nvidia.com,
baolu.lu@linux.intel.com, bp@alien8.de,
dave.hansen@linux.intel.com,
easwar.hariharan@linux.microsoft.com, hpa@zytor.com,
iommu@lists.linux.dev, jacob.jun.pan@linux.intel.com,
joro@8bytes.org, jpb@kernel.org, kas@kernel.org, kees@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
nicolinc@nvidia.com, peterz@infradead.org, praan@google.com,
robin.murphy@arm.com, ryasuoka@redhat.com, smostafa@google.com,
sohil.mehta@intel.com, tglx@kernel.org, will@kernel.org,
x86@kernel.org, xin@zytor.com
Subject: Re: [PATCH v2] iommu: Allow device driver to use its own PASID space for SVA
Date: Mon, 25 May 2026 13:47:15 -0300 [thread overview]
Message-ID: <20260525164715.GA2487554@ziepe.ca> (raw)
In-Reply-To: <20260525152924.524721-1-joonwonkang@google.com>
On Mon, May 25, 2026 at 03:29:24PM +0000, Joonwon Kang wrote:
> Currently, the only known expected user of the new kAPI is our team. Since
> I test if the patch resolves our problem before sending it, I believe it
> should be good enough. Do you mean more than our team by "accompanied
> users"?
He means you cannot send patches like this that only serve OOT drivers
to the mainline kernel.
Jason
next prev parent reply other threads:[~2026-05-25 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 15:07 [PATCH v2] iommu: Allow device driver to use its own PASID space for SVA Joonwon Kang
2026-05-21 7:39 ` Baolu Lu
2026-05-21 8:25 ` Joonwon Kang
2026-05-25 8:10 ` Tian, Kevin
2026-05-25 15:29 ` Joonwon Kang
2026-05-25 16:47 ` Jason Gunthorpe [this message]
2026-05-26 6:58 ` Joonwon Kang
2026-05-26 7:21 ` Tian, Kevin
2026-05-26 8:44 ` Joonwon Kang
2026-05-26 12:36 ` Joonwon Kang
2026-05-26 12:39 ` Jason Gunthorpe
2026-05-26 12:46 ` Joonwon Kang
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=20260525164715.GA2487554@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Alexander.Grest@microsoft.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=amhetre@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=easwar.hariharan@linux.microsoft.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joonwonkang@google.com \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=kas@kernel.org \
--cc=kees@kernel.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicolinc@nvidia.com \
--cc=peterz@infradead.org \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=ryasuoka@redhat.com \
--cc=smostafa@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.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