From: Paolo Bonzini <pbonzini@redhat.com>
To: Arthur Chunqi Li <yzt356@gmail.com>
Cc: kvm <kvm@vger.kernel.org>, Jan Kiszka <jan.kiszka@web.de>
Subject: Re: Calling to kvm_mmu_load
Date: Tue, 29 Oct 2013 13:55:58 +0100 [thread overview]
Message-ID: <526FB05E.1070204@redhat.com> (raw)
In-Reply-To: <CABpY8MLX0=YFtJwCJcFhZStSedAgCQpvNvQ44GFQit=0+YNc-g@mail.gmail.com>
Il 29/10/2013 06:39, Arthur Chunqi Li ha scritto:
> What is the dirty page tracking code path? I find a obsoleted flag
> "dirty_page_log_all" in the very previous codes, but I cannot get the
> most recent version of tracking dirty pages.
Basically everything that accesses the dirty_bitmap field of struct
kvm_memory_slot is involved. It all starts when the
KVM_SET_USER_MEMORY_REGION ioctl is called with the
KVM_MEM_LOG_DIRTY_PAGES flag set.
> Besides, I noticed that memory management in KVM uses the mechanism
> with "struct kvm_memory_slot". How is kvm_memory_slot used with the
> cooperation of Linux memory management?
kvm_memory_slot just maps a host userspace address range to a guest
physical address range. Cooperation with Linux memory management is
done with the Linux MMU notifiers. MMU notifiers let KVM know that a
page has been swapped out, and KVM reacts by invalidating the shadow
page tables for the corresponding guest physical address.
Paolo
next prev parent reply other threads:[~2013-10-29 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 7:56 Calling to kvm_mmu_load Arthur Chunqi Li
2013-10-23 6:21 ` Paolo Bonzini
2013-10-24 7:55 ` Arthur Chunqi Li
2013-10-25 0:43 ` Paolo Bonzini
2013-10-29 5:39 ` Arthur Chunqi Li
2013-10-29 12:55 ` Paolo Bonzini [this message]
2013-10-30 11:39 ` Arthur Chunqi Li
2013-10-30 11:44 ` Paolo Bonzini
2013-10-31 8:05 ` Arthur Chunqi Li
2013-10-31 9:52 ` Paolo Bonzini
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=526FB05E.1070204@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=yzt356@gmail.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).