From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [RFC PATCH] x86_64,entry,xen: Do not invoke espfix64 on Xen
Date: Tue, 15 Jul 2014 15:04:06 -0400 [thread overview]
Message-ID: <53C57B26.1020105@oracle.com> (raw)
In-Reply-To: <53C57A4E.1060000@zytor.com>
On 07/15/2014 03:00 PM, H. Peter Anvin wrote:
> On 07/15/2014 12:00 PM, Boris Ostrovsky wrote:
>> One way or the other we need to disable espfix64 on PV --- I discovered
>> that one of Peter's tests crashes the hypervisor.
>>
> You do realize that that means you have bigger problems than just
> espfix, right?
Yes.
-boris
next prev parent reply other threads:[~2014-07-15 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 16:23 [RFC PATCH] x86_64,entry,xen: Do not invoke espfix64 on Xen Andy Lutomirski
2014-07-15 17:19 ` Boris Ostrovsky
2014-07-15 17:22 ` Andy Lutomirski
2014-07-15 19:00 ` Boris Ostrovsky
2014-07-15 19:00 ` H. Peter Anvin
2014-07-15 19:04 ` Boris Ostrovsky [this message]
2014-07-15 19:02 ` Andy Lutomirski
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=53C57B26.1020105@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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