From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Alan Carew <alan.carew@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [dpdk-dev] [PATCH v4 00/10] VM Power Management
Date: Fri, 12 Dec 2014 00:18:08 +0100 [thread overview]
Message-ID: <10291528.MoKaz8pbFD@xps13> (raw)
In-Reply-To: <548732C9.2020201@redhat.com>
2014-12-09 18:35, Paolo Bonzini:
> >>>> Did you make any progress in Qemu/KVM community?
> >>>> We need to be sync'ed up with them to be sure we share the same goal.
> >>>> I want also to avoid using a solution which doesn't fit with their
> >>>> plan.
> >>>> Remember that we already had this problem with ivshmem which was
> >>>> planned to be dropped.
> >>>
> >>> Unfortunately, I have not yet received any feedback:
> >>> http://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg01103.html
> >>
> >> Just to add to what Alan said above, this capability does not exist in
> >> qemu at the moment, and based on there having been no feedback on th
> >> qemu mailing list so far, I think it's reasonable to assume that it
> >> will not be implemented in the immediate future. The VM Power
> >> Management feature has also been designed to allow easy migration to a
> >> qemu-based solution when this is supported in future. Therefore, I'd
> >> be in favour of accepting this feature into DPDK now.
> >>
> >> It's true that the implementation is a work-around, but there have
> >> been similar cases in DPDK in the past. One recent example that comes
> >> to mind is userspace vhost. The original implementation could also be
> >> considered a work-around, but it met the needs of many in the
> >> community. Now, with support for vhost-user in qemu 2.1, that
> >> implementation is being improved. I'd see VM Power Management
> >> following a similar path when this capability is supported in qemu.
>
> I wonder if this might be papering over a bug in the host cpufreq
> driver. If the guest is not doing much and leaving a lot of idle CPU
> time, the host should scale down the frequency of that CPU. In the case
> of pinned VCPUs this should really "just work". What is the problem
> that is being solved?
>
> Paolo
Alan, Pablo, please could you explain your logic with VM power management?
--
Thomas
next prev parent reply other threads:[~2014-12-11 23:18 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 ` Thomas Monjalon [this message]
2014-12-12 13:00 ` [Qemu-devel] [dpdk-dev] " Carew, Alan
2014-12-12 14:50 ` Paolo Bonzini
2014-12-12 16:10 ` Thomas Monjalon
2014-12-12 16:13 ` Paolo Bonzini
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=10291528.MoKaz8pbFD@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=alan.carew@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).