From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Fam Zheng" <famz@redhat.com>,
qemu-devel@nongnu.org
Cc: armbru@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] dump: Acquire BQL around vm_start() in dump thread
Date: Thu, 4 May 2017 14:58:20 +0200 [thread overview]
Message-ID: <3e9180c7-dc77-a300-2638-9a1b8c9a1a31@redhat.com> (raw)
In-Reply-To: <CAJ+F1CK9sup=RVT2wCuiFMiCPZAryPg1qYX9HtDGwvnTy73oRA@mail.gmail.com>
On 03/05/2017 10:37, Marc-André Lureau wrote:
> Hi
>
> On Wed, May 3, 2017 at 11:42 AM Fam Zheng <famz@redhat.com
> <mailto:famz@redhat.com>> wrote:
>
> On Wed, 05/03 15:28, Fam Zheng wrote:
> > This fixes an assertion failure in the following backtrace:
>
> Do you know if it's a regression? Is this a racy case? (I couldn't
> reproduce)
I think it's never worked since separate-thread dump was introduced.
Paolo
>
> > __GI___assert_fail
> > memory_region_transaction_commit
> > memory_region_add_eventfd
> > virtio_pci_ioeventfd_assign
> > virtio_bus_set_host_notifier
> > virtio_blk_data_plane_start
> > virtio_bus_start_ioeventfd
> > virtio_vmstate_change
> > vm_state_notify
> > vm_prepare_start
> > vm_start
> > dump_cleanup
> > dump_process
> > dump_thread
> > start_thread
> > clone
> >
> > vm_start need BQL, acquire it if doing cleaning up from main thread.
>
> Oops, s/need/needs and s/main thread/detached thread/.
>
>
> With that fixed,
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com
> <mailto:marcandre.lureau@redhat.com>>
>
> --
> Marc-André Lureau
next prev parent reply other threads:[~2017-05-04 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 7:28 [Qemu-devel] [PATCH] dump: Acquire BQL around vm_start() in dump thread Fam Zheng
2017-05-03 7:42 ` Fam Zheng
2017-05-03 8:37 ` Marc-André Lureau
2017-05-04 12:58 ` Paolo Bonzini [this message]
2017-05-04 12:59 ` 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=3e9180c7-dc77-a300-2638-9a1b8c9a1a31@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=peterx@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).