From: Paul Mundt <lethal@linux-sh.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] sh4: add signal handling support for user space emulator
Date: Wed, 21 Nov 2007 17:40:48 +0900 [thread overview]
Message-ID: <20071121084048.GA24217@linux-sh.org> (raw)
In-Reply-To: <aec7e5c30711210016u10dbcf13r6a8bb75abd3625ac@mail.gmail.com>
On Wed, Nov 21, 2007 at 05:16:55PM +0900, Magnus Damm wrote:
> +#define MOVW(n) (0x9300|((n)-2)) /* Move mem word at PC+n to R3 */
> +#define TRAP_NOARG 0xc310 /* Syscall w/no args (NR in R3) SH3/4 */
> +#define OR_R0_R0 0x200b /* or r0,r0 (insert to avoid hardware bug) */
This is legacy SH-4 errata, and does not pop up on any of the other
parts. These days all SH-4 parts return through the vsyscall page, where
we deal with this errata directly without having to push it in to the
return frame. While you might not want to deal with implementing the
vsyscall page, there's definitely no point in crapping up the return
frame with this chip errata in the general case.
next prev parent reply other threads:[~2007-11-21 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 8:16 [Qemu-devel] [PATCH] sh4: add signal handling support for user space emulator Magnus Damm
2007-11-21 8:40 ` Paul Mundt [this message]
2007-11-22 4:59 ` Magnus Damm
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=20071121084048.GA24217@linux-sh.org \
--to=lethal@linux-sh.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 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).