From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>
Subject: Re: [PATCH] system: Try hardware accelerators (KVM, HVF) before software one (TCG)
Date: Fri, 3 Jan 2025 12:48:28 -0500 [thread overview]
Message-ID: <Z3gi7ANjATS7Hxyx@x1n> (raw)
In-Reply-To: <d06dd874-c6a5-49ba-89c1-60668ad639d4@linaro.org>
On Fri, Jan 03, 2025 at 06:16:38PM +0100, Philippe Mathieu-Daudé wrote:
> On 3/1/25 16:15, Daniel P. Berrangé wrote:
> > On Fri, Jan 03, 2025 at 04:05:58PM +0100, Philippe Mathieu-Daudé wrote:
> > > As Daniel suggested [*]:
> > >
> > > > We should consider to rank HVF above TCG, on the basis
> > > > that HW acceleration is faster and should provide a
> > > > host<->guest security boundary that we don't claim for TCG
> > >
> > > [*] https://lore.kernel.org/qemu-devel/Z07YASl2Pd3CPtjE@redhat.com/
> >
> > Note, my statement above was on the basis that HVF passes all our
> > functional tests, thus indicating a decent level of confidence
> > in the correctness of the HVF impl.
>
> Indeed, I forgot about that, and only tested in my 'HVF-only'
> directory before posting, but ...
>
> > If anyone knows any show stopper problems with HVF that would
> > justify blocking its promotion ahead of TCG.... say now.
>
> ... here we go:
>
> 3/15 qemu:qtest+qtest-aarch64 / qtest-aarch64/migration-test ERROR
> 0.88s killed by signal 11 SIGSEGV
Hmm.. I think migration-test specifies either kvm or tcg in all its tests,
so I don't yet know why this patch can affect it..
migrate_start():
cmd_source = g_strdup_printf("-accel kvm%s -accel tcg "
"-machine %s,%s "
...);
May need a closer look on the crashed stack.
--
Peter Xu
next prev parent reply other threads:[~2025-01-03 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 15:05 [PATCH] system: Try hardware accelerators (KVM, HVF) before software one (TCG) Philippe Mathieu-Daudé
2025-01-03 15:15 ` Daniel P. Berrangé
2025-01-03 17:16 ` Philippe Mathieu-Daudé
2025-01-03 17:48 ` Peter Xu [this message]
2025-01-04 11:28 ` Phil Dennis-Jordan
2025-01-06 18:43 ` Daniel P. Berrangé
2025-01-08 8:36 ` Phil Dennis-Jordan
2025-01-06 17:33 ` Richard Henderson
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=Z3gi7ANjATS7Hxyx@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=dbarboza@ventanamicro.com \
--cc=farosas@suse.de \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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 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.