[PATCH v5 02/12] iommu/vt-d: Manage scalalble mode PASID tables

[Joerg Roedel]

Hi Baolu,

On Wed, Nov 28, 2018 at 11:54:39AM +0800, Lu Baolu wrote:
> @@ -2482,12 +2482,13 @@ static struct dmar_domain *dmar_insert_one_dev_info(struct intel_iommu *iommu,
>  	if (dev)
>  		dev->archdata.iommu = info;
>  
> -	if (dev && dev_is_pci(dev) && info->pasid_supported) {
> +	/* PASID table is mandatory for a PCI device in scalable mode. */
> +	if (dev && dev_is_pci(dev) && sm_supported(iommu)) {

This will also allocate a PASID table if the device does not support
PASIDs, right? Will the table not be used in that case or will the
device just use the fallback PASID? Isn't it better in that case to have
no PASID table?

> @@ -143,18 +143,20 @@ int intel_pasid_alloc_table(struct device *dev)
>  		return -ENOMEM;
>  	INIT_LIST_HEAD(&pasid_table->dev);
>  
> -	size = sizeof(struct pasid_entry);
> -	count = min_t(int, pci_max_pasids(to_pci_dev(dev)), intel_pasid_max_id);
> -	order = get_order(size * count);
> +	if (info->pasid_supported)
> +		max_pasid = min_t(int, pci_max_pasids(to_pci_dev(dev)),
> +				  intel_pasid_max_id);
> +
> +	size = max_pasid >> (PASID_PDE_SHIFT - 3);
> +	order = size ? get_order(size) : 0;
>  	pages = alloc_pages_node(info->iommu->node,
> -				 GFP_ATOMIC | __GFP_ZERO,
> -				 order);
> +				 GFP_ATOMIC | __GFP_ZERO, order);

This is a simple data structure allocation path, does it need
GFP_ATOMIC?



	Joerg