* [PATCH] iommu/amd: Fix logics to determine and checking max PASID
@ 2014-03-05 19:01 suravee.suthikulpanit
2014-03-05 22:35 ` Joerg Roedel
0 siblings, 1 reply; 4+ messages in thread
From: suravee.suthikulpanit @ 2014-03-05 19:01 UTC (permalink / raw)
To: iommu, joro; +Cc: linux-kernel, kim.naru, jay.cornwall, Suravee Suthikulpanit
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
According to IOMMUv2, max PASID is defined as ((2^(PASmax+1)) - 1)
using the value from MMIOx30[PASmax] register. The current does not
determine this correctly. Also the PASID_MASK should be determined by
max PASID instead of hardcoding value of 0xfffff.
Adding logic to check the number of bits used for PASID before issuing
CMD_INV_IOTLB_PAGES and CMD_COMPLETE_PPR since they only support 16-bit
PASID. However, this should not affect the currently available
hardware since they only implement 16-bit PASID.
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Tested-by: Jay Cornwall <Jay.Cornwall@amd.com>
---
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(-)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
index faf0da4..d9d64ce 100644
--- a/drivers/iommu/amd_iommu.c
+++ b/drivers/iommu/amd_iommu.c
@@ -963,7 +963,7 @@ static void build_inv_iommu_pasid(struct iommu_cmd *cmd, u16 domid, int pasid,
address &= ~(0xfffULL);
- cmd->data[0] = pasid & PASID_MASK;
+ cmd->data[0] = pasid & amd_iommu_max_pasid;
cmd->data[1] = domid;
cmd->data[2] = lower_32_bits(address);
cmd->data[3] = upper_32_bits(address);
@@ -977,6 +977,16 @@ static void build_inv_iommu_pasid(struct iommu_cmd *cmd, u16 domid, int pasid,
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);
+
memset(cmd, 0, sizeof(*cmd));
address &= ~(0xfffULL);
@@ -997,11 +1007,21 @@ static void build_inv_iotlb_pasid(struct iommu_cmd *cmd, u16 devid, int pasid,
static void build_complete_ppr(struct iommu_cmd *cmd, u16 devid, int pasid,
int status, int tag, bool gn)
{
+ /* 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);
+
memset(cmd, 0, sizeof(*cmd));
cmd->data[0] = devid;
if (gn) {
- cmd->data[1] = pasid & PASID_MASK;
+ cmd->data[1] = pasid & amd_iommu_max_pasid;
cmd->data[2] = CMD_INV_IOMMU_PAGES_GN_MASK;
}
cmd->data[3] = tag & 0x1ff;
@@ -3570,7 +3590,7 @@ int amd_iommu_domain_enable_v2(struct iommu_domain *dom, int pasids)
unsigned long flags;
int levels, ret;
- if (pasids <= 0 || pasids > (PASID_MASK + 1))
+ if (pasids <= 0 || pasids > (amd_iommu_max_pasid + 1))
return -EINVAL;
/* Number of GCR3 table levels required */
diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
index 28b4bea..ce2a3b3 100644
--- a/drivers/iommu/amd_iommu_init.c
+++ b/drivers/iommu/amd_iommu_init.c
@@ -150,7 +150,8 @@ int amd_iommus_present;
bool amd_iommu_np_cache __read_mostly;
bool amd_iommu_iotlb_sup __read_mostly = true;
-u32 amd_iommu_max_pasids __read_mostly = ~0;
+u32 amd_iommu_max_pasid __read_mostly = ~0;
+EXPORT_SYMBOL(amd_iommu_max_pasid);
bool amd_iommu_v2_present __read_mostly;
bool amd_iommu_pc_present __read_mostly;
@@ -1231,14 +1232,14 @@ static int iommu_init_pci(struct amd_iommu *iommu)
if (iommu_feature(iommu, FEATURE_GT)) {
int glxval;
- u32 pasids;
- u64 shift;
+ u32 max_pasid;
+ u64 pasmax;
- shift = iommu->features & FEATURE_PASID_MASK;
- shift >>= FEATURE_PASID_SHIFT;
- pasids = (1 << shift);
+ pasmax = iommu->features & FEATURE_PASID_MASK;
+ pasmax >>= FEATURE_PASID_SHIFT;
+ max_pasid = (1 << (pasmax + 1)) - 1;
- amd_iommu_max_pasids = min(amd_iommu_max_pasids, pasids);
+ amd_iommu_max_pasid = min(amd_iommu_max_pasid, max_pasid);
glxval = iommu->features & FEATURE_GLXVAL_MASK;
glxval >>= FEATURE_GLXVAL_SHIFT;
diff --git a/drivers/iommu/amd_iommu_types.h b/drivers/iommu/amd_iommu_types.h
index e400fbe..f7ab2d2 100644
--- a/drivers/iommu/amd_iommu_types.h
+++ b/drivers/iommu/amd_iommu_types.h
@@ -98,8 +98,6 @@
#define FEATURE_GLXVAL_SHIFT 14
#define FEATURE_GLXVAL_MASK (0x03ULL << FEATURE_GLXVAL_SHIFT)
-#define PASID_MASK 0x000fffff
-
/* MMIO status bits */
#define MMIO_STATUS_EVT_INT_MASK (1 << 1)
#define MMIO_STATUS_COM_WAIT_INT_MASK (1 << 2)
@@ -696,8 +694,8 @@ extern unsigned long *amd_iommu_pd_alloc_bitmap;
*/
extern u32 amd_iommu_unmap_flush;
-/* Smallest number of PASIDs supported by any IOMMU in the system */
-extern u32 amd_iommu_max_pasids;
+/* Smallest max PASID supported by any IOMMU in the system */
+extern u32 amd_iommu_max_pasid;
extern bool amd_iommu_v2_present;
diff --git a/drivers/iommu/amd_iommu_v2.c b/drivers/iommu/amd_iommu_v2.c
index 5208828..cd328e9 100644
--- a/drivers/iommu/amd_iommu_v2.c
+++ b/drivers/iommu/amd_iommu_v2.c
@@ -760,7 +760,7 @@ int amd_iommu_init_device(struct pci_dev *pdev, int pasids)
if (!amd_iommu_v2_supported())
return -ENODEV;
- if (pasids <= 0 || pasids > (PASID_MASK + 1))
+ if (pasids <= 0 || pasids > (amd_iommu_max_pasid + 1))
return -EINVAL;
devid = device_id(pdev);
--
1.7.10.4
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] iommu/amd: Fix logics to determine and checking max PASID
2014-03-05 19:01 [PATCH] iommu/amd: Fix logics to determine and checking max PASID suravee.suthikulpanit
@ 2014-03-05 22:35 ` Joerg Roedel
2014-03-05 22:46 ` Suravee Suthikulanit
2014-03-05 23:08 ` Suravee Suthikulanit
0 siblings, 2 replies; 4+ messages in thread
From: Joerg Roedel @ 2014-03-05 22:35 UTC (permalink / raw)
To: suravee.suthikulpanit; +Cc: iommu, linux-kernel, kim.naru, jay.cornwall
On Wed, Mar 05, 2014 at 01:01:08PM -0600, suravee.suthikulpanit@amd.com 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] iommu/amd: Fix logics to determine and checking max PASID
2014-03-05 22:35 ` Joerg Roedel
@ 2014-03-05 22:46 ` Suravee Suthikulanit
2014-03-05 23:08 ` Suravee Suthikulanit
1 sibling, 0 replies; 4+ messages in thread
From: Suravee Suthikulanit @ 2014-03-05 22:46 UTC (permalink / raw)
To: Joerg Roedel; +Cc: iommu, linux-kernel, kim.naru, jay.cornwall
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@amd.com 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
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] iommu/amd: Fix logics to determine and checking max PASID
2014-03-05 22:35 ` Joerg Roedel
2014-03-05 22:46 ` Suravee Suthikulanit
@ 2014-03-05 23:08 ` Suravee Suthikulanit
1 sibling, 0 replies; 4+ messages in thread
From: Suravee Suthikulanit @ 2014-03-05 23:08 UTC (permalink / raw)
To: Joerg Roedel; +Cc: iommu, linux-kernel, kim.naru, jay.cornwall
On 3/5/2014 4:35 PM, Joerg Roedel wrote:
>> - cmd->data[1] = pasid & PASID_MASK;
>> >+ cmd->data[1] = pasid & amd_iommu_max_pasid;
> ... masking out the other bits is redundant.
>
>
> Joerg
Agree. I can take out the masking stuff here, but I think we should be
using the amd_iommu_max_pasid instead of hard coded PASID_MASK for the rest.
Suravee
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-03-05 23:08 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-05 19:01 [PATCH] iommu/amd: Fix logics to determine and checking max PASID suravee.suthikulpanit
2014-03-05 22:35 ` Joerg Roedel
2014-03-05 22:46 ` Suravee Suthikulanit
2014-03-05 23:08 ` Suravee Suthikulanit
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox