From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, kvm <kvm@vger.kernel.org>
Subject: Re: KVM x86: Infinite loop on updating accessed bit in r/o page table
Date: Tue, 25 Feb 2014 15:11:37 +0100 [thread overview]
Message-ID: <530CA499.9070401@redhat.com> (raw)
In-Reply-To: <530C7D19.2000409@siemens.com>
Il 25/02/2014 12:23, Jan Kiszka ha scritto:
>> > even though OVMF sets the accessed/dirty bits so it's not exactly the same
>> > scenario.
>> >
>> > Note that NPT simply does not support this. Page tables must be writable
>> > in the NPT page tables, according to the AMD manual.
> We could still emulate the instruction in such a case to get beyond the
> write fault. Slow but more correct, I suppose.
They must be writable always, even if A=D=1. So the only solution would
be to emulate everything that puts page tables in ROMs, which is really
too slow to be viable. We're really talking 50-100 times slower than
bare metal.
Paolo
prev parent reply other threads:[~2014-02-25 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 18:29 KVM x86: Infinite loop on updating accessed bit in r/o page table Jan Kiszka
2014-02-25 10:57 ` Paolo Bonzini
2014-02-25 11:23 ` Jan Kiszka
2014-02-25 14:11 ` Paolo Bonzini [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=530CA499.9070401@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.