From: Stefan Weil <sw@weilnetz.de>
To: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Helge Deller <deller@gmx.de>, Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures
Date: Wed, 10 Apr 2019 08:24:30 +0200 [thread overview]
Message-ID: <eba5dd64-53c7-4daa-a851-00cf9d7aff25@weilnetz.de> (raw)
In-Reply-To: <b6df5f4b-d567-bab0-fb9d-78ca20154ec7@redhat.com>
On 10.04.19 08:07, Thomas Huth wrote:
> That's great, good to know that you're still interested in TCI! ... but
> I think one of the main problems is still that we completely lack test
> coverage for TCI - the code always is in danger to bit-rot if it is not
> tested by default.
Ideally it would be possible to build a QEMU executable with KVM (on
those hosts which support it), native TCG and TCI, so users could decide
at runtime which of the three alternatives they want. Then CI builds
(not necessarily production builds) would include all source files and
could also run tests with TCI if desired.
It was not possible to have native and interpreted TCG selectable at
runtime when I started the TCI implementation, but time went on and QEMU
and TCG evolved, so maybe it is now possible.
Stefan
next prev parent reply other threads:[~2019-04-10 6:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 18:57 [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures Helge Deller
2019-04-04 19:24 ` Philippe Mathieu-Daudé
2019-04-05 7:14 ` Helge Deller
2019-04-05 1:34 ` Peter Maydell
2019-04-05 7:56 ` Helge Deller
2019-04-05 7:56 ` Helge Deller
2019-04-05 8:26 ` Daniel P. Berrangé
2019-04-05 9:02 ` Helge Deller
2019-04-05 9:10 ` Philippe Mathieu-Daudé
2019-04-05 9:13 ` Peter Maydell
2019-04-05 9:13 ` Peter Maydell
2019-04-05 9:15 ` Daniel P. Berrangé
2019-04-05 8:47 ` Philippe Mathieu-Daudé
2019-04-05 8:47 ` Philippe Mathieu-Daudé
2019-04-05 9:02 ` Daniel P. Berrangé
2019-04-05 9:02 ` Daniel P. Berrangé
2019-04-05 9:16 ` Philippe Mathieu-Daudé
2019-04-05 9:16 ` Philippe Mathieu-Daudé
2019-04-09 19:46 ` Stefan Weil
2019-04-09 19:46 ` Stefan Weil
2019-04-09 20:39 ` Richard Henderson
2019-04-10 6:17 ` Stefan Weil
2019-04-11 6:21 ` Richard Henderson
2019-04-10 6:07 ` Thomas Huth
2019-04-10 6:07 ` Thomas Huth
2019-04-10 6:24 ` Stefan Weil [this message]
2019-04-10 8:22 ` Thomas Huth
2019-04-10 19:22 ` Stefan Weil
2019-04-10 7:48 ` Thomas Huth
2019-04-10 7:48 ` Thomas Huth
2019-04-06 8:59 ` 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=eba5dd64-53c7-4daa-a851-00cf9d7aff25@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=deller@gmx.de \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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.