From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
dev@dpdk.org, "Carew, Alan" <alan.carew@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [dpdk-dev] [PATCH v4 00/10] VM Power Management
Date: Fri, 12 Dec 2014 17:13:55 +0100 [thread overview]
Message-ID: <548B1443.6060706@redhat.com> (raw)
In-Reply-To: <6597811.ARdDfzU0XI@xps13>
On 12/12/2014 17:10, Thomas Monjalon wrote:
> > Ok, this looks specific enough that an out-of-band solution within DPDK
> > sounds like the best approach. It seems unnecessary to involve the
> > hypervisor (neither KVM nor QEMU).
>
> Paolo, I don't understand why you don't imagine controlling frequency scaling
> of a pinned vCPU transparently?
Probably because I don't imagine controlling frequency scaling from the
application on bare metal, either. :) It seems to me that this is just
working around limitations of the kernel.
Paolo
> In my understanding, we currently cannot control frequency scaling without
> knowing wether we are in a VM or not.
prev parent reply other threads:[~2014-12-12 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1412003903-9061-1-git-send-email-alan.carew@intel.com>
[not found] ` <3349663.LNtcecTXb3@xps13>
[not found] ` <0E29434AEE0C3A4180987AB476A6F6306D2811AD@IRSMSX109.ger.corp.intel.com>
[not found] ` <1804867.TWdiCQc2JQ@xps13>
[not found] ` <0E29434AEE0C3A4180987AB476A6F6306D28E7DF@IRSMSX109.ger.corp.intel.com>
[not found] ` <26FA93C7ED1EAA44AB77D62FBE1D27BA54C4BD63@IRSMSX102.ger.corp.intel.com>
2014-11-22 17:17 ` [Qemu-devel] [dpdk-dev] [PATCH v4 00/10] VM Power Management Vincent JARDIN
2014-12-09 17:35 ` [Qemu-devel] " Paolo Bonzini
2014-12-11 23:18 ` [Qemu-devel] [dpdk-dev] " Thomas Monjalon
2014-12-12 13:00 ` Carew, Alan
2014-12-12 14:50 ` Paolo Bonzini
2014-12-12 16:10 ` Thomas Monjalon
2014-12-12 16:13 ` Paolo Bonzini [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=548B1443.6060706@redhat.com \
--to=pbonzini@redhat.com \
--cc=alan.carew@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas.monjalon@6wind.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 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).