|
| From: | Paolo Bonzini |
| Subject: | Re: [PATCH RESEND 2/2] memory: Add tracepoint for dirty sync |
| Date: | Mon, 20 Sep 2021 14:59:22 +0200 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 17/08/21 18:05, Peter Xu wrote:
I'm also wondering whether kvm-smram needs a whole bitmap as I don't know what RAM would be touched within system manager mode (as I thought it should only touch a very limited range and should be defined somewhere), but that's off-topic.
The kvm-smram dirty bitmap will include all memory touched while the SMM address space is in effect, so not just SMRAM. The two KVM dirty bitmaps end up in just one QEMU dirty bitmap (the one with id DIRTY_MEMORY_MIGRATION) but they are separate at the kernel level.
Paolo
| [Prev in Thread] | Current Thread | [Next in Thread] |