qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, qemu-stable@nongnu.org,
	Bandan Das <bsd@redhat.com>,
	mprivozn@redhat.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Delay initialization of memory backends
Date: Tue, 6 Sep 2016 09:39:19 +0200	[thread overview]
Message-ID: <c56ba853-947d-d176-8829-a880611669c5@redhat.com> (raw)
In-Reply-To: <20160906052359-mutt-send-email-mst@kernel.org>



On 09/06/2016 04:24 AM, Michael S. Tsirkin wrote:
> On Mon, Sep 05, 2016 at 04:01:30PM -0300, Eduardo Habkost wrote:
>> On Mon, Sep 05, 2016 at 02:26:30PM +0200, Paolo Bonzini wrote:
>>> On 02/09/2016 20:59, Eduardo Habkost wrote:
>>>> While trying to fix the original bug in v1, another bug was fixed
>>>> by accident: TCG initialization of dirty_log_mask was broken when
>>>> using memory backends.
>>>>
>>>> The fix, on the other hand, broke vhost-user-test because it
>>>> relied on TCG, even though TCG is incompatible with vhost.
>>>>
>>>> This new version changes vhost-user-test to not rely on TCG, so
>>>> we can finally fix the initialization ordering of memory
>>>> backends.
>>>>
>>>> Eduardo Habkost (2):
>>>>   vhost-user-test: Use libqos instead of pxe-virtio.rom
>>>>   vl: Delay initialization of memory backends
>>>>
>>>>  tests/Makefile.include  |  2 +-
>>>>  tests/vhost-user-test.c | 37 ++++++++++++++++++++++++++++++++++---
>>>>  vl.c                    | 13 +++++++++++++
>>>>  3 files changed, 48 insertions(+), 4 deletions(-)
>>>>
>>>
>>> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>>>
>>> for whoever wants to pick this up...
>>
>> I will commit it. Thanks!
>
> Feel free to commit if you didn't already.
>
> Belatedly:
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>

Michael, please note that not using TCG also fixes the hang observed
with patch:
28ed5ef ("vhost-user: Attempt to fix a race with set_mem_table.")
It confirms my analysis that it would only happen with relying on TCG.
Should we revert your revert once this series applied to mainline?

So, FWIW now that the patch may be already committed:
Tested-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime

      reply	other threads:[~2016-09-06  7:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 18:59 [Qemu-devel] [PATCH v2 0/2] Delay initialization of memory backends Eduardo Habkost
2016-09-02 18:59 ` [Qemu-devel] [PATCH v2 1/2] vhost-user-test: Use libqos instead of pxe-virtio.rom Eduardo Habkost
2016-09-02 18:59 ` [Qemu-devel] [PATCH v2 2/2] vl: Delay initialization of memory backends Eduardo Habkost
2016-09-05  9:03 ` [Qemu-devel] [PATCH v2 0/2] " Markus Armbruster
2016-09-05 12:26 ` Paolo Bonzini
2016-09-05 19:01   ` Eduardo Habkost
2016-09-06  2:24     ` Michael S. Tsirkin
2016-09-06  7:39       ` Maxime Coquelin [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=c56ba853-947d-d176-8829-a880611669c5@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=armbru@redhat.com \
    --cc=bsd@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mprivozn@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).