From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Keir Fraser <keir@xen.org>, Matt Wilson <msw@amazon.com>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: [PATCH v2] xen/x86: add a comment regarding how to get the VCPU ID on HVM
Date: Mon, 23 Sep 2013 20:07:55 +0200 [thread overview]
Message-ID: <1379959675-46864-1-git-send-email-roger.pau@citrix.com> (raw)
Add a note to the public headers regarding how to get the VCPU ID for
HVM guests (on x86).
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Matt Wilson <msw@amazon.com>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Matt Wilson <msw@amazon.com>
---
This is what Linux PVHVM does AFAIK, and also what I've been using in
my FreeBSD PVHVM series, but it's not written anywere.
---
Changes since v1:
* Reworded the comment as requested by Matt.
---
xen/include/public/vcpu.h | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/xen/include/public/vcpu.h b/xen/include/public/vcpu.h
index e888daf..f09367a 100644
--- a/xen/include/public/vcpu.h
+++ b/xen/include/public/vcpu.h
@@ -35,6 +35,10 @@
* @cmd == VCPUOP_??? (VCPU operation).
* @vcpuid == VCPU to operate on.
* @extra_args == Operation-specific extra arguments (NULL if none).
+ *
+ * For x86 HVM domains that use VCPU operations the VCPU ID is the ACPI
+ * Processor ID of the CPU (not to be confused with the APIC ID), as
+ * fetched from the MADT table.
*/
/*
--
1.7.7.5 (Apple Git-26)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2013-09-23 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 18:07 Roger Pau Monne [this message]
2013-10-07 10:21 ` [PATCH v2] xen/x86: add a comment regarding how to get the VCPU ID on HVM Roger Pau Monné
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=1379959675-46864-1-git-send-email-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=msw@amazon.com \
--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 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.