From: Paolo Bonzini <pbonzini@redhat.com>
To: nick <xerofoify@gmail.com>, gleb@kernel.org
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Fix Mes in emulate.c
Date: Wed, 19 Nov 2014 10:29:52 +0100 [thread overview]
Message-ID: <546C6310.305@redhat.com> (raw)
In-Reply-To: <546C0BB6.5010109@gmail.com>
On 19/11/2014 04:17, nick wrote:
> Greeting Gleb and other maintainers, I known this may not be that
> easy to fix but if someone is willing to send me the fault addresses
> or a hardware manual in order to fix and add the correct return
> correct addresses for the fix mes in the emulate.c for the x86
> architecture.
Hi Nick,
I need to check more closely, but I think the FIXMEs have already been
fixed. The address is already stored by arch/x86/kvm/paging_tmpl.h's
FNAME(walk_addr_generic) in walker->fault.address, and propagated by
FNAME(gva_to_gpa).
You can send a patch to remove them.
Paolo
parent reply other threads:[~2014-11-19 9:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <546C0BB6.5010109@gmail.com>]
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=546C6310.305@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.org \
--cc=xerofoify@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).