From: James Dingwall <james@dingwall.me.uk>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [james-xen@dingwall.me.uk: [Xen-users] Xen 4.2.0 - CPU Frequency Scaling]
Date: Tue, 2 Oct 2012 22:30:45 +0100 [thread overview]
Message-ID: <20121002213045.GA7918@dingwall.me.uk> (raw)
In-Reply-To: <CACJDEmpQBpAsxR9WTFGG-52T-0UXJpTprf_rAwC_6JiiHHt6vg@mail.gmail.com>
On Tue, Oct 02, 2012 at 03:08:39PM -0400, Konrad Rzeszutek Wilk wrote:
> >>
> >> What exactly are you trying to manage? As in what are you doing?
> >
> > What I was trying to achieve was 2 vcpus assigned and pinned to dom0 with
> > the remaining available for domUs. I wanted to set the scaling governor as
> > performance for the dom0 vcpus and ondemand for domUs.
> >
> > It was an obvious test to change dom0_max_vcpus and I should have done it
> > before. On removing the parameter so that all cpus were seen in dom0 I could
> > control the power state of them all independently. Reinstating the
> > parameter with value of n showed that cpu 1 - (n-1) could be controlled
> > independently while cpus 0 and n-11 were grouped together.
>
> And this behavior existed with the old kernel? Or was this something
> you were trying to do now?
I seem to recall that with the old xen-sources kernel that this wasn't a
problem as I had an init script which set the cpu frequency governors as
I wanted them. However once mainline got dom0 pvops I jumped to that
and made do without that particular feature. Once xen-acpi-processor
was added then I noticed this behaviour. It is possible that during
that time I added the dom0_max_vcpus parameter and so I'm not comparing
exactly the same configuration. I'll poke around to see if I can find
an old xen kernel which I can test with.
Thanks,
JAmes
prev parent reply other threads:[~2012-10-02 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 16:13 [james-xen@dingwall.me.uk: [Xen-users] Xen 4.2.0 - CPU Frequency Scaling] James Dingwall
2012-10-01 16:33 ` Konrad Rzeszutek Wilk
2012-10-01 20:27 ` James Dingwall
2012-10-02 19:08 ` Konrad Rzeszutek Wilk
2012-10-02 21:30 ` James Dingwall [this message]
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=20121002213045.GA7918@dingwall.me.uk \
--to=james@dingwall.me.uk \
--cc=konrad@kernel.org \
--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).