From: Paolo Bonzini <pbonzini@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/virtio: enable common virtio feature for mmio device
Date: Mon, 16 Jun 2014 11:50:53 +0200 [thread overview]
Message-ID: <539EBDFD.2040406@redhat.com> (raw)
In-Reply-To: <CACVXFVPcY3CxRyR2Cr44igBUFDxEmz_RwR=jDbfQrtK=J6qAAA@mail.gmail.com>
Il 16/06/2014 11:26, Ming Lei ha scritto:
> On Mon, Jun 16, 2014 at 3:54 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 09/06/2014 10:00, Ming Lei ha scritto:
>>
>>> On Wed, Jun 4, 2014 at 10:05 AM, Ming Lei <ming.lei@canonical.com> wrote:
>>>>
>>>> Both 'indirect_desc' and 'event_idx' are bus independent features,
>>>> and they should be enabled for mmio devices too.
>>>>
>>>> On arm64 quad core VM(qemu-kvm), the patch can increase block I/O
>>>> performance a lot with latest linux tree:
>>>> - without the patch: 14K IOPS
>>>> - with the patch: 34K IOPS
>>>>
>>>> fio script:
>>>> [global]
>>>> direct=1
>>>> bsrange=4k-4k
>>>> timeout=10
>>>> numjobs=4
>>>> ioengine=libaio
>>>> iodepth=64
>>>>
>>>> filename=/dev/vdc
>>>> group_reporting=1
>>>>
>>>> [f1]
>>>> rw=randread
>>>>
>>>> Cc: Peter Maydell <peter.maydell@linaro.org>
>>>> Signed-off-by: Ming Lei <ming.lei@canonical.com>
>>>> ---
>>>> hw/virtio/virtio-mmio.c | 6 ++++++
>>>> 1 file changed, 6 insertions(+)
>>>>
>>>> diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
>>>> index 8829eb0..18c6e5b 100644
>>>> --- a/hw/virtio/virtio-mmio.c
>>>> +++ b/hw/virtio/virtio-mmio.c
>>>> @@ -369,10 +369,16 @@ static void virtio_mmio_realizefn(DeviceState *d,
>>>> Error **errp)
>>>> sysbus_init_mmio(sbd, &proxy->iomem);
>>>> }
>>>>
>>>> +static Property virtio_mmio_properties[] = {
>>>> + DEFINE_VIRTIO_COMMON_FEATURES(VirtIOMMIOProxy, host_features),
>>>> + DEFINE_PROP_END_OF_LIST(),
>>>> +};
>>>> +
>>>> static void virtio_mmio_class_init(ObjectClass *klass, void *data)
>>>> {
>>>> DeviceClass *dc = DEVICE_CLASS(klass);
>>>>
>>>> + dc->props = virtio_mmio_properties;
>>>> dc->realize = virtio_mmio_realizefn;
>>>> dc->reset = virtio_mmio_reset;
>>>> set_bit(DEVICE_CATEGORY_MISC, dc->categories);
>>>> --
>>>> 1.7.9.5
>>
>>
>> Looks good.
>
> Paolo, thanks for your review.
>
>> Can you look into moving DEFINE_VIRTIO_COMMON_FEATURES
>> from all virtio pci devices to TYPE_VIRTIO_PCI, too?
>
> OK, that looks a good cleanup, how about the attached patch?
Since you touched DEFINE_VIRTIO_SCSI_FEATURES and
DEFINE_VIRTIO_NET_FEATURES, you need to do the same change in
hw/s390x/s390-virtio-bus.c and hw/s390x/virtio-ccw.c as well.
Otherwise, the PCI parts of the patch are okay. Thanks,
Paolo
> If it is OK, I will prepare a formal one for submitting.
next prev parent reply other threads:[~2014-06-16 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 2:05 [Qemu-devel] [PATCH] hw/virtio: enable common virtio feature for mmio device Ming Lei
2014-06-09 8:00 ` Ming Lei
2014-06-16 7:54 ` Paolo Bonzini
2014-06-16 9:26 ` Ming Lei
2014-06-16 9:50 ` Paolo Bonzini [this message]
2014-06-30 10:09 ` Michael S. Tsirkin
2014-06-30 10:13 ` Ming Lei
2014-06-30 9:59 ` Ming Lei
2014-06-30 10:08 ` Michael S. Tsirkin
2014-07-02 12:34 ` Michael S. Tsirkin
2014-07-02 12:36 ` Ming Lei
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=539EBDFD.2040406@redhat.com \
--to=pbonzini@redhat.com \
--cc=ming.lei@canonical.com \
--cc=peter.maydell@linaro.org \
--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 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).