linux-mips
[Top] [All Lists]

Re: unaligned access

To: kevink@mips.com
Subject: Re: unaligned access
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Sat, 24 Feb 2007 00:12:49 +0900 (JST)
Cc: ralf@linux-mips.org, sathesh_edara2003@yahoo.co.in, rajat.noida.india@gmail.com, linux-mips@linux-mips.org
In-reply-to: <005701c7573f$6aca0890$10eca8c0@grendel>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20070223030645.GA1349@linux-mips.org> <20070223.123630.92584856.nemoto@toshiba-tops.co.jp> <005701c7573f$6aca0890$10eca8c0@grendel>
Sender: linux-mips-bounce@linux-mips.org
On Fri, 23 Feb 2007 09:18:59 +0100, "Kevin D. Kissell" <kevink@mips.com> wrote:
> One thing about the current, system-call based interface that is kind-of
> cool, and different from both what you propose and what was described
> as being implemented for ARM, is that Ralf's scheme is per-thread.
> I don't know if that power really outweighs the ease-of-use aspect
> of being able to manipuate it from the shell command line, but it's 
> not something to throw away lightly.  I have no issues with moving
> the log data, should it be resurrected, from syslog to /sys/kernel/whatever,
> though.

Well, /sys/kernel method can coexist with per-thread FIXADE method.
We can use /sys/kernel (or something) to change default action.  And
sysmips() or something can be used to override it.

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>