From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Add hypercall to expose physical CPU in xen hypervisor
Date: Fri, 06 Nov 2009 16:30:37 +0000 [thread overview]
Message-ID: <C719FFAD.19683%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098418E4775B99@PDSMSX501.ccr.corp.intel.com>
On 06/11/2009 08:20, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
> This patch add hypercall to xen hypervisor to expose physical CPU information.
> It also make some changes to current cpu online/offline logic:
> 1) Firstly, cpu online/offline will trigger a vIRQ to dom0 for status changes
> notification.
> 2) It also add an interface to platform operation to online/offline physical
> CPU. Currently the cpu online/offline interface is in sysctl, which can't be
> triggered in kernel. With this change, it is possible to trigger cpu
> online/offline in dom0 through sysfs interface.
Is this and the accompanying Linux patch something that people really want?
The new platform hypercall will never be changeable for compatibility
reasons and looks kinda... arbitrary.
Personally I'd rather not take it.
-- Keir
next prev parent reply other threads:[~2009-11-06 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 8:20 [PATCH] Add hypercall to expose physical CPU in xen hypervisor Jiang, Yunhong
2009-11-06 16:30 ` Keir Fraser [this message]
2009-11-08 1:59 ` Jiang, Yunhong
2009-11-08 7:46 ` Keir Fraser
2009-11-09 0:45 ` Jiang, Yunhong
2009-11-09 22:03 ` Jeremy Fitzhardinge
2009-11-10 12:16 ` Jiang, Yunhong
2009-11-10 16:36 ` Konrad Rzeszutek Wilk
2009-11-10 18:00 ` Jeremy Fitzhardinge
2009-11-10 12:02 ` Jiang, Yunhong
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=C719FFAD.19683%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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 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.