all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH v2 qemu] add patches to work around stuck guest IO with iothread and VirtIO block/SCSI
Date: Mon, 5 Feb 2024 12:39:46 +0100	[thread overview]
Message-ID: <4e762285-2455-4d7f-986d-62b4d42dcf82@proxmox.com> (raw)
In-Reply-To: <c101e725-909f-42f8-898f-c856813d4de9@proxmox.com>

Am 02.02.24 um 19:42 schrieb Thomas Lamprecht:
> 
> basically applied this, thanks.
> 
> Basically, as I went for the v2 [0], as the series file needed some adaption
>  due to recent v8.1.5 patch I just made a new commit but kept your message and
> added an Originally-by Trailer, hope that's all right with you.
> 

Yes, sure. Wanted to send a new version anyways :)

While the diff to v1 is pretty small, I did a quick test again and found
no obvious issue, while it still fixes my reproducer.

> [0]: https://lore.kernel.org/qemu-devel/20240202153158.788922-1-hreitz@redhat.com/
>      But still only the first two patches, the clean-up did not applied at 8.1.5 
>      and I did not bother checking that out closely.

Yes, there were some changes in the meantime and while a backport might
be removing the event_notifier_set() call from
virtio_blk_data_plane_start(), with the current code, there also is a
smp_wmb() and aio_context_acquire(s->ctx) in between
event_notifier_set() and virtio_queue_aio_attach_host_notifier(), so not
sure if that's okay in all scenarios. I don't think the backport is
necessary, because setting the event notifier twice will just kick the
virt queue twice.




      reply	other threads:[~2024-02-05 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  9:40 [pve-devel] " Fiona Ebner
2024-02-02 18:42 ` [pve-devel] applied: " Thomas Lamprecht
2024-02-05 11:39   ` Fiona Ebner [this message]

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=4e762285-2455-4d7f-986d-62b4d42dcf82@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal