From: Maxim Levitsky <mlevitsk@redhat.com>
To: qemu-devel@nongnu.org
Cc: Fam Zheng <fam@euphon.net>, Paolo Bonzini <pbonzini@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [PATCH 0/3] RFC: few random hacks to improve eventfd fallback path
Date: Thu, 17 Dec 2020 17:00:37 +0200 [thread overview]
Message-ID: <20201217150040.906961-1-mlevitsk@redhat.com> (raw)
These few patches are the result of a random hacking I did to make the qemu
cope with eventfd allocation failure, when using an iothread,
as it happened in bz #1897550.
I am not 100% sure which patches in this series are worth to merge, or if
this can be fixed in a better way.
After this patch series applied, qemu still hangs while running reproducer for
this BZ due to ABBA lock inversion which needs some heavy rework to get rid of.
I explained all the (gory) details in the bugzilla.
This patch series was (lightly) tested with make check, iotests and with
the reproducer.
Best regards,
Maxim Levitsky
Maxim Levitsky (3):
scsi: virtio-scsi: don't process IO on fenced dataplane
virtio-scsi: don't uninitialize queues that we didn't initialize
event_notifier: handle initialization failure better
hw/scsi/virtio-scsi-dataplane.c | 26 +++++++++++++++++++-------
include/qemu/event_notifier.h | 1 +
util/event_notifier-posix.c | 16 ++++++++++++++++
3 files changed, 36 insertions(+), 7 deletions(-)
--
2.26.2
next reply other threads:[~2020-12-17 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:00 Maxim Levitsky [this message]
2020-12-17 15:00 ` [PATCH 1/3] scsi: virtio-scsi: don't process IO on fenced dataplane Maxim Levitsky
2020-12-17 15:00 ` [PATCH 2/3] virtio-scsi: don't uninitialize queues that we didn't initialize Maxim Levitsky
2020-12-17 15:00 ` [PATCH 3/3] event_notifier: handle initialization failure better Maxim Levitsky
2021-01-07 10:26 ` [PATCH 0/3] RFC: few random hacks to improve eventfd fallback path Maxim Levitsky
2021-01-13 14:38 ` Paolo Bonzini
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=20201217150040.906961-1-mlevitsk@redhat.com \
--to=mlevitsk@redhat.com \
--cc=fam@euphon.net \
--cc=mst@redhat.com \
--cc=pbonzini@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).