From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Markus Armbruster <armbru@redhat.com>,
Ting Wang <kathy.wangting@huawei.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4] hmp: add info iothreads command
Date: Tue, 23 Jun 2015 14:31:24 +0200 [thread overview]
Message-ID: <5589519C.1030604@de.ibm.com> (raw)
In-Reply-To: <55894EBB.6090302@de.ibm.com>
Am 23.06.2015 um 14:19 schrieb Christian Borntraeger:
> Am 23.06.2015 um 13:57 schrieb Markus Armbruster:
>> Ting Wang <kathy.wangting@huawei.com> writes:
>>
>>> Hi Luiz and Markus,
>>>
>>> Would you like to pick up this patch, which has
>>> been reviewed by Stefan and Fam?
>>
>> Looks like this fell through the cracks back in March. You should've
>> asked for merge much earlier. Pinging the maintainer after two weeks is
>> fair.
>>
>> I just did a monitor pull, and I can't yet say whether I'll do another
>> for 2.4.
>>
>> Quick review inline.
>>
>
> Is there some patch available that allows someone to query the disks attached to
> an iothread (or check if a disk uses iothreads?). I had several testers asking why
> x-dataplane is off after specifying iothread. Maybe this information could be
> added here as well?
>
To make my last point clear. I know that x-dataplane != iothread, but people
google for "is data plane enabled" and the only answer they find is x-data-plane,
because iothreads are not visible for drives (e.g. via info qtree).
next prev parent reply other threads:[~2015-06-23 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 8:58 [Qemu-devel] [PATCH v4] hmp: add info iothreads command Ting Wang
2015-03-13 9:10 ` Fam Zheng
2015-03-13 9:16 ` Patchew Tool
2015-03-13 9:30 ` Fam Zheng
2015-03-13 14:09 ` Markus Armbruster
2015-03-17 15:48 ` Stefan Hajnoczi
2015-06-23 2:22 ` Ting Wang
2015-06-23 11:57 ` Markus Armbruster
2015-06-23 12:19 ` Christian Borntraeger
2015-06-23 12:31 ` Christian Borntraeger [this message]
2015-06-23 15:02 ` Stefan Hajnoczi
2015-06-23 13:47 ` Luiz Capitulino
2015-06-26 6:15 ` Ting Wang
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=5589519C.1030604@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kathy.wangting@huawei.com \
--cc=lcapitulino@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.