From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Emilio Cota <cota@braap.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/2] fix for #285
Date: Wed, 11 Jan 2023 12:26:00 +0000 [thread overview]
Message-ID: <Y76q2HjvfzwLnlBT@redhat.com> (raw)
In-Reply-To: <20230111035536.309885-1-cota@braap.org>
On Tue, Jan 10, 2023 at 10:55:34PM -0500, Emilio Cota wrote:
> Context:
> https://gitlab.com/qemu-project/qemu/-/issues/285
>
> So far the only fix that we have had posted on the list is
> https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg00391.html
> by Daniel. The approach that I'm following here should have
> the same outcome, except that it doesn't change the guest's
> environment. The approach is to import GTree (sans GSlice)
> into QEMU, and use that for TCG.
>
> Daniel: what is the testing that you're using? Could you test
> these patches to confirm they fix the issue?
I used the demo program in the bug report. With your patches applied,
that appears to run without hangs for a decent amount of time.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2023-01-11 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 3:55 [PATCH 0/2] fix for #285 Emilio Cota
2023-01-11 3:55 ` [PATCH 1/2] util: import GTree as QTree Emilio Cota
2023-01-11 12:08 ` Daniel P. Berrangé
2023-01-29 22:28 ` Emilio Cota
2023-01-11 3:55 ` [PATCH 2/2] tcg: use QTree instead of GTree Emilio Cota
2023-01-11 12:10 ` Daniel P. Berrangé
2023-01-29 22:32 ` Emilio Cota
2023-01-11 12:34 ` Daniel P. Berrangé
2023-01-25 15:58 ` Daniel P. Berrangé
2023-01-29 22:38 ` Emilio Cota
2023-01-30 9:27 ` Daniel P. Berrangé
2023-01-30 19:09 ` Richard Henderson
2023-02-05 16:41 ` Emilio Cota
2023-01-11 12:26 ` Daniel P. Berrangé [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=Y76q2HjvfzwLnlBT@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cota@braap.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: 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.