From: Paolo Bonzini <pbonzini@redhat.com>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [PATCH v2 0/1] vl.c: fix trace backend init ordering
Date: Tue, 2 Mar 2021 12:03:52 +0100 [thread overview]
Message-ID: <caa67187-d9c2-bfec-b9f2-4c0240f1f18b@redhat.com> (raw)
In-Reply-To: <635eb0bb-f5fc-d3a0-924d-dd417d16cd45@gmail.com>
On 02/03/21 11:51, Daniel Henrique Barboza wrote:
> Ping
>
> There is at least one user in the Libvirt ML experiencing the same problem
> this patch is fixing, using QEMU upstream compiling with the trace backend,
> and it seems like the daemonization is still not working.
>
>
> Thanks,
>
> DHB
>
> On 1/5/21 3:14 PM, Daniel Henrique Barboza wrote:
>> changes from v2:
>> - fixed a typo in the comment block
>> - added Paolo's R-b
>>
>>
>> Daniel Henrique Barboza (1):
>> vl.c: do not execute trace_init_backends() before daemonizing
>>
>> softmmu/vl.c | 18 +++++++++++++-----
>> 1 file changed, 13 insertions(+), 5 deletions(-)
>>
>
Sorry, I was expecting Stefan to apply this patch. I have now queued it.
Paolo
prev parent reply other threads:[~2021-03-02 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 18:14 [PATCH v2 0/1] vl.c: fix trace backend init ordering Daniel Henrique Barboza
2021-01-05 18:14 ` [PATCH v2 1/1] vl.c: do not execute trace_init_backends() before daemonizing Daniel Henrique Barboza
2021-01-06 16:59 ` Stefan Hajnoczi
2021-01-06 19:59 ` Paolo Bonzini
2021-01-19 14:10 ` Daniel Henrique Barboza
2021-03-02 10:51 ` [PATCH v2 0/1] vl.c: fix trace backend init ordering Daniel Henrique Barboza
2021-03-02 11:03 ` Paolo Bonzini [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=caa67187-d9c2-bfec-b9f2-4c0240f1f18b@redhat.com \
--to=pbonzini@redhat.com \
--cc=danielhb413@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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).