From: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
To: quintela@redhat.com
Cc: amit.shah@redhat.com, borntraeger@de.ibm.com,
qemu-devel@nongnu.org, dgilbert@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 1/2] cpu: Provide vcpu throttling interface
Date: Wed, 03 Jun 2015 10:35:36 -0400 [thread overview]
Message-ID: <556F10B8.9080703@linux.vnet.ibm.com> (raw)
In-Reply-To: <878uc29mwz.fsf@neno.neno>
On 06/03/2015 03:12 AM, Juan Quintela wrote:
>> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
>> >index 39f0f19..9d16e6a 100644
>> >--- a/include/qom/cpu.h
>> >+++ b/include/qom/cpu.h
>> >@@ -310,6 +310,11 @@ struct CPUState {
>> > uint32_t can_do_io;
>> > int32_t exception_index; /* used by m68k TCG */
>> >
>> >+ /* vcpu throttling controls */
>> >+ QEMUTimer *throttle_timer;
>> >+ bool throttle_timer_stop;
>> >+ float throttle_ratio;
>> >+
> I think that if we go this way, we can have a single throotling thread
> that do a for loop for each vcpu. As a bonus, we got a single timer,
> and single bool and a single throotle_ratio (i.e. it don't need to be on
> the cpu struct). Being a global will don't matter because we are
> requiring the iothread anyways.
>
Juan,
I like this idea. I'll work up another patch set :).
--
-- Jason J. Herne (jjherne@linux.vnet.ibm.com)
next prev parent reply other threads:[~2015-06-03 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 15:17 [Qemu-devel] [PATCH 0/2] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-06-01 15:17 ` [Qemu-devel] [PATCH 1/2] cpu: Provide vcpu throttling interface Jason J. Herne
2015-06-01 15:23 ` Andrey Korolyov
2015-06-01 17:04 ` Jason J. Herne
2015-06-03 7:12 ` Juan Quintela
2015-06-03 14:35 ` Jason J. Herne [this message]
2015-06-01 15:17 ` [Qemu-devel] [PATCH 2/2] migration: Dynamic cpu throttling for auto-converge Jason J. Herne
2015-06-01 15:32 ` Dr. David Alan Gilbert
2015-06-01 17:16 ` Jason J. Herne
2015-06-02 13:58 ` Dr. David Alan Gilbert
2015-06-02 14:37 ` Jason J. Herne
2015-06-02 14:57 ` Dr. David Alan Gilbert
2015-06-02 16:45 ` Eric Blake
2015-06-03 7:24 ` Juan Quintela
2015-06-03 7:21 ` Juan Quintela
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=556F10B8.9080703@linux.vnet.ibm.com \
--to=jjherne@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dgilbert@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 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.