From: "Luck, Tony" <tony.luck@intel.com>
To: Andy Lutomirski <luto@kernel.org>, "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
Peter Zijlstra <peterz@infradead.org>, x86 <x86@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
iommu <iommu@lists.linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>,
H Peter Anvin <hpa@zytor.com>,
Christoph Hellwig <hch@infradeed.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw2@infradead.org>
Subject: RE: [PATCH v3 01/13] iommu: Change type of pasid to unsigned int
Date: Wed, 17 Jun 2020 19:39:43 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F67216A@ORSMSX115.amr.corp.intel.com> (raw)
In-Reply-To: <CALCETrXFHa_05-sGAy5M9YGJWUfTn9MfM-ZYk+hp12tqHNJA0Q@mail.gmail.com>
> Is PASID in the uapi at all?
$ grep pasid include/uapi/linux/iommu.h
* @pasid: Process Address Space ID
__u32 pasid;
* @pasid: Process Address Space ID
__u32 pasid;
* @pasid: Process Address Space ID
__u32 pasid;
* - If the PASID bit is set, the @pasid field is populated and the invalidation
* @pasid: process address space ID
__u64 pasid;
* struct iommu_inv_pasid_info - PASID Selective Invalidation Structure
* - If the PASID bit is set, the @pasid field is populated and the invalidation
* @pasid: process address space ID
struct iommu_inv_pasid_info {
__u64 pasid;
* @pasid_info: invalidation data when @granularity is %IOMMU_INV_GRANU_PASID
struct iommu_inv_pasid_info pasid_info;
* struct iommu_gpasid_bind_data_vtd - Intel VT-d specific data on device and guest
struct iommu_gpasid_bind_data_vtd {
* struct iommu_gpasid_bind_data - Information about device and guest PASID binding
* @hpasid: Process address space ID used for the guest mm in host IOMMU
* @gpasid: Process address space ID used for the guest mm in guest IOMMU
struct iommu_gpasid_bind_data {
__u64 hpasid;
__u64 gpasid;
struct iommu_gpasid_bind_data_vtd vtd;
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-06-17 19:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 18:23 [PATCH v3 00/13] x86: tag application address space for devices Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 01/13] iommu: Change type of pasid to unsigned int Fenghua Yu
2020-06-17 19:35 ` Andy Lutomirski
2020-06-17 19:39 ` Luck, Tony [this message]
2020-06-17 20:04 ` Andy Lutomirski
2020-06-18 7:12 ` Christoph Hellwig
2020-06-18 15:22 ` Fenghua Yu
2020-06-22 18:09 ` Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 02/13] ocxl: " Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 03/13] iommu/vt-d: Change flags type to unsigned int in binding mm Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 04/13] docs: x86: Add documentation for SVA (Shared Virtual Addressing) Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 05/13] x86/cpufeatures: Enumerate ENQCMD and ENQCMDS instructions Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 06/13] x86/fpu/xstate: Add supervisor PASID state for ENQCMD feature Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 07/13] x86/msr-index: Define IA32_PASID MSR Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 08/13] mm: Define pasid in mm Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 09/13] fork: Clear PASID for new mm Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 10/13] x86/process: Clear PASID state for a newly forked/cloned thread Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 11/13] x86/mmu: Allocate/free PASID Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 12/13] sched: Define and initialize a flag to identify valid PASID in the task Fenghua Yu
2020-06-17 18:23 ` [PATCH v3 13/13] x86/traps: Fix up invalid PASID Fenghua Yu
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=3908561D78D1C84285E8C5FCA982C28F7F67216A@ORSMSX115.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.jiang@intel.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=hch@infradeed.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@intel.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).