qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Peter Maydell <peter.maydell@linaro.org>,
	Helge Deller <deller@kernel.org>
Cc: Laurent Vivier <laurent@vivier.eu>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [PATCH] tcg/tci: Fix TCI on hppa host and update TCI test matrix
Date: Sun, 7 Jan 2024 22:40:27 +0100	[thread overview]
Message-ID: <7df97a8e-6bb2-482c-86cf-a9dbf2bd2e53@gmx.de> (raw)
In-Reply-To: <CAFEAcA9K4GVcYNe2YvtDxiXC-HBvAXEZzNMA-z9xkpNY4Qf2EQ@mail.gmail.com>

On 1/7/24 16:22, Peter Maydell wrote:
> On Sun, 7 Jan 2024 at 07:20, Helge Deller <deller@kernel.org> wrote:
>>
>> Update the TCI interpreter test matrix for big-endian hosts with
>> big- (hppa, hppa64) and little-endian (x86,x96-64) targets.
>> I used native ppc64 and hppa hosts for those tests.
>>
>> Starting TCI on a hppa host crashed immediately, because hppa is
>> the only archive left where the stack grows upwards.
>> Write-protecting the stack guard page at the top of the stack
>> fixes the crash.
>
> We deliberately dropped support for HPPA hosts, under
> commit a1eaa6281f8b and commit b1cef6d02f84bd8.
> Do we really care enough about trying to run on these
> ancient host CPUs to want to bring it back?
>
> My personal rule of thumb is that if a host CPU is supported
> only by TCI then we are better off saying it is entirely
> unsupported -- in practice the performance will be so
> terrible as to not be something anybody will want to use,
> especially for older architectures which are slow to
> start with.

I can see your point (and the performance is really horrible).
It's not my intention to make hppa a supported TCI platform,
but for me it's a good candidate to at least test TCI on
a big-endian machine, mostly because I have access to some of
such machines.
And, this patch is all what's needed and it's pretty trivial, so
it would be great if it could be accepted.

Helge


  reply	other threads:[~2024-01-07 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07  7:19 [PATCH] tcg/tci: Fix TCI on hppa host and update TCI test matrix Helge Deller
2024-01-07 10:54 ` Philippe Mathieu-Daudé
2024-01-08  7:24   ` Akihiko Odaki
2024-01-07 15:22 ` Peter Maydell
2024-01-07 21:40   ` Helge Deller [this message]
2024-01-08 11:50     ` Philippe Mathieu-Daudé

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=7df97a8e-6bb2-482c-86cf-a9dbf2bd2e53@gmx.de \
    --to=deller@gmx.de \
    --cc=deller@kernel.org \
    --cc=laurent@vivier.eu \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=richard.henderson@linaro.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).