From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, glin@suse.de,
agraf@suse.de, brogers@suse.de, afaerber@suse.de,
lnussel@suse.de, edk2-devel@lists.sf.net, stable@vger.kernel.org,
gleb@redhat.com
Subject: Re: [PATCH] KVM: mmu: allow page tables to be in read-only slots
Date: Mon, 02 Sep 2013 17:20:15 +0800 [thread overview]
Message-ID: <5224584F.6010409@linux.vnet.ibm.com> (raw)
In-Reply-To: <1377866497-3866-1-git-send-email-pbonzini@redhat.com>
On 08/30/2013 08:41 PM, Paolo Bonzini wrote:
> Page tables in a read-only memory slot will currently cause a triple
> fault because the page walker uses gfn_to_hva and it fails on such a slot.
>
> OVMF uses such a page table; however, real hardware seems to be fine with
> that as long as the accessed/dirty bits are set. Save whether the slot
> is readonly, and later check it when updating the accessed and dirty bits.
Paolo, do you know why OVMF is using readonly memory like this?
AFAIK, The fault trigged by this kind of access can hardly be fixed by
userspace since the fault is trigged by pagetable walking not by the current
instruction. Do you have any idea to let uerspace emulate it properly?
next prev parent reply other threads:[~2013-09-02 9:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 12:41 [PATCH] KVM: mmu: allow page tables to be in read-only slots Paolo Bonzini
2013-09-01 9:17 ` Gleb Natapov
2013-09-02 9:42 ` Xiao Guangrong
2013-09-02 9:49 ` Gleb Natapov
2013-09-02 10:05 ` Xiao Guangrong
2013-09-02 10:11 ` Gleb Natapov
2013-09-02 15:58 ` Paolo Bonzini
2013-09-02 16:27 ` Gleb Natapov
2013-10-14 15:28 ` Paolo Bonzini
2013-09-02 9:20 ` Xiao Guangrong [this message]
2013-09-02 9:25 ` Gleb Natapov
2013-09-02 10:00 ` Xiao Guangrong
2013-09-02 10:07 ` Gleb Natapov
2013-09-02 15:56 ` Paolo Bonzini
2013-09-02 16:26 ` Gleb Natapov
2013-09-02 16:00 ` Paolo Bonzini
2013-09-02 16:16 ` Gleb Natapov
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=5224584F.6010409@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=brogers@suse.de \
--cc=edk2-devel@lists.sf.net \
--cc=gleb@redhat.com \
--cc=glin@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lnussel@suse.de \
--cc=pbonzini@redhat.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox