From: "Alex Bennée" <alex.bennee@linaro.org>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, peterx@redhat.com, peter.maydell@linaro.org,
qemu-devel@nongnu.org
Subject: Re: [PATCH V2] intel_iommu: refine iotlb hash calculation
Date: Wed, 12 Apr 2023 09:41:56 +0100 [thread overview]
Message-ID: <87bkjtpk2n.fsf@linaro.org> (raw)
In-Reply-To: <20230412073510.7158-1-jasowang@redhat.com>
Jason Wang <jasowang@redhat.com> writes:
> Commit 1b2b12376c8 ("intel-iommu: PASID support") takes PASID into
> account when calculating iotlb hash like:
>
> static guint vtd_iotlb_hash(gconstpointer v)
> {
> const struct vtd_iotlb_key *key = v;
>
> return key->gfn | ((key->sid) << VTD_IOTLB_SID_SHIFT) |
> (key->level) << VTD_IOTLB_LVL_SHIFT |
> (key->pasid) << VTD_IOTLB_PASID_SHIFT;
> }
>
> This turns out to be problematic since:
>
> - the shift will lose bits if not converting to uint64_t
> - level should be off by one in order to fit into 2 bits
> - VTD_IOTLB_PASID_SHIFT is 30 but PASID is 20 bits which will waste
> some bits
> - the hash result is uint64_t so we will lose bits when converting to
> guint
>
> So this patch fixes them by
>
> - converting the keys into uint64_t before doing the shift
> - off level by one to make it fit into two bits
> - change the sid, lvl and pasid shift to 26, 42 and 44 in order to
> take the full width of uint64_t
> - perform an XOR to the top 32bit with the bottom 32bit for the final
> result to fit guint
>
> Fixes: Coverity CID 1508100
> Fixes: 1b2b12376c8 ("intel-iommu: PASID support")
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> Changes since V1:
> - perform XOR to avoid losing bits when converting to gint
> ---
> hw/i386/intel_iommu.c | 9 +++++----
> hw/i386/intel_iommu_internal.h | 6 +++---
> 2 files changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index a62896759c..94d52f4205 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -64,8 +64,8 @@ struct vtd_as_key {
> struct vtd_iotlb_key {
> uint64_t gfn;
> uint32_t pasid;
> - uint32_t level;
> uint16_t sid;
> + uint8_t level;
> };
>
> static void vtd_address_space_refresh_all(IntelIOMMUState *s);
> @@ -221,10 +221,11 @@ static gboolean vtd_iotlb_equal(gconstpointer v1, gconstpointer v2)
> static guint vtd_iotlb_hash(gconstpointer v)
> {
> const struct vtd_iotlb_key *key = v;
> + uint64_t hash64 = key->gfn | ((uint64_t)(key->sid) << VTD_IOTLB_SID_SHIFT) |
> + (uint64_t)(key->level - 1) << VTD_IOTLB_LVL_SHIFT |
> + (uint64_t)(key->pasid) << VTD_IOTLB_PASID_SHIFT;
>
> - return key->gfn | ((key->sid) << VTD_IOTLB_SID_SHIFT) |
> - (key->level) << VTD_IOTLB_LVL_SHIFT |
> - (key->pasid) << VTD_IOTLB_PASID_SHIFT;
> + return (guint)((hash64 >> 32) ^ (hash64 & 0xffffffffU));
Have you measured the distribution this hash gives you? Otherwise
consider using the qemu_xxhash() functions to return a well distributed
32 bit hash value.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-04-12 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 7:35 [PATCH V2] intel_iommu: refine iotlb hash calculation Jason Wang
2023-04-12 8:41 ` Alex Bennée [this message]
2023-04-13 3:33 ` Jason Wang
2023-04-13 9:58 ` Alex Bennée
2023-04-13 14:32 ` Peter Xu
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=87bkjtpk2n.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).