From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xen.org
Cc: Paul Durrant <paul.durrant@citrix.com>
Subject: [PATCH 2/2] Register Linux PV-on-HVM drivers product number.
Date: Wed, 26 Sep 2012 14:50:38 +0100 [thread overview]
Message-ID: <1348667438-28496-3-git-send-email-paul.durrant@citrix.com> (raw)
In-Reply-To: <1348667438-28496-1-git-send-email-paul.durrant@citrix.com>
This is already in use despite never being registereed.
See XEN_IOPORT_LINUX_PRODNUM in include/xen/platform_pci.h
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
---
xen/include/public/hvm/pvdrivers.h | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/xen/include/public/hvm/pvdrivers.h b/xen/include/public/hvm/pvdrivers.h
index 98d61d0..75fa656 100644
--- a/xen/include/public/hvm/pvdrivers.h
+++ b/xen/include/public/hvm/pvdrivers.h
@@ -28,17 +28,14 @@
* This is the master registry of product numbers for
* PV drivers.
* If you need a new product number allocating, please
- * post to xen-devel@lists.xen.org. You should NOT use
+ * post to xen-devel@lists.xensource.com. You should NOT use
* a product number without allocating one.
* If you maintain a separate versioning and distribution path
* for PV drivers you should have a separate product number so
* that your drivers can be separated from others.
*
- * During development, you may use the EXPERIMENTAL product ID to
+ * During development, you may use the product ID to
* indicate a driver which is yet to be released.
- *
- * See docs/misc/hvm-emulated-unplug.markdown for details of how
- * the product number is used.
*/
#define PVDRIVERS_XENSOURCE_WINDOWS_ID 0x0001 /* Citrix */
@@ -47,6 +44,9 @@
#define PVDRIVERS_GPLPV_WINDOWS_ID 0x0002 /* James Harper */
#define PVDRIVERS_GPLPV_WINDOWS_NAME "gplpv-windows"
+#define PVDRIVERS_LINUX_ID 0x0003 /* platform_pci.h */
+#define PVDRIVERS_LINUX_NAME "linux"
+
#define PVDRIVERS_EXPERIMENTAL_ID 0xffff
#define PVDRIVERS_EXPERIMENTAL_NAME "experimental"
--
1.7.2.5
next prev parent reply other threads:[~2012-09-26 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 13:50 [PATCH 0/2] PV drivers product number registration Paul Durrant
2012-09-26 13:50 ` [PATCH 1/2] Add a new pvdrivers header to serve as the register of product numbers Paul Durrant
2012-09-28 17:54 ` Ian Jackson
2012-09-26 13:50 ` Paul Durrant [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-01 16:28 [PATCH 0/2] PV drivers product number registration (v3) Paul Durrant
2012-10-01 16:28 ` [PATCH 2/2] Register Linux PV-on-HVM drivers product number Paul Durrant
2012-10-01 16:56 ` Ian Jackson
2012-10-01 9:41 [PATCH 0/2] PV drivers product number registration (v2) Paul Durrant
2012-10-01 9:41 ` [PATCH 2/2] Register Linux PV-on-HVM drivers product number Paul Durrant
2012-09-26 12:23 [PATCH 0/2] PV drivers product number registration Paul Durrant
2012-09-26 12:23 ` [PATCH 2/2] Register Linux PV-on-HVM drivers product number Paul Durrant
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=1348667438-28496-3-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--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 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).