All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: bazulay@redhat.com, juzhang@redhat.com, qemu-devel@nongnu.org,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] QMP: Introduce commands doc
Date: Fri, 14 May 2010 18:43:01 +0300	[thread overview]
Message-ID: <4BED6F85.50309@redhat.com> (raw)
In-Reply-To: <m3pr0yq333.fsf@blackfin.pond.sub.org>

On 05/14/2010 11:50 AM, Markus Armbruster wrote:
>
>>> +
>>> +{ "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
>>>
>>>        
>> Oh, we do have more.
>>
>> Please document the units for this value (bits per second)?
>>      
> bytes per second?
>    

Bandwidth is typically measured in bits per second.

>>> +- "bus": identical to the parent's bus number (json-int)
>>> +- "slot": slot number (json-int)
>>> +- "function": function number (json-int)
>>>
>>>        
>> Would have been nicer as a nested object (list of buses, each
>> containing a list of slots, each containing a list of functions).
>>      
> We have a list of buses, each containing a list of device functions.
> Not sure the additional level of nesting you propose buys us anything.
>    

A slot is the hotpluggable entity.  Open your computer and you can 
actually see them.

btw would be good to list empty slots as well.

What about PCI domains?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2010-05-14 15:43 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 19:11 [Qemu-devel] [PATCH v2 0/2]: QMP: Commands doc Luiz Capitulino
2010-05-05 19:11 ` [Qemu-devel] [PATCH 1/2] QMP: Introduce commands doc Luiz Capitulino
2010-05-12 16:48   ` Markus Armbruster
2010-05-12 21:17     ` Luiz Capitulino
2010-05-13  7:01       ` Markus Armbruster
2010-05-13 13:15         ` Luiz Capitulino
2010-05-14 11:29       ` Kevin Wolf
2010-05-13 13:48   ` Avi Kivity
2010-05-13 14:55     ` Luiz Capitulino
2010-05-13 15:01       ` Daniel P. Berrange
2010-05-13 16:23         ` Avi Kivity
2010-05-13 21:57           ` Luiz Capitulino
2010-05-14  8:33             ` Markus Armbruster
2010-05-14 16:42               ` Avi Kivity
2010-05-14 17:06                 ` Markus Armbruster
2010-05-13 15:05       ` Avi Kivity
2010-05-14  8:39       ` Markus Armbruster
2010-05-14 15:07         ` Luiz Capitulino
2010-05-14  8:50     ` Markus Armbruster
2010-05-14 15:43       ` Avi Kivity [this message]
2010-05-14 17:03         ` Markus Armbruster
2010-05-14 17:09           ` Avi Kivity
2010-05-17  8:27             ` Markus Armbruster
2010-05-17  9:09               ` Avi Kivity
2010-05-17 11:19                 ` Markus Armbruster
2010-05-17 18:01                   ` Anthony Liguori
2010-05-17 19:21                     ` Gerd Hoffmann
2010-05-18  6:55                       ` Avi Kivity
2010-05-14 22:54           ` Luiz Capitulino
2010-05-15  6:19             ` Avi Kivity
2010-05-17  8:27               ` Markus Armbruster
2010-05-17 18:10               ` Anthony Liguori
2010-05-17 18:12                 ` Avi Kivity
2010-05-18  9:51                 ` Markus Armbruster
2010-05-18 12:45                   ` Luiz Capitulino
2010-05-14  8:52     ` Markus Armbruster
2010-05-14 16:52   ` [Qemu-devel] " Jan Kiszka
2010-05-14 17:01     ` Avi Kivity
2010-05-14 17:02       ` Avi Kivity
2010-05-14 17:08         ` Jan Kiszka
2010-05-14 17:12           ` Avi Kivity
2010-05-14 23:10           ` Luiz Capitulino
2010-05-15  8:42             ` Jan Kiszka
2010-05-17 13:22               ` Luiz Capitulino
2010-05-18 11:21               ` Markus Armbruster
2010-05-18 12:48                 ` Luiz Capitulino
2010-05-05 19:11 ` [Qemu-devel] [PATCH 2/2] Monitor: Drop QMP documentation from code Luiz Capitulino
  -- strict thread matches above, loose matches on Subject: below --
2010-04-30 17:03 [Qemu-devel] [PATCH 0/2] QMP: Commands doc Luiz Capitulino
2010-04-30 17:03 ` [Qemu-devel] [PATCH 1/2] QMP: Introduce commands doc Luiz Capitulino
2010-05-03 16:24   ` Markus Armbruster
2010-05-04 21:58     ` Luiz Capitulino

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=4BED6F85.50309@redhat.com \
    --to=avi@redhat.com \
    --cc=armbru@redhat.com \
    --cc=bazulay@redhat.com \
    --cc=juzhang@redhat.com \
    --cc=lcapitulino@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 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.