From: Jason Gunthorpe <jgg@nvidia.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joro@8bytes.org>,
peter.maydell@linaro.org, kvm@vger.kernel.org,
vivek.gautam@arm.com, kvmarm@lists.cs.columbia.edu,
eric.auger.pro@gmail.com, ashok.raj@intel.com, maz@kernel.org,
vsethi@nvidia.com, zhangfei.gao@linaro.org, kevin.tian@intel.com,
will@kernel.org, alex.williamson@redhat.com,
wangxingang5@huawei.com, linux-kernel@vger.kernel.org,
lushenming@huawei.com, iommu@lists.linux-foundation.org,
robin.murphy@arm.com
Subject: Re: [RFC v16 1/9] iommu: Introduce attach/detach_pasid_table API
Date: Thu, 9 Dec 2021 11:40:46 -0400 [thread overview]
Message-ID: <20211209154046.GQ6385@nvidia.com> (raw)
In-Reply-To: <b576084b-482f-bcb7-35a6-d786dbb305e1@redhat.com>
On Thu, Dec 09, 2021 at 08:50:04AM +0100, Eric Auger wrote:
> > The kernel API should accept the S1ContextPtr IPA and all the parts of
> > the STE that relate to the defining the layout of what the S1Context
> > points to an thats it.
> Yes that's exactly what is done currently. At config time the host must
> trap guest STE changes (format and S1ContextPtr) and "incorporate" those
> changes into the stage2 related STE information. The STE is owned by the
> host kernel as it contains the stage2 information (S2TTB).
[..]
> Note this series only coped with a single CD in the Context Descriptor
> Table.
I'm confused, where does this limit arise?
The kernel accepts as input all the bits in the STE that describe the
layout of the CDT owned by userspace, shouldn't userspace be able to
construct all forms of CDT with any number of CDs in them?
Or do you mean this is some qemu limitation?
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe via iommu <iommu@lists.linux-foundation.org>
To: Eric Auger <eric.auger@redhat.com>
Cc: peter.maydell@linaro.org, kevin.tian@intel.com,
lushenming@huawei.com, robin.murphy@arm.com, ashok.raj@intel.com,
kvm@vger.kernel.org,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
maz@kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, vsethi@nvidia.com,
vivek.gautam@arm.com, alex.williamson@redhat.com,
wangxingang5@huawei.com, zhangfei.gao@linaro.org,
eric.auger.pro@gmail.com, will@kernel.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [RFC v16 1/9] iommu: Introduce attach/detach_pasid_table API
Date: Thu, 9 Dec 2021 11:40:46 -0400 [thread overview]
Message-ID: <20211209154046.GQ6385@nvidia.com> (raw)
In-Reply-To: <b576084b-482f-bcb7-35a6-d786dbb305e1@redhat.com>
On Thu, Dec 09, 2021 at 08:50:04AM +0100, Eric Auger wrote:
> > The kernel API should accept the S1ContextPtr IPA and all the parts of
> > the STE that relate to the defining the layout of what the S1Context
> > points to an thats it.
> Yes that's exactly what is done currently. At config time the host must
> trap guest STE changes (format and S1ContextPtr) and "incorporate" those
> changes into the stage2 related STE information. The STE is owned by the
> host kernel as it contains the stage2 information (S2TTB).
[..]
> Note this series only coped with a single CD in the Context Descriptor
> Table.
I'm confused, where does this limit arise?
The kernel accepts as input all the bits in the STE that describe the
layout of the CDT owned by userspace, shouldn't userspace be able to
construct all forms of CDT with any number of CDs in them?
Or do you mean this is some qemu limitation?
Jason
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: kevin.tian@intel.com, lushenming@huawei.com,
robin.murphy@arm.com, ashok.raj@intel.com, kvm@vger.kernel.org,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
maz@kernel.org, Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
vsethi@nvidia.com, vivek.gautam@arm.com,
alex.williamson@redhat.com, wangxingang5@huawei.com,
zhangfei.gao@linaro.org, eric.auger.pro@gmail.com,
will@kernel.org, kvmarm@lists.cs.columbia.edu,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [RFC v16 1/9] iommu: Introduce attach/detach_pasid_table API
Date: Thu, 9 Dec 2021 11:40:46 -0400 [thread overview]
Message-ID: <20211209154046.GQ6385@nvidia.com> (raw)
In-Reply-To: <b576084b-482f-bcb7-35a6-d786dbb305e1@redhat.com>
On Thu, Dec 09, 2021 at 08:50:04AM +0100, Eric Auger wrote:
> > The kernel API should accept the S1ContextPtr IPA and all the parts of
> > the STE that relate to the defining the layout of what the S1Context
> > points to an thats it.
> Yes that's exactly what is done currently. At config time the host must
> trap guest STE changes (format and S1ContextPtr) and "incorporate" those
> changes into the stage2 related STE information. The STE is owned by the
> host kernel as it contains the stage2 information (S2TTB).
[..]
> Note this series only coped with a single CD in the Context Descriptor
> Table.
I'm confused, where does this limit arise?
The kernel accepts as input all the bits in the STE that describe the
layout of the CDT owned by userspace, shouldn't userspace be able to
construct all forms of CDT with any number of CDs in them?
Or do you mean this is some qemu limitation?
Jason
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2021-12-09 15:40 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 10:44 [RFC v16 0/9] SMMUv3 Nested Stage Setup (IOMMU part) Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 1/9] iommu: Introduce attach/detach_pasid_table API Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-12-06 10:48 ` Joerg Roedel
2021-12-06 10:48 ` Joerg Roedel
2021-12-06 10:48 ` Joerg Roedel
2021-12-07 10:22 ` Eric Auger
2021-12-07 10:22 ` Eric Auger
2021-12-07 10:22 ` Eric Auger
2021-12-08 2:44 ` Lu Baolu
2021-12-08 2:44 ` Lu Baolu
2021-12-08 2:44 ` Lu Baolu
2021-12-08 7:33 ` Eric Auger
2021-12-08 7:33 ` Eric Auger
2021-12-08 7:33 ` Eric Auger
2021-12-08 12:56 ` Jason Gunthorpe
2021-12-08 12:56 ` Jason Gunthorpe
2021-12-08 12:56 ` Jason Gunthorpe via iommu
2021-12-08 17:20 ` Jean-Philippe Brucker
2021-12-08 17:20 ` Jean-Philippe Brucker
2021-12-08 17:20 ` Jean-Philippe Brucker
2021-12-08 18:31 ` Jason Gunthorpe
2021-12-08 18:31 ` Jason Gunthorpe
2021-12-08 18:31 ` Jason Gunthorpe via iommu
2021-12-09 2:58 ` Tian, Kevin
2021-12-09 2:58 ` Tian, Kevin
2021-12-09 2:58 ` Tian, Kevin
[not found] ` <BN9PR11MB527624080CB9302481B74C7A8C709@BN9PR11MB5276.namprd11.prod.outlook.com>
2021-12-09 3:59 ` Tian, Kevin
2021-12-09 3:59 ` Tian, Kevin
2021-12-09 3:59 ` Tian, Kevin
2021-12-09 16:08 ` Jason Gunthorpe
2021-12-09 16:08 ` Jason Gunthorpe
2021-12-09 16:08 ` Jason Gunthorpe via iommu
2021-12-10 8:56 ` Tian, Kevin
2021-12-10 8:56 ` Tian, Kevin
2021-12-10 13:23 ` Jason Gunthorpe
2021-12-10 13:23 ` Jason Gunthorpe
2021-12-11 3:57 ` Tian, Kevin
2021-12-11 3:57 ` Tian, Kevin
2021-12-16 20:48 ` Jason Gunthorpe
2021-12-16 20:48 ` Jason Gunthorpe
2022-01-04 2:42 ` Tian, Kevin
2022-01-04 2:42 ` Tian, Kevin
2021-12-11 5:18 ` Tian, Kevin
2021-12-11 5:18 ` Tian, Kevin
2021-12-09 7:50 ` Eric Auger
2021-12-09 7:50 ` Eric Auger
2021-12-09 7:50 ` Eric Auger
2021-12-09 15:40 ` Jason Gunthorpe [this message]
2021-12-09 15:40 ` Jason Gunthorpe
2021-12-09 15:40 ` Jason Gunthorpe via iommu
2021-12-09 16:37 ` Eric Auger
2021-12-09 16:37 ` Eric Auger
2021-12-09 16:37 ` Eric Auger
2021-12-09 3:21 ` Tian, Kevin
2021-12-09 3:21 ` Tian, Kevin
2021-12-09 3:21 ` Tian, Kevin
2021-12-09 9:44 ` Eric Auger
2021-12-09 9:44 ` Eric Auger
2021-12-09 9:44 ` Eric Auger
2021-12-09 8:31 ` Eric Auger
2021-12-09 8:31 ` Eric Auger
2021-12-09 8:31 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 2/9] iommu: Introduce iommu_get_nesting Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 22:15 ` kernel test robot
2021-10-28 3:22 ` kernel test robot
2021-10-27 10:44 ` [RFC v16 3/9] iommu/smmuv3: Allow s1 and s2 configs to coexist Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 4/9] iommu/smmuv3: Get prepared for nested stage support Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 5/9] iommu/smmuv3: Implement attach/detach_pasid_table Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 6/9] iommu/smmuv3: Allow stage 1 invalidation with unmanaged ASIDs Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 7/9] iommu/smmuv3: Implement cache_invalidate Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` [RFC v16 8/9] iommu/smmuv3: report additional recoverable faults Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 21:05 ` kernel test robot
2021-10-27 22:41 ` kernel test robot
2021-10-27 22:41 ` kernel test robot
2021-10-27 10:44 ` [RFC v16 9/9] iommu/smmuv3: Disallow nested mode in presence of HW MSI regions Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-10-27 10:44 ` Eric Auger
2021-12-03 12:27 ` [RFC v16 0/9] SMMUv3 Nested Stage Setup (IOMMU part) Zhangfei Gao
2021-12-03 12:27 ` Zhangfei Gao
2021-12-03 12:27 ` Zhangfei Gao
2021-12-07 10:27 ` Eric Auger
2021-12-07 10:27 ` Eric Auger
2021-12-07 10:27 ` Eric Auger
2021-12-07 10:35 ` Zhangfei Gao
2021-12-07 10:35 ` Zhangfei Gao
2021-12-07 10:35 ` Zhangfei Gao
2021-12-07 11:06 ` Eric Auger
2021-12-07 11:06 ` Eric Auger
2021-12-07 11:06 ` Eric Auger
2021-12-08 13:33 ` Shameerali Kolothum Thodi
2021-12-08 13:33 ` Shameerali Kolothum Thodi
2021-12-08 13:33 ` Shameerali Kolothum Thodi via iommu
2021-12-03 13:13 ` Sumit Gupta
2021-12-03 13:13 ` Sumit Gupta
2021-12-03 13:13 ` Sumit Gupta via iommu
2021-12-07 10:28 ` Eric Auger
2021-12-07 10:28 ` Eric Auger
2021-12-07 10:28 ` Eric Auger
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=20211209154046.GQ6385@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lushenming@huawei.com \
--cc=maz@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=robin.murphy@arm.com \
--cc=vivek.gautam@arm.com \
--cc=vsethi@nvidia.com \
--cc=wangxingang5@huawei.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.