From: Kevin Wolf <kwolf@redhat.com> To: qemu-block@nongnu.org Cc: kwolf@redhat.com, mreitz@redhat.com, qemu-devel@nongnu.org Subject: [Qemu-devel] [PATCH 0/2] blockjob: Fix coroutine thread after AioContext change Date: Fri, 3 May 2019 19:17:42 +0200 [thread overview] Message-ID: <20190503171744.21589-1-kwolf@redhat.com> (raw) Kevin Wolf (2): blockjob: Fix coroutine thread after AioContext change test-block-iothread: Job coroutine thread after AioContext switch job.c | 2 +- tests/test-block-iothread.c | 107 ++++++++++++++++++++++++++++++++++++ 2 files changed, 108 insertions(+), 1 deletion(-) -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com> To: qemu-block@nongnu.org Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com Subject: [Qemu-devel] [PATCH 0/2] blockjob: Fix coroutine thread after AioContext change Date: Fri, 3 May 2019 19:17:42 +0200 [thread overview] Message-ID: <20190503171744.21589-1-kwolf@redhat.com> (raw) Message-ID: <20190503171742.n38urnoNWkGwFxwPh-ZglibGWouvrNnir18vtLy3ZYM@z> (raw) Kevin Wolf (2): blockjob: Fix coroutine thread after AioContext change test-block-iothread: Job coroutine thread after AioContext switch job.c | 2 +- tests/test-block-iothread.c | 107 ++++++++++++++++++++++++++++++++++++ 2 files changed, 108 insertions(+), 1 deletion(-) -- 2.20.1
next reply other threads:[~2019-05-03 17:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-03 17:17 Kevin Wolf [this message] 2019-05-03 17:17 ` [Qemu-devel] [PATCH 0/2] blockjob: Fix coroutine thread after AioContext change Kevin Wolf 2019-05-03 17:17 ` [Qemu-devel] [PATCH 1/2] " Kevin Wolf 2019-05-03 17:17 ` Kevin Wolf 2019-05-03 17:17 ` [Qemu-devel] [PATCH 2/2] test-block-iothread: Job coroutine thread after AioContext switch Kevin Wolf 2019-05-03 17:17 ` Kevin Wolf 2019-05-08 12:15 ` [Qemu-devel] [PATCH 0/2] blockjob: Fix coroutine thread after AioContext change Kevin Wolf
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=20190503171744.21589-1-kwolf@redhat.com \ --to=kwolf@redhat.com \ --cc=mreitz@redhat.com \ --cc=qemu-block@nongnu.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: linkBe 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.