From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Raj, Ashok" Subject: Re: bind pasid table API Date: Mon, 25 Sep 2017 08:14:04 -0700 Message-ID: <20170925151403.GA131920@otc-nc-03> References: <20170918204516.2f6beffb@jacob-builder> <6ecc1afc-6302-cd22-6944-ef4c6ac09587@arm.com> <20170920153510.4dc5e5c3@jacob-builder> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Jean-Philippe Brucker Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org" , Jacob Pan , David Woodhouse List-Id: iommu@lists.linux-foundation.org On Mon, Sep 25, 2017 at 12:45:00PM +0100, Jean-Philippe Brucker wrote: [snip] > This format tells how the guest organizes its PASID tables. Depending on > 'format', the PASID table can be: > * A flat array of descriptors > * One array of 1st-level descriptors pointing to a 2nd level of > descriptors. When translating an access, the SMMU splits the PASID at bit > 6, uses the upper half to get the 1st level descriptor and the lower half > to get the 2nd level one (4k leaf table). > * The same format, but instead split at PASID bit 10 (64k leaf table) When in multilevel PASID table, do you shadow it in the host? or every level is all hosted in guest space? in Intel vt-d, when context is in a nested mode, PASID table is a gPA. Its a single level table. Cheers, Ashok