All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] KVM: VMX: report internal error for MMIO #PF due to delivery event
Date: Thu, 18 Oct 2012 16:30:44 +0200	[thread overview]
Message-ID: <50801294.2020007@redhat.com> (raw)
In-Reply-To: <507E4696.7020007@linux.vnet.ibm.com>

On 10/17/2012 07:48 AM, Xiao Guangrong wrote:
> The #PF with PFEC.RSV = 1 indicates that the guest is accessing MMIO, we
> can not fix it if it is caused by delivery event. Reporting internal error
> for this case

Applied, thanks.


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

      reply	other threads:[~2012-10-18 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  5:46 [PATCH 1/2] KVM: VMX: report internal error for the unhandleable event Xiao Guangrong
2012-10-17  5:48 ` [PATCH 2/2] KVM: VMX: report internal error for MMIO #PF due to delivery event Xiao Guangrong
2012-10-18 14:30   ` Avi Kivity [this message]

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=50801294.2020007@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=xiaoguangrong@linux.vnet.ibm.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.