[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN9PR11MB5276083231E7C7C6FFCC6E248C93A@BN9PR11MB5276.namprd11.prod.outlook.com>
Date: Fri, 15 Dec 2023 07:38:19 +0000
From: "Tian, Kevin" <kevin.tian@...el.com>
To: Jason Gunthorpe <jgg@...dia.com>, Suravee Suthikulpanit
<suravee.suthikulpanit@....com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>, "joro@...tes.org"
<joro@...tes.org>, "Liu, Yi L" <yi.l.liu@...el.com>, "nicolinc@...dia.com"
<nicolinc@...dia.com>, "eric.auger@...hat.com" <eric.auger@...hat.com>,
"vasant.hegde@....com" <vasant.hegde@....com>, "jon.grimm@....com"
<jon.grimm@....com>, "santosh.shukla@....com" <santosh.shukla@....com>,
"Dhaval.Giani@....com" <Dhaval.Giani@....com>, "pandoh@...gle.com"
<pandoh@...gle.com>, "loganodell@...gle.com" <loganodell@...gle.com>
Subject: RE: [RFC PATCH 4/6] iommufd: Introduce data struct for AMD nested
domain allocation
> From: Jason Gunthorpe <jgg@...dia.com>
> Sent: Wednesday, December 13, 2023 10:04 PM
>
> The viommu object should hold the GID. I'm not sure you need a GID
> right now (can you just issue invalidation on the physical side?), but
> if you do need GID to bridge until the viommu is ready it should
> probably be allocated by and stored in the nesting parent.
>
and how is GID different from existing Domain ID of nesting parent?
Powered by blists - more mailing lists