From: "Andreas Färber" <afaerber@suse.de>
To: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
Cc: quintela@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com,
borntraeger@de.ibm.com, amit.shah@redhat.com,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 1/5] cpu: Provide vcpu throttling interface
Date: Thu, 02 Jul 2015 18:47:03 +0200 [thread overview]
Message-ID: <55956B07.3000109@suse.de> (raw)
In-Reply-To: <1435855010-30882-2-git-send-email-jjherne@linux.vnet.ibm.com>
Am 02.07.2015 um 18:36 schrieb Jason J. Herne:
> Provide a method to throttle guest cpu execution. CPUState is augmented with
> timeout controls and throttle start/stop functions. To throttle the guest cpu
> the caller simply has to call the throttle set function and provide a percentage
> of throttle time.
>
> Signed-off-by: Jason J. Herne <jjherne@linux.vnet.ibm.com>
> Reviewed-by: Matthew Rosato <mjrosato@linux.vnet.ibm.com>
> ---
> cpus.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> include/qom/cpu.h | 38 ++++++++++++++++++++++++++++++++
> 2 files changed, 104 insertions(+)
No objections from my side, but the interesting code is outside my area.
I feel we (including myself) are abusing include/qom/cpu.h (here there's
not even a single CPUState argument) but I don't have a better
suggestion. At some point we'll need to revisit the cpu.h vs. cpu-all.h
etc. split or even introduce something new.
I'm preparing a qom-cpu pull and assume this will go through the
migration tree when finalized.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-07-02 16:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 16:36 [Qemu-devel] [PATCH v4 0/5] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 1/5] cpu: Provide vcpu throttling interface Jason J. Herne
2015-07-02 16:43 ` Paolo Bonzini
2015-07-02 16:58 ` Dr. David Alan Gilbert
2015-07-13 14:43 ` Jason J. Herne
2015-07-13 15:14 ` Paolo Bonzini
2015-07-15 12:40 ` Jason J. Herne
2015-07-15 12:54 ` Paolo Bonzini
2015-07-16 14:21 ` Jason J. Herne
2015-07-23 9:59 ` Paolo Bonzini
2015-07-31 17:12 ` Jason J. Herne
2015-07-31 17:16 ` Paolo Bonzini
2015-07-31 17:42 ` Jason J. Herne
2015-07-31 18:11 ` Jason J. Herne
2015-08-01 9:40 ` Paolo Bonzini
2015-09-01 14:43 ` Jason J. Herne
2015-07-02 16:47 ` Andreas Färber [this message]
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 2/5] migration: Parameters for auto-converge cpu throttling Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 3/5] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 4/5] qmp/hmp: Add throttle ratio to query-migrate and info migrate Jason J. Herne
2015-07-02 16:36 ` [Qemu-devel] [PATCH v4 5/5] migration: Disambiguate MAX_THROTTLE Jason J. Herne
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=55956B07.3000109@suse.de \
--to=afaerber@suse.de \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).