From: Pavel Fedin <p.fedin@samsung.com>
To: "'Michael S. Tsirkin'" <mst@redhat.com>
Cc: 'Christian Borntraeger' <borntraeger@de.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio: Implement userspace forwarding for host notifiers
Date: Thu, 19 Nov 2015 14:44:37 +0300 [thread overview]
Message-ID: <014b01d122bf$ab73dc90$025b95b0$@samsung.com> (raw)
In-Reply-To: <20151119125348-mutt-send-email-mst@redhat.com>
Hello!
> OK, that's better, thanks!
Yes, indeed this was simple.
> Why do we need
> if (kvm_eventfds_enabled()) {
> memory_region_add_eventfd(&proxy->iomem, VIRTIO_MMIO_QUEUENOTIFY, 4,
> true, n, notifier);
> } else if (!set_handler) {
> virtio_queue_set_host_notifier_forwarding(vq);
> }
> everywhere though?
>
> Can't memory_region_add_eventfd DTRT depending on kvm etc?
You know... I took a look at this, and yes, i could simply hook up emulation into memory region handlers. And everything that
expects KVM eventfd binding will magically start working, probably rendering some bypass code obsolete.
I have only one concern against this. qemu is a large piece of software, consisting of lots of components. I cannot test absolutely
everything in every configuration. I suggest, old code was written with the assumption that if memory_region_add_eventfd() works, we
are really using KVM acceleration. If we break this assumption, how much code will mysteriously misbehave instead of throwing
"function not supported" error, which is quite easy to trace down and fix?
What i would refactor, perhaps, is to add a return code to memory_region_add_eventfd(), so that it can signal failure instead of a
critical abort, this would allow to get rid of kvm_eventfds_enabled() accompanying checks.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-11-19 11:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:50 [Qemu-devel] [PATCH] virtio: Implement userspace forwarding for host notifiers Pavel Fedin
2015-11-19 9:56 ` Christian Borntraeger
2015-11-19 10:18 ` Pavel Fedin
2015-11-19 11:41 ` Cornelia Huck
2015-11-19 12:02 ` Pavel Fedin
2015-11-19 12:05 ` Michael S. Tsirkin
2015-11-19 10:55 ` Michael S. Tsirkin
2015-11-19 11:44 ` Pavel Fedin [this message]
2015-11-19 12:01 ` Michael S. Tsirkin
2015-11-19 12:06 ` Paolo Bonzini
2015-11-19 12:10 ` Michael S. Tsirkin
2015-11-19 12:17 ` Pavel Fedin
2015-11-19 12:31 ` Paolo Bonzini
2015-11-19 12:55 ` Cornelia Huck
2015-11-19 16:03 ` Pavel Fedin
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='014b01d122bf$ab73dc90$025b95b0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=borntraeger@de.ibm.com \
--cc=mst@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 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).