From: Avi Kivity <avi@redhat.com>
To: kvm@vger.kernel.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [PATCH 0/2] Fix walk_addr() page fault error codes
Date: Tue, 6 Jul 2010 16:49:34 +0300 [thread overview]
Message-ID: <1278424176-15310-1-git-send-email-avi@redhat.com> (raw)
This patchset fixes bugs in page fault error code generation. With the patches
applied, the access.flat unit test now passes with no errors on shadow, npt,
and ept.
Avi Kivity (2):
KVM: MMU: Only indicate a fetch fault in page fault error code if nx
is enabled
KVM: MMU: Keep going on permission error
arch/x86/kvm/paging_tmpl.h | 52 +++++++++++++++++++++++++------------------
1 files changed, 30 insertions(+), 22 deletions(-)
next reply other threads:[~2010-07-06 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 13:49 Avi Kivity [this message]
2010-07-06 13:49 ` [PATCH 1/2] KVM: MMU: Only indicate a fetch fault in page fault error code if nx is enabled Avi Kivity
2010-07-06 13:49 ` [PATCH 2/2] KVM: MMU: Keep going on permission error Avi Kivity
2010-07-07 12:33 ` Jan Kiszka
2010-07-07 12:41 ` Avi Kivity
2010-07-08 11:14 ` Jan Kiszka
2010-07-08 11:19 ` Avi Kivity
2010-07-06 21:17 ` [PATCH 0/2] Fix walk_addr() page fault error codes Marcelo Tosatti
2010-07-07 1:49 ` Xiao Guangrong
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=1278424176-15310-1-git-send-email-avi@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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;
as well as URLs for NNTP newsgroup(s).