qemu-arm
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] hw/arm/smmuv3: add device properties to disable cached iotlb


From: chenxiang (M)
Subject: Re: [RFC] hw/arm/smmuv3: add device properties to disable cached iotlb
Date: Wed, 4 Aug 2021 16:51:07 +0800
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0



在 2021/8/4 16:45, Peter Maydell 写道:
On Wed, 4 Aug 2021 at 09:41, chenxiang <chenxiang66@hisilicon.com> wrote:
From: Xiang Chen <chenxiang66@hisilicon.com>

It splits invalidations into ^2 range invalidations in the patch
6d9cd115b(" hw/arm/smmuv3: Enforce invalidation on a power of two range").
So for some scenarios such as the size of invalidation is not ^2 range
invalidation, it costs more time to invalidate.
Currently smmuv3_translate is rarely used (i only see it is used when
binding msi), so i think maybe we can disable cached iotlb to promote
efficiency of invalidation. So add device property disable_cached_iotlb
to disable cached iotlb, and then we can send non-^2 range invalidation
directly.
Use tool dma_map_benchmark to have a test on the latency of unmap,
and we can see it promotes much on unmap when the size of invalidation
is not ^2 range invalidation (such as g = 7/15/31/511):

Hi. Can you send all patches to the qemu-devel list, please (you can
cc qemu-arm if you like)? The automated patch-handling tools and some
developers only read qemu-devel.
https://wiki.qemu.org/Contribute/SubmitAPatch has some more detail
on sending patches.

Ok, thanks for your remind. I will resend it to qemu-devel list.


thanks
-- PMM

.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]