All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Garcia <berto@igalia.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 9/9] throttle: add name of ThrottleGroup to BlockDeviceInfo
Date: Wed, 4 Mar 2015 08:20:25 +0100	[thread overview]
Message-ID: <20150304072025.GA21627@igalia.com> (raw)
In-Reply-To: <878ufd44t9.fsf@blackfin.pond.sub.org>

On Wed, Mar 04, 2015 at 08:09:22AM +0100, Markus Armbruster wrote:

> >> { 'type': 'ThrottleGroupInfo',
> >>   'data': { 'name': 'str', 'nodes': ['BlockDeviceInfo'] } }
> >> 
> >> { 'command': 'query-block-throttle',
> >>   'returns': ['ThrottleGroupInfo'] }

> We need a coherent set of block queries.  What we have is an ad hoc
> mess.  Alberto proposes to add to the mess.  Digs us deeper into the
> hole.

If you can describe what you would like to have then I can try to
help.

Berto

  reply	other threads:[~2015-03-04  7:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 16:06 [Qemu-devel] [PATCH v2 0/9] Block Throttle Group Support Alberto Garcia
2015-02-13 16:06 ` [Qemu-devel] [PATCH 1/9] throttle: Extract timers from ThrottleState into a separate ThrottleTimers structure Alberto Garcia
2015-03-03 16:03   ` Stefan Hajnoczi
2015-02-13 16:06 ` [Qemu-devel] [PATCH 2/9] throttle: Add throttle group infrastructure Alberto Garcia
2015-03-03 16:38   ` Stefan Hajnoczi
2015-03-04 10:18     ` Alberto Garcia
2015-03-04 16:02       ` Stefan Hajnoczi
2015-02-13 16:06 ` [Qemu-devel] [PATCH 3/9] throttle: Add throttle group infrastructure tests Alberto Garcia
2015-02-13 16:06 ` [Qemu-devel] [PATCH 4/9] throttle: Prepare to have multiple timers for one ThrottleState Alberto Garcia
2015-03-03 16:50   ` Stefan Hajnoczi
2015-02-13 16:06 ` [Qemu-devel] [PATCH 5/9] throttle: Add a way to know if throttle_schedule_timer had armed a timer Alberto Garcia
2015-02-13 16:06 ` [Qemu-devel] [PATCH 6/9] throttle: Add a way to fire one of the timers asap like a bottom half Alberto Garcia
2015-03-03 17:08   ` Stefan Hajnoczi
2015-02-13 16:06 ` [Qemu-devel] [PATCH 7/9] throttle: Add throttle group support Alberto Garcia
2015-02-24 16:45   ` Eric Blake
2015-02-24 16:47     ` Eric Blake
2015-03-03 21:00   ` Stefan Hajnoczi
2015-03-04 13:53     ` Alberto Garcia
2015-03-04 16:04       ` Stefan Hajnoczi
2015-03-04 16:16         ` Alberto Garcia
2015-03-05 17:41           ` Stefan Hajnoczi
2015-02-13 16:06 ` [Qemu-devel] [PATCH 8/9] throttle: Update throttle infrastructure copyright Alberto Garcia
2015-02-24 16:49   ` Eric Blake
2015-02-24 20:21     ` Benoît Canet
2015-02-13 16:06 ` [Qemu-devel] [PATCH 9/9] throttle: add name of ThrottleGroup to BlockDeviceInfo Alberto Garcia
2015-02-24 16:54   ` Eric Blake
2015-02-25 10:56     ` Alberto Garcia
2015-02-25 15:23       ` Eric Blake
2015-02-25 15:37         ` Alberto Garcia
2015-02-26 13:56         ` Alberto Garcia
2015-03-03 17:53           ` Eric Blake
2015-03-04  7:09             ` Markus Armbruster
2015-03-04  7:20               ` Alberto Garcia [this message]
2015-03-03 21:07 ` [Qemu-devel] [PATCH v2 0/9] Block Throttle Group Support Stefan Hajnoczi

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=20150304072025.GA21627@igalia.com \
    --to=berto@igalia.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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.