From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: Re: [Draft B] Boot ABI for HVM guests without a device-model
Date: Wed, 26 Aug 2015 17:38:13 +0200 [thread overview]
Message-ID: <55DDDD65.1000207@citrix.com> (raw)
In-Reply-To: <55DDAEA2.8000104@citrix.com>
El 26/08/15 a les 14.18, Andrew Cooper ha escrit:
> On 26/08/15 12:48, Roger Pau Monné wrote:
>> ELFNOTE(Xen, XEN_ELFNOTE_FEATURES, .asciz, "writable_descriptor_tables|auto_translated_physmap|supervisor_mode_kernel")
>> ELFNOTE(Xen, XEN_ELFNOTE_SUPPORTED_FEATURES, .long ((1 << XENFEAT_writable_page_tables) | \
>> (1 << XENFEAT_auto_translated_physmap) | \
>> (1 << XENFEAT_supervisor_mode_kernel) | \
>> (1 << XENFEAT_hvm_callback_vector))
>
> Can we see about fixing the overloading of XENFEAT_supervisor_mode_kernel ?
>
> IMO it should be relegated to history. It was an old,
> not-fully-implemented pv feature (subsequently removed completely) which
> is not relevant to HVM guests.
Maybe we can get rid of both XEN_ELFNOTE_FEATURES and
XEN_ELFNOTE_SUPPORTED_FEATURES if the kernel only supports PVH?
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-08-26 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 11:48 [Draft B] Boot ABI for HVM guests without a device-model Roger Pau Monné
2015-08-26 12:00 ` Jan Beulich
2015-08-26 12:12 ` Andrew Cooper
2015-08-26 14:44 ` Roger Pau Monné
2015-08-27 8:04 ` Jan Beulich
2015-08-27 9:43 ` Andrew Cooper
2015-08-27 9:57 ` Roger Pau Monné
2015-08-27 11:08 ` Jan Beulich
2015-08-26 12:18 ` Andrew Cooper
2015-08-26 15:38 ` Roger Pau Monné [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=55DDDD65.1000207@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=elena.ufimtseva@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).