From: Lu Baolu <baolu.lu@linux.intel.com>
To: Zenghui Yu <yuzenghui@huawei.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: baolu.lu@linux.intel.com, dwmw2@infradead.org, joro@8bytes.org,
will@kernel.org, jacob.jun.pan@linux.intel.com,
eric.auger@redhat.com, yi.l.liu@intel.com, kevin.tian@intel.com,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH] iommu/vt-d: Fix status code for Allocate/Free PASID command
Date: Mon, 1 Mar 2021 08:44:39 +0800 [thread overview]
Message-ID: <30c18a6d-fd0f-6e63-c231-d6f068410342@linux.intel.com> (raw)
In-Reply-To: <20210227073909.432-1-yuzenghui@huawei.com>
On 2/27/21 3:39 PM, Zenghui Yu wrote:
> As per Intel vt-d spec, Rev 3.0 (section 10.4.45 "Virtual Command Response
> Register"), the status code of "No PASID available" error in response to
> the Allocate PASID command is 2, not 1. The same for "Invalid PASID" error
> in response to the Free PASID command.
>
> We will otherwise see confusing kernel log under the command failure from
> guest side. Fix it.
>
> Fixes: 24f27d32ab6b ("iommu/vt-d: Enlightened PASID allocation")
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
> drivers/iommu/intel/pasid.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iommu/intel/pasid.h b/drivers/iommu/intel/pasid.h
> index 97dfcffbf495..444c0bec221a 100644
> --- a/drivers/iommu/intel/pasid.h
> +++ b/drivers/iommu/intel/pasid.h
> @@ -30,8 +30,8 @@
> #define VCMD_VRSP_IP 0x1
> #define VCMD_VRSP_SC(e) (((e) >> 1) & 0x3)
> #define VCMD_VRSP_SC_SUCCESS 0
> -#define VCMD_VRSP_SC_NO_PASID_AVAIL 1
> -#define VCMD_VRSP_SC_INVALID_PASID 1
> +#define VCMD_VRSP_SC_NO_PASID_AVAIL 2
> +#define VCMD_VRSP_SC_INVALID_PASID 2
> #define VCMD_VRSP_RESULT_PASID(e) (((e) >> 8) & 0xfffff)
> #define VCMD_CMD_OPERAND(e) ((e) << 8)
> /*
>
Thanks a lot for catching this.
Acked-by: Lu Baolu <baolu.lu@linux.intel.com>
Best regards,
baolu
next prev parent reply other threads:[~2021-03-01 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 7:39 [PATCH] iommu/vt-d: Fix status code for Allocate/Free PASID command Zenghui Yu
2021-03-01 0:44 ` Lu Baolu [this message]
2021-03-04 12:32 ` Joerg Roedel
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=30c18a6d-fd0f-6e63-c231-d6f068410342@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wanghaibin.wang@huawei.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yuzenghui@huawei.com \
/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