From: Auger Eric <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
Jason Wang <jasowang@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Peter Xu <peterx@redhat.com>,
vivek.gautam@arm.com, qemu-arm <qemu-arm@nongnu.org>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eric Auger <eric.auger.pro@gmail.com>
Subject: Re: [PATCH v2 4/7] hw/arm/smmu-common: Fix smmu_iotlb_inv_iova when asid is not set
Date: Tue, 9 Mar 2021 09:37:29 +0100 [thread overview]
Message-ID: <4626b8d9-8b0f-c81c-56a2-331957dfd81a@redhat.com> (raw)
In-Reply-To: <CAFEAcA_ZTJUD1SfbAX07uk+WceO_NvqE_i+NrHF13bAOmfF3nw@mail.gmail.com>
Hi Peter,
On 3/8/21 5:37 PM, Peter Maydell wrote:
> On Thu, 25 Feb 2021 at 09:15, Eric Auger <eric.auger@redhat.com> wrote:
>>
>> If the asid is not set, do not attempt to locate the key directly
>> as all inserted keys have a valid asid.
>>
>> Use g_hash_table_foreach_remove instead.
>>
>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>> ---
>> hw/arm/smmu-common.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/arm/smmu-common.c b/hw/arm/smmu-common.c
>> index 405d5c5325..e9ca3aebb2 100644
>> --- a/hw/arm/smmu-common.c
>> +++ b/hw/arm/smmu-common.c
>> @@ -151,7 +151,7 @@ inline void
>> smmu_iotlb_inv_iova(SMMUState *s, int asid, dma_addr_t iova,
>> uint8_t tg, uint64_t num_pages, uint8_t ttl)
>> {
>> - if (ttl && (num_pages == 1)) {
>> + if (ttl && (num_pages == 1) && (asid >= 0)) {
>> SMMUIOTLBKey key = smmu_get_iotlb_key(asid, iova, tg, ttl);
>>
>> g_hash_table_remove(s->iotlb, &key);
>
> Do we also need to avoid the remove-by-key codepath if
> the tg is not set ?
when TG is not set, TTL is res0 so I think it is safe.
Thanks
Eric
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2021-03-09 8:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 9:14 [PATCH v2 0/7] Some vIOMMU fixes Eric Auger
2021-02-25 9:14 ` [PATCH v2 1/7] intel_iommu: Fix mask may be uninitialized in vtd_context_device_invalidate Eric Auger
2021-02-25 10:08 ` Philippe Mathieu-Daudé
2021-02-25 16:33 ` Auger Eric
2021-02-25 15:41 ` Peter Xu
2021-02-25 9:14 ` [PATCH v2 2/7] dma: Introduce dma_aligned_pow2_mask() Eric Auger
2021-02-25 15:56 ` Peter Xu
2021-03-08 16:34 ` Peter Maydell
2021-02-25 9:14 ` [PATCH v2 3/7] virtio-iommu: Handle non power of 2 range invalidations Eric Auger
2021-02-25 16:01 ` Peter Xu
2021-02-25 9:14 ` [PATCH v2 4/7] hw/arm/smmu-common: Fix smmu_iotlb_inv_iova when asid is not set Eric Auger
2021-03-08 16:37 ` Peter Maydell
2021-03-09 8:37 ` Auger Eric [this message]
2021-02-25 9:14 ` [PATCH v2 5/7] hw/arm/smmuv3: Enforce invalidation on a power of two range Eric Auger
2021-03-08 16:44 ` Peter Maydell
2021-02-25 9:14 ` [PATCH v2 6/7] hw/arm/smmuv3: Fix SMMU_CMD_CFGI_STE_RANGE handling Eric Auger
2021-03-08 16:41 ` Peter Maydell
2021-02-25 9:14 ` [PATCH v2 7/7] hw/arm/smmuv3: Uniformize sid traces Eric Auger
2021-02-25 10:11 ` Philippe Mathieu-Daudé
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=4626b8d9-8b0f-c81c-56a2-331957dfd81a@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=vivek.gautam@arm.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;
as well as URLs for NNTP newsgroup(s).