From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, ian.campbell@eu.citrix.com
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 1/6] docs: Document the ELF_FEATURES entry
Date: Fri, 15 Mar 2013 15:51:51 -0400 [thread overview]
Message-ID: <1363377116-30324-2-git-send-email-konrad.wilk@oracle.com> (raw)
In-Reply-To: <1363377116-30324-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-15 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 19:51 [PATCH v4] Documentation to various header files (v4?) Konrad Rzeszutek Wilk
2013-03-15 19:51 ` Konrad Rzeszutek Wilk [this message]
2013-03-15 19:51 ` [PATCH 2/6] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 3/6] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 4/6] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-03-15 19:51 ` [PATCH 5/6] docs: Document start_info changes in Xen 4.2 Konrad Rzeszutek Wilk
2013-03-18 10:55 ` Jan Beulich
2013-03-18 11:11 ` Keir Fraser
2013-03-18 13:08 ` Jan Beulich
2013-03-15 19:51 ` [PATCH 6/6] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-03-18 9:44 ` [PATCH v4] Documentation to various header files (v4?) Ian Campbell
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=1363377116-30324-2-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@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).