All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Add missing emulation failure report in kvm_mmu_page_fault()
Date: Sun, 17 Jan 2010 14:34:23 +0200	[thread overview]
Message-ID: <4B5303CF.2070508@redhat.com> (raw)
In-Reply-To: <1263545063-10285-1-git-send-email-sheng@linux.intel.com>

On 01/15/2010 10:44 AM, Sheng Yang wrote:
> Currently we only have handle_invalid_guest_state() reported emulation failure...
>
> Signed-off-by: Sheng Yang<sheng@linux.intel.com>
> ---
>   arch/x86/kvm/mmu.c |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 4f5508c..037e52a 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -2791,6 +2791,7 @@ int kvm_mmu_page_fault(struct kvm_vcpu *vcpu, gva_t cr2, u32 error_code)
>   		++vcpu->stat.mmio_exits;
>   		return 0;
>   	case EMULATE_FAIL:
> +		kvm_report_emulation_failure(vcpu, "emulation failure");
>   		vcpu->run->exit_reason = KVM_EXIT_INTERNAL_ERROR;
>   		vcpu->run->internal.suberror = KVM_INTERNAL_ERROR_EMULATION;
>   		vcpu->run->internal.ndata = 0;
>    

This is intentional - instead of spamming dmesg, we exit with an 
internal error.  Modern qemu-kvm will halt and allow the user to inspect 
the guest with the built-in disassembler.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-01-17 12:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15  8:44 [PATCH] KVM: Add missing emulation failure report in kvm_mmu_page_fault() Sheng Yang
2010-01-17 12:34 ` Avi Kivity [this message]
2010-01-18  9:32   ` Sheng Yang
2010-01-18 11:32     ` Avi Kivity
2010-01-19  3:06       ` Sheng Yang
2010-01-19  7:54         ` Avi Kivity
2010-01-19  7:57           ` Gleb Natapov
2010-01-19  8:05             ` Sheng Yang

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=4B5303CF.2070508@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.intel.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 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.