From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Improve o32 syscall handling
Date: Mon, 22 Nov 2004 07:18:54 +0100 [thread overview]
Message-ID: <20041122061854.GA25433@linux-mips.org> (raw)
In-Reply-To: <20041121164557.GQ20986@rembrandt.csv.ica.uni-stuttgart.de>
On Sun, Nov 21, 2004 at 05:45:57PM +0100, Thiemo Seufer wrote:
> For the 64bit Kernel, it
> - checks for unaligned user stack
Why bother, the unaligned exception handler should take care of this.
> - also allows now up to 8 arguments
Quite frankly I'd prefer to see this being handle in userspace. For o32
it's too late to go for that but for N32 / N64 we still may have a chance.
> - LONG_L a2, TI_FLAGS($28) # current->work
> + lw a2, TI_FLAGS($28) # current->work
Flags is a long variable.
Ralf
next prev parent reply other threads:[~2004-11-22 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 16:45 [PATCH] Improve o32 syscall handling Thiemo Seufer
2004-11-22 6:18 ` Ralf Baechle [this message]
2004-11-22 7:00 ` Thiemo Seufer
2004-11-22 7:13 ` Ralf Baechle
2004-11-22 9:37 ` Thiemo Seufer
2004-11-27 0:29 ` Thiemo Seufer
2004-11-23 12:47 ` Gleb O. Raiko
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=20041122061854.GA25433@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=linux-mips@linux-mips.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