Re: [PATCH v4 1/9] iommu/vt-d: Global PASID name space

Hi Peter, Thanks for looking into my patches. On 07/11/2018 10:48 AM, Peter Xu wrote: > On Mon, Jul 09, 2018 at 01:22:50PM +0800, Lu Baolu wrote: > > [...] > >> +#ifndef __INTEL_PASID_H >> +#define __INTEL_PASID_H >> + >> +#define PASID_MIN 0x1 >> +#define PASID_MAX

Re: [PATCH v4 1/9] iommu/vt-d: Global PASID name space

On Mon, Jul 09, 2018 at 01:22:50PM +0800, Lu Baolu wrote: [...] > +#ifndef __INTEL_PASID_H > +#define __INTEL_PASID_H > + > +#define PASID_MIN0x1 > +#define PASID_MAX0x2 Could I ask whether there's a reason to explicitly use 0x2 for the max value?

[PATCH v4 1/9] iommu/vt-d: Global PASID name space

This adds the system wide PASID name space for the PASID allocation. Currently we are using per IOMMU PASID name spaces which are not suitable for some use cases. For an example, one application (associated with a PASID) might talk to two physical devices simultaneously while the two devices could