From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Tim Deegan <tim@xen.org>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/HVM: prevent infinite VM entry retries
Date: Thu, 27 Nov 2014 12:58:01 +0000 [thread overview]
Message-ID: <54772DE9020000780004B2DF@mail.emea.novell.com> (raw)
In-Reply-To: <54771D0A.2010901@citrix.com>
>>> On 27.11.14 at 13:46, <andrew.cooper3@citrix.com> wrote:
> On 27/11/14 12:39, Jan Beulich wrote:
>> if ( unlikely(exit_reason == VMEXIT_INVALID) )
>> {
>
> I think it would be good to retain the printk here from previous
> versions of the patch, specifically identifies the below vmcb dump as
> caused by a failed vmentry. As it stands, it is a vmcb dump with no
> other context.
>
> Either way, Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
I meant to do so and then forgot. Added to the to be committed
version.
Jan
prev parent reply other threads:[~2014-11-27 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 12:39 [PATCH] x86/HVM: prevent infinite VM entry retries Jan Beulich
2014-11-27 12:46 ` Andrew Cooper
2014-11-27 12:58 ` Jan Beulich [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=54772DE9020000780004B2DF@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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.