Re: [PATCH v3] memory: Optimize replay of guest mapping

2023-04-19 Thread Peter Maydell
On Wed, 19 Apr 2023 at 03:38, Duan, Zhenzhong wrote: > >> The documentation for the replay method of IOMMUMemoryRegionClass > >> says: > >> * The default implementation of memory_region_iommu_replay() is to > >> * call the IOMMU translate method for every page in the address space > >>

RE: [PATCH v3] memory: Optimize replay of guest mapping

2023-04-18 Thread Duan, Zhenzhong
edua...@habkost.net; da...@redhat.com; >phi...@linaro.org >Subject: Re: [PATCH v3] memory: Optimize replay of guest mapping > >On Tue, Apr 18, 2023 at 11:13:57AM +0100, Peter Maydell wrote: >> On Thu, 13 Apr 2023 at 12:12, Zhenzhong Duan > wrote: >> > >> >

Re: [PATCH v3] memory: Optimize replay of guest mapping

2023-04-18 Thread Peter Xu
On Tue, Apr 18, 2023 at 11:13:57AM +0100, Peter Maydell wrote: > On Thu, 13 Apr 2023 at 12:12, Zhenzhong Duan wrote: > > > > On x86, there are two notifiers registered due to vtd-ir memory > > region splitting the entire address space. During replay of the > > address space for each notifier, the

Re: [PATCH v3] memory: Optimize replay of guest mapping

2023-04-18 Thread Peter Maydell
On Thu, 13 Apr 2023 at 12:12, Zhenzhong Duan wrote: > > On x86, there are two notifiers registered due to vtd-ir memory > region splitting the entire address space. During replay of the > address space for each notifier, the whole address space is > scanned which is unnecessary. We only need to

Re: [PATCH v3] memory: Optimize replay of guest mapping

2023-04-13 Thread Peter Xu
On Thu, Apr 13, 2023 at 07:00:19PM +0800, Zhenzhong Duan wrote: > On x86, there are two notifiers registered due to vtd-ir memory > region splitting the entire address space. During replay of the > address space for each notifier, the whole address space is > scanned which is unnecessary. We only