qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Cc: mark.cave-ayland@ilande.co.uk
Subject: Re: [RFC PATCH] linux-user/sparc: Implement v8plus signals
Date: Tue, 15 Jun 2021 07:44:19 -0700	[thread overview]
Message-ID: <2a3fb13c-d793-c910-7f86-0b021d2c1642@linaro.org> (raw)
In-Reply-To: <a8938653-3f26-ba97-3672-ff10e56a9a60@vivier.eu>

On 6/14/21 11:48 PM, Laurent Vivier wrote:
> Le 26/05/2021 à 03:13, Richard Henderson a écrit :
>> Sparc v8plus is a sparc64 running a 32-bit ABI.
>> The significant difference vs sparc32 is that all 64 bits of
>> the %g and %o registers, plus %xcc, are saved across interrupts,
>> context switches, and signals.
>>
>> There's a special marker in the saved %psr value that's used to
>> indicate that %xcc and the high bits are present in the frame.
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>>
>> I have been unable to find an extant v8plus distribution with
>> which to test this beyond compilation.  Thus the RFC.  I know
>> debian used to have one, but they have moved to pure sparc64 now.
>>
>> Thoughts?
> 
> In my test, I use debian wheezy, and it seems to be sparc32plus v8+:
> 
> $ file chroot/sparc/wheezy/bin/ls
> chroot/sparc/wheezy/bin/ls: ELF 32-bit MSB executable, SPARC32PLUS, V8+ Required, total store
> ordering, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux
> 2.6.26, BuildID[sha1]=3fdfb5b9f829824f6110b7a2d91efd9947614263, stripped
> 
> I get wheezy from http://archive.debian.org/debian
> 
> If you want I can make a try with your patch.

Yes, please.


r~



  reply	other threads:[~2021-06-15 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  1:13 [RFC PATCH] linux-user/sparc: Implement v8plus signals Richard Henderson
2021-06-15  6:48 ` Laurent Vivier
2021-06-15 14:44   ` Richard Henderson [this message]
2021-06-16 18:43     ` Laurent Vivier

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=2a3fb13c-d793-c910-7f86-0b021d2c1642@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=laurent@vivier.eu \
    --cc=mark.cave-ayland@ilande.co.uk \
    --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 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).