From: Jens Axboe <axboe@kernel.dk>
To: Ju Hyung Park <qkrwngud825@gmail.com>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
io-uring@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: io_uring possibly the culprit for qemu hang (linux-5.4.y)
Date: Sat, 17 Oct 2020 09:02:09 -0600 [thread overview]
Message-ID: <7ea53adb-14c7-8c31-2f9e-44a3847ee91c@kernel.dk> (raw)
In-Reply-To: <CAD14+f0h-r7o=m0NvHxjCgKaQe24_MDupcDdSOu05PhXp8B1-w@mail.gmail.com>
On 10/17/20 8:29 AM, Ju Hyung Park wrote:
> Hi Jens.
>
> On Sat, Oct 17, 2020 at 3:07 AM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Would be great if you could try 5.4.71 and see if that helps for your
>> issue.
>>
>
> Oh wow, yeah it did fix the issue.
>
> I'm able to reliably turn off and start the VM multiple times in a row.
> Double checked by confirming QEMU is dynamically linked to liburing.so.1.
>
> Looks like those 4 io_uring fixes helped.
Awesome, thanks for testing!
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Ju Hyung Park <qkrwngud825@gmail.com>
Cc: qemu-devel@nongnu.org, io-uring@vger.kernel.org,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: io_uring possibly the culprit for qemu hang (linux-5.4.y)
Date: Sat, 17 Oct 2020 09:02:09 -0600 [thread overview]
Message-ID: <7ea53adb-14c7-8c31-2f9e-44a3847ee91c@kernel.dk> (raw)
In-Reply-To: <CAD14+f0h-r7o=m0NvHxjCgKaQe24_MDupcDdSOu05PhXp8B1-w@mail.gmail.com>
On 10/17/20 8:29 AM, Ju Hyung Park wrote:
> Hi Jens.
>
> On Sat, Oct 17, 2020 at 3:07 AM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Would be great if you could try 5.4.71 and see if that helps for your
>> issue.
>>
>
> Oh wow, yeah it did fix the issue.
>
> I'm able to reliably turn off and start the VM multiple times in a row.
> Double checked by confirming QEMU is dynamically linked to liburing.so.1.
>
> Looks like those 4 io_uring fixes helped.
Awesome, thanks for testing!
--
Jens Axboe
next prev parent reply other threads:[~2020-10-17 15:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 16:26 io_uring possibly the culprit for qemu hang (linux-5.4.y) Ju Hyung Park
2020-10-01 3:03 ` Jens Axboe
2020-10-01 8:59 ` Stefano Garzarella
2020-10-01 8:59 ` Stefano Garzarella
2020-10-01 13:47 ` Jack Wang
2020-10-01 14:30 ` Ju Hyung Park
2020-10-01 14:30 ` Ju Hyung Park
2020-10-02 7:34 ` Stefano Garzarella
2020-10-02 7:34 ` Stefano Garzarella
2020-10-16 18:04 ` Ju Hyung Park
2020-10-16 18:07 ` Jens Axboe
2020-10-17 14:29 ` Ju Hyung Park
2020-10-17 14:29 ` Ju Hyung Park
2020-10-17 15:02 ` Jens Axboe [this message]
2020-10-17 15:02 ` Jens Axboe
2020-10-19 9:22 ` Pankaj Gupta
2020-10-19 9:22 ` Pankaj Gupta
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=7ea53adb-14c7-8c31-2f9e-44a3847ee91c@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=qkrwngud825@gmail.com \
--cc=sgarzare@redhat.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.