From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "jeremy@goop.org" <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"mike.mcclurg@citrix.com" <mike.mcclurg@citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stefan.bader@canonical.com" <stefan.bader@canonical.com>,
"rjw@sisk.pl" <rjw@sisk.pl>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"liang.tang@oracle.com" <liang.tang@oracle.com>,
"Yu, Ke" <ke.yu@intel.com>,
"konrad@kernel.org" <konrad@kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: [Xen-devel] [PATCH 3/8] ACPI: processor: add __acpi_processor_[un]register_driver helpers.
Date: Thu, 22 Dec 2011 23:01:03 -0400 [thread overview]
Message-ID: <20111223030103.GA7218@andromeda.dapyr.net> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1506E01AAC469@shsmsx502.ccr.corp.intel.com>
> > OK. Lets put the # VCPU != PCPU aside. Say dom0 will boot with all
> > CPUs and then later on the admin starts unplugging them.
>
> This should be communicated to major Xen based distributions, so that it's
> an agreed approach since in majority case dom0 is configured as UP or
> a few VCPUs.
I am not saying that is it the agreed approach. There has to be
flexibility in supporting both. But what I want to understand whether
the requirement for VCPU != PCPU can be put aside and put in the drivers
later on.
So that the first approach is not changing the generic drivers (much).
The reason I am asking about this is two-fold:
1). For new distros (Ubuntu, Fedora), the default is all VCPUs.
Enterprising users might use dom0_max_vcpus to limit the VCPU count,
but most won't.
Which mean we can concentrate on bringing the _Pxx/_Cxx parsing
up to the hypervisor. Which is really neccessary on any chipset
which has the notion of TurboBoost (otherwise the Xen scheduler
won't pick this up and won't engage this mode in certain
workloads).
2). The ACPI maintainers are busy with ACPI 5.0. I don't know how
much work this is, but it probably means tons of stuff with
embedded platforms and tons of regression testing. So if there
is a patch that does not impact the generic code much (or any)
it will make their life easier. Which also means we can built
on top that for the VCPU != PCPU case.
That is what I am trying to understand.
next prev parent reply other threads:[~2011-12-23 3:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 17:20 [RFC PATCH] Exporting ACPI Pxx/Cxx states to other kernel subsystems (v1) Konrad Rzeszutek Wilk
2011-11-30 17:20 ` [PATCH 1/8] ACPI: processor: export necessary interfaces Konrad Rzeszutek Wilk
2011-12-16 21:33 ` Konrad Rzeszutek Wilk
2011-12-19 5:43 ` Tian, Kevin
2011-12-19 5:43 ` Tian, Kevin
2011-12-19 14:17 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-11-30 17:20 ` [PATCH 2/8] ACPI: processor: cache acpi_power_register in cx structure Konrad Rzeszutek Wilk
2011-11-30 17:20 ` [PATCH 3/8] ACPI: processor: add __acpi_processor_[un]register_driver helpers Konrad Rzeszutek Wilk
2011-11-30 17:20 ` Konrad Rzeszutek Wilk
2011-12-16 22:03 ` Konrad Rzeszutek Wilk
2011-12-19 5:48 ` Tian, Kevin
2011-12-19 14:26 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-12-20 2:29 ` Tian, Kevin
2011-12-20 15:31 ` Konrad Rzeszutek Wilk
2011-12-21 0:35 ` Tian, Kevin
2011-12-23 3:01 ` Konrad Rzeszutek Wilk [this message]
2011-12-26 1:31 ` Tian, Kevin
2012-01-03 20:59 ` Konrad Rzeszutek Wilk
2012-01-06 1:07 ` Tian, Kevin
2012-01-13 22:24 ` Konrad Rzeszutek Wilk
2012-01-13 22:24 ` Konrad Rzeszutek Wilk
2012-01-17 3:03 ` Tian, Kevin
2012-01-17 3:03 ` Tian, Kevin
2012-01-17 17:13 ` Konrad Rzeszutek Wilk
2012-01-17 18:19 ` Konrad Rzeszutek Wilk
2012-01-23 16:53 ` Konrad Rzeszutek Wilk
2011-11-30 17:21 ` [PATCH 4/8] ACPI: processor: Don't setup cpu idle driver and handler when we do not want them Konrad Rzeszutek Wilk
2011-12-16 21:36 ` Konrad Rzeszutek Wilk
2011-12-19 10:33 ` liang tang
2011-12-19 14:26 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-12-20 6:25 ` liang tang
2011-11-30 17:21 ` [PATCH 5/8] ACPI: add processor driver for Xen virtual CPUs Konrad Rzeszutek Wilk
2011-11-30 17:21 ` Konrad Rzeszutek Wilk
2011-12-01 9:24 ` [Xen-devel] " Jan Beulich
2011-12-01 9:24 ` Jan Beulich
2011-12-12 17:29 ` Konrad Rzeszutek Wilk
2011-12-12 17:29 ` Konrad Rzeszutek Wilk
2011-12-13 7:45 ` Jan Beulich
2011-12-13 7:45 ` Jan Beulich
2011-12-13 9:26 ` liang tang
2011-12-16 22:21 ` Konrad Rzeszutek Wilk
2012-02-10 17:18 ` Konrad Rzeszutek Wilk
2011-11-30 17:21 ` [PATCH 6/8] ACPI: processor: override the interface of register acpi processor handler for Xen vcpu Konrad Rzeszutek Wilk
2011-11-30 17:21 ` [PATCH 7/8] ACPI: xen processor: add PM notification interfaces Konrad Rzeszutek Wilk
2011-11-30 17:21 ` [PATCH 8/8] ACPI: xen processor: set ignore_ppc to handle PPC event for Xen vcpu 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=20111223030103.GA7218@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=Ian.Campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=ke.yu@intel.com \
--cc=kevin.tian@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=lenb@kernel.org \
--cc=liang.tang@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.mcclurg@citrix.com \
--cc=rjw@sisk.pl \
--cc=stefan.bader@canonical.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 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.