From: Avi Kivity <avi@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: jdike@addtoit.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, aarcange@redhat.com,
mtosatti@redhat.com
Subject: Re: [PATCH] emulate accessed bit for EPT
Date: Mon, 08 Feb 2010 12:27:24 +0200 [thread overview]
Message-ID: <4B6FE70C.6020107@redhat.com> (raw)
In-Reply-To: <20100203161103.11e2b572@annuminas.surriel.com>
On 02/03/2010 11:11 PM, Rik van Riel wrote:
> Currently KVM pretends that pages with EPT mappings never got
> accessed. This has some side effects in the VM, like swapping
> out actively used guest pages and needlessly breaking up actively
> used hugepages.
>
> We can avoid those very costly side effects by emulating the
> accessed bit for EPT PTEs, which should only be slightly costly
> because pages pass through page_referenced infrequently.
>
> TLB flushing is taken care of by kvm_mmu_notifier_clear_flush_young().
>
> This seems to help prevent KVM guests from being swapped out when
> they should not on my system.
>
>
Applied, thanks.
>
> - /* always return old for EPT */
> + /*
> + * Emulate the accessed bit for EPT, by checking if this page has
> + * an EPT mapping, and clearing it if it does. On the next access,
> + * a new EPT mapping will be established.
> + * This has some overhead, but not as much as the cost of swapping
> + * out actively used pages or breaking up actively used hugepages.
> + */
> if (!shadow_accessed_mask)
> - return 0;
> + return kvm_unmap_rmapp(kvm, rmapp, data);
>
This could be optimized by using a software-available bit for 'present'
and the rwx bits for young, that is:
(present, rwx) -> the page is present and recently accessed, will not
cause EPT violation
(present, !rwx) -> page is present but old, will cause EPT violation
but not rmap games and get_user_pages_fast().
However that's best done later if ever.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-02-08 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 21:11 [PATCH] emulate accessed bit for EPT Rik van Riel
2010-02-04 4:12 ` Balbir Singh
2010-02-04 13:40 ` Rik van Riel
2010-02-04 15:30 ` Balbir Singh
2010-02-04 15:41 ` Rik van Riel
2010-02-04 15:52 ` Balbir Singh
2010-02-04 17:47 ` Andrea Arcangeli
2010-02-05 17:34 ` Marcelo Tosatti
2010-02-05 18:14 ` Andrea Arcangeli
2010-02-07 19:21 ` Marcelo Tosatti
2010-02-04 16:17 ` Jeff Dike
2010-02-08 10:27 ` Avi Kivity [this message]
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=4B6FE70C.6020107@redhat.com \
--to=avi@redhat.com \
--cc=aarcange@redhat.com \
--cc=jdike@addtoit.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.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