All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Lalancette <clalance@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Print Guest VMCS state on vmexit failure
Date: Tue, 20 Oct 2009 10:42:24 +0200	[thread overview]
Message-ID: <4ADD77F0.6010102@redhat.com> (raw)
In-Reply-To: <4ADD70CB.10109@redhat.com>

Avi Kivity wrote:
> On 10/20/2009 04:50 PM, Chris Lalancette wrote:
>> If we fail to handle a VMEXIT for some reason, print out a lot
>> more debugging information about the state of the GUEST VMCS
>> area.  This does not fix a bug, but helps a lot when trying to
>> track down the cause of a VMEXIT/VMENTRY failure.
>>    
> 
> register state can just as easily be examined in the qemu monitor.
> 

Ah, true.  OK, forget this patch.

-- 
Chris Lalancette

  reply	other threads:[~2009-10-20  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  7:50 [PATCH] Print Guest VMCS state on vmexit failure Chris Lalancette
2009-10-20  7:57 ` Gleb Natapov
2009-10-20  8:01   ` Chris Lalancette
2009-10-20  8:11 ` Avi Kivity
2009-10-20  8:42   ` Chris Lalancette [this message]
2009-10-20  8:55     ` Nikola Ciprich
2009-10-20  8:57       ` Chris Lalancette
2009-10-20  9:08         ` Avi Kivity

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=4ADD77F0.6010102@redhat.com \
    --to=clalance@redhat.com \
    --cc=avi@redhat.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.