Linux IOMMU Development
 help / color / mirror / Atom feed
From: Suravee Suthikulanit <suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	jay.cornwall-5C7GfCeVMHo@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kim.naru-5C7GfCeVMHo@public.gmane.org
Subject: Re: [PATCH] iommu/amd: Fix logics to determine and checking max PASID
Date: Wed, 5 Mar 2014 16:46:58 -0600	[thread overview]
Message-ID: <5317A962.10004@amd.com> (raw)
In-Reply-To: <20140305223544.GA2813-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>

Joerg,

Other commands can still support upto 20-bit PASID. As I mentioned, 
there is still no system with more than 16-bit PASID.

Either way, I have also replaced the PASID_MASK with the value derived 
from MMIOx30h[PASmax] of the IOMMU Extended Feature register instead.
This should allow us not to have to change the mask things again for 
future hardware.

We just need to revisit this BUG_ON() part when the new spec comes.

Suravee


On 3/5/2014 4:35 PM, Joerg Roedel wrote:
> On Wed, Mar 05, 2014 at 01:01:08PM -0600, suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org wrote:
>>   drivers/iommu/amd_iommu.c       |   26 +++++++++++++++++++++++---
>>   drivers/iommu/amd_iommu_init.c  |   15 ++++++++-------
>>   drivers/iommu/amd_iommu_types.h |    6 ++----
>>   drivers/iommu/amd_iommu_v2.c    |    2 +-
>>   4 files changed, 34 insertions(+), 15 deletions(-)
>
> Hmm, this looks a bit complicated. Since the inv_iotlb_pasid and
> complete_ppr command only support 16 bit pasids by specification, there
> is no way to support pasids with more than 16 bits in general anymore. I
> think the best way to handle it is to just change the PASID_MASK to
> 0x0000ffff.
>
>>   static void build_inv_iotlb_pasid(struct iommu_cmd *cmd, u16 devid, int pasid,
>>   				  int qdep, u64 address, bool size)
>>   {
>> +	/* Note:
>> +	 * This command supports only 16-bit PASID.
>> +	 * Currently, hardware only implement upto 16-bit PASID
>> +	 * even though the spec says it could have upto 20 bits.
>> +	 * This is likely to be updated in the future revision of
>> +	 * IOMMU specs when the hardware with PASID > 16 bits
>> +	 * become available.
>> +	 */
>> +	BUG_ON(pasid > 0xFFFF);
>
> We can keep this as BUG_ON(pasid & ~PASID_MASK), but then ...
>
>> -		cmd->data[1]  = pasid & PASID_MASK;
>> +		cmd->data[1]  = pasid & amd_iommu_max_pasid;
>
> ... masking out the other bits is redundant.
>
>
> 	Joerg
>
>
>

  parent reply	other threads:[~2014-03-05 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 19:01 [PATCH] iommu/amd: Fix logics to determine and checking max PASID suravee.suthikulpanit-5C7GfCeVMHo
     [not found] ` <1394046068-3858-1-git-send-email-suravee.suthikulpanit-5C7GfCeVMHo@public.gmane.org>
2014-03-05 22:35   ` Joerg Roedel
     [not found]     ` <20140305223544.GA2813-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-03-05 22:46       ` Suravee Suthikulanit [this message]
2014-03-05 23:08       ` Suravee Suthikulanit

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=5317A962.10004@amd.com \
    --to=suravee.suthikulpanit-5c7gfcevmho@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jay.cornwall-5C7GfCeVMHo@public.gmane.org \
    --cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
    --cc=kim.naru-5C7GfCeVMHo@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox