From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, Ian.Jackson@eu.citrix.com
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 06/11] docs: Document the ELF_FEATURES entry
Date: Mon, 25 Mar 2013 10:41:17 -0400 [thread overview]
Message-ID: <1364222482-14697-7-git-send-email-konrad.wilk@oracle.com> (raw)
In-Reply-To: <1364222482-14697-1-git-send-email-konrad.wilk@oracle.com>
Mark-up for inclusion of generated docs.
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
xen/include/public/features.h | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/xen/include/public/features.h b/xen/include/public/features.h
index 5b70418..a149aa6 100644
--- a/xen/include/public/features.h
+++ b/xen/include/public/features.h
@@ -28,6 +28,20 @@
#define __XEN_PUBLIC_FEATURES_H__
/*
+ * `incontents 200 elfnotes_features XEN_ELFNOTE_FEATURES
+ *
+ * The list of all the features the guest supports. They are set by
+ * parsing the XEN_ELFNOTE_FEATURES and XEN_ELFNOTE_SUPPORTED_FEATURES
+ * string. The format is the feature names (as given here without the
+ * "XENFEAT_" prefix) separated by '|' characters.
+ * If a feature is required for the kernel to function then the feature name
+ * must be preceded by a '!' character.
+ *
+ * Note that if XEN_ELFNOTE_SUPPORTED_FEATURES is used, then in the
+ * XENFEAT_dom0 MUST be set if the guest is to be booted as dom0,
+ */
+
+/*
* If set, the guest does not need to write-protect its pagetables, and can
* update them via direct writes.
*/
--
1.8.0.2
next prev parent reply other threads:[~2013-03-25 14:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 14:41 [PATCH] docs/traces Acked patches Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 01/11] trace: Use correct trace class for power management changes Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 02/11] trace: Add trace events for IRQ activities Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 03/11] trace: Add the other variant of do_block Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 04/11] trace: Add reason for NMI exit TRAP Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 05/11] docs: Document the ELF notes Konrad Rzeszutek Wilk
2013-03-25 14:41 ` Konrad Rzeszutek Wilk [this message]
2013-03-25 14:41 ` [PATCH 07/11] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 08/11] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 09/11] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 10/11] docs: Document start_info changes in Xen 4.2 Konrad Rzeszutek Wilk
2013-03-25 14:41 ` [PATCH 11/11] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-03-25 15:13 ` [PATCH] docs/traces Acked patches Jan Beulich
2013-03-25 15:37 ` George Dunlap
2013-03-25 15:48 ` Jan Beulich
2013-03-25 16:43 ` George Dunlap
2013-03-25 19:57 ` Konrad Rzeszutek Wilk
2013-03-25 16:46 ` Konrad Rzeszutek Wilk
2013-03-25 17:20 ` Jan Beulich
2013-03-25 20:04 ` Konrad Rzeszutek Wilk
2013-04-10 9:24 ` Ian Campbell
2013-03-26 16:28 ` Ian Jackson
2013-03-27 16:36 ` Konrad Rzeszutek Wilk
2013-03-28 16:00 ` Ian Jackson
2013-03-29 13:06 ` Konrad Rzeszutek Wilk
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=1364222482-14697-7-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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).