From: Yingshiuan Pan <yingshiuan.pan@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Pavel Fedin <p.fedin@samsung.com>,
QEMU Developers <qemu-devel@nongnu.org>,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/3] virtio-mmio: introduce eventfd support
Date: Sat, 19 Sep 2015 00:56:42 +0800 [thread overview]
Message-ID: <CAA1vHq+HOygWirTn4EZy7Qcsd6Zmts7Yv-wrbHSUhtS3Tr3x+Q@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-SqUcxS+O5FKT0bod9+AptKBPM35wkzU0dqHK1Hbb55w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1860 bytes --]
Hi Peter,
I think this patch set was already merged by Michael in Jun. :).
http://git.qemu.org/?p=qemu.git;a=commit;h=434027badb421863b85ffdb4769966533c001cfa
--
Best Regards,
Yingshiuan Pan
2015-09-19 0:24 GMT+08:00 Peter Maydell <peter.maydell@linaro.org>:
> On 12 May 2015 at 09:10, Pavel Fedin <p.fedin@samsung.com> wrote:
> > This patch set introduces eventfd support for virio-mmio. It was
> originally
> > published by Ying-Shiuan Pan but never got it to upstream:
> > https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg00715.html
> > I have updated and successfully tested it with vhost-net. I confirm
> that this
> > solution significantly improves the network performance even without
> irqfd.
> > I would like to upstream it, since virtio-mmio is still there. I know
> that
> > some of you consider it deprecated, however i believe this is not
> entirely
> > true. Because you can add it to machine models which are not supposed to
> > have PCI (like vexpress).
> > An old patch set relied on additional "eventfd" option in order to
> disable
> > the support if not implemented in kernel. My version simply checks
> > kvm_eventfds_enabled() for this purpose, so backwards compatibility is
> much
> > better.
> > I decided to leave this set in three parts because ioeventfd support
> should
> > be enabled only when both host and guest notifiers are in place. I
> believe
> > it will not work with partial implementation, at least because vhost-net
> > requires both sets of eventfds. In this version i added correct reset
> handling.
>
> Hi Pavel. I've been going through my to-review folder and found this
> series from back in May lurking in it. Sorry I never got to reviewing it.
> Do you think it's still a change worth having? If so, please can you
> rebase and resend and I'll look at it this time around.
>
> thanks
> -- PMM
>
[-- Attachment #2: Type: text/html, Size: 2771 bytes --]
next prev parent reply other threads:[~2015-09-18 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 8:10 [Qemu-devel] [PATCH v3 0/3] virtio-mmio: introduce eventfd support Pavel Fedin
2015-05-12 8:10 ` [Qemu-devel] [PATCH v3 1/3] virtio-mmio: introduce set_host_notifier() Pavel Fedin
2015-05-12 8:10 ` [Qemu-devel] [PATCH v3 2/3] virtio-mmio: introduce set_guest_notifiers Pavel Fedin
2015-05-12 8:10 ` [Qemu-devel] [PATCH v3 3/3] virtio-mmio: start ioeventfd when status gets DRIVER_OK Pavel Fedin
2015-09-18 16:24 ` [Qemu-devel] [PATCH v3 0/3] virtio-mmio: introduce eventfd support Peter Maydell
2015-09-18 16:56 ` Yingshiuan Pan [this message]
2015-09-18 17:02 ` Peter Maydell
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=CAA1vHq+HOygWirTn4EZy7Qcsd6Zmts7Yv-wrbHSUhtS3Tr3x+Q@mail.gmail.com \
--to=yingshiuan.pan@gmail.com \
--cc=mst@redhat.com \
--cc=p.fedin@samsung.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).