From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: sathesh babu <sathesh_edara2003@yahoo.co.in>,
Rajat Jain <rajat.noida.india@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: unaligned access
Date: Fri, 23 Feb 2007 03:06:45 +0000 [thread overview]
Message-ID: <20070223030645.GA1349@linux-mips.org> (raw)
In-Reply-To: <01fc01c75693$195858b0$10eca8c0@grendel>
On Thu, Feb 22, 2007 at 04:06:57PM +0100, Kevin D. Kissell wrote:
> Default behavior in MIPS is to silently fix up and emulate. A MIPS-specific
> system call (sys_sysmips with the command argument of MIPS_FIXADE
> and a parameter agument of zero) allows for this to be overridden, so that
> such accesses will be fatal. It looks as if there was once support to log the events
> to syslog, independently of whether or not they were fixed up, but it doesn't look to me
> as if that still works in 2.6.x kernels.
There used to be a configuration option to allow logging which was a
leftover from the times when I implemented the unaligned emulation. I
did never find it useful later on, so I removed that in almost 9 years
ago and nobody missed it since :-)
But I don't mind putting it back, controllable by sysctl if there is any
demand for it.
Ralf
next prev parent reply other threads:[~2007-02-23 3:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 7:10 unaligned access sathesh babu
2007-02-22 7:53 ` Rajat Jain
2007-02-22 9:18 ` sathesh babu
2007-02-22 15:06 ` Kevin D. Kissell
2007-02-22 15:06 ` Kevin D. Kissell
2007-02-23 3:06 ` Ralf Baechle [this message]
2007-02-23 3:36 ` Atsushi Nemoto
2007-02-23 8:18 ` Kevin D. Kissell
2007-02-23 8:18 ` Kevin D. Kissell
2007-02-23 15:12 ` Atsushi Nemoto
2007-02-23 16:18 ` Ralf Baechle
2007-02-23 16:29 ` Maciej W. Rozycki
2007-02-23 9:48 ` sathesh babu
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=20070223030645.GA1349@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=rajat.noida.india@gmail.com \
--cc=sathesh_edara2003@yahoo.co.in \
/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