From: Andrew Cooper <andrew.cooper3@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>, Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Huaitong Han <huaitong.han@intel.com>, Tim Deegan <tim@xen.org>,
Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: Xen PV PTE ABI (or lack thereof)
Date: Thu, 21 Jan 2016 14:37:19 +0000 [thread overview]
Message-ID: <56A0ED1F.90603@citrix.com> (raw)
In-Reply-To: <56A0EB42.1050003@citrix.com>
On 21/01/16 14:29, David Vrabel wrote:
> On 21/01/16 13:17, Andrew Cooper wrote:
>> As we see with the Protection Key feature, newer hardware feature start
>> using bits which were previously software available, and we absolutely
>> don't want to be in a position where our ABI prevents us from ever
>> supporting a new feature.
> I don't see a problem in not supporting new features in /PV/ guests.
I know you want to kill PV guests. I am not going to deliberately
cripple PV guests in an attempt to achieve that goal.
>
> I think we should document the PV ABI as-is. i.e., that these two PTE
> bits are not available for PV guest use.
This is already known to break some guests. It shouldn't stay as it
currently is.
~Andrew
next prev parent reply other threads:[~2016-01-21 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 20:10 Xen PV PTE ABI (or lack thereof) Andrew Cooper
2016-01-21 11:07 ` Jan Beulich
2016-01-21 11:16 ` Andrew Cooper
2016-01-21 12:59 ` Jan Beulich
2016-01-21 13:17 ` Andrew Cooper
2016-01-21 13:55 ` Jan Beulich
2016-01-21 15:10 ` Andrew Cooper
2016-01-21 14:29 ` David Vrabel
2016-01-21 14:37 ` Andrew Cooper [this message]
2016-01-21 14:53 ` David Vrabel
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=56A0ED1F.90603@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=huaitong.han@intel.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.