[Top] [All Lists]

Re: unaligned access

To: Ralf Baechle <>, "Kevin D. Kissell" <>
Subject: Re: unaligned access
From: sathesh babu <>
Date: Fri, 23 Feb 2007 09:48:38 +0000 (GMT)
Cc: sathesh babu <>, Rajat Jain <>,
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=n6RjLV+82WGXCwqqjudRDHRPudETAKusK09k1MRNnSfk0fK841s/nRjFzqQp6QzC9z0A2kcxw5FuyCcB+o4FP7nqZoFZBZP7ALOrpszPs7LM/chWKlcZyfxsg2jMd+7cGZ4GRnew/AH90CNxYFhai5UuEwAfH9zS2sBD3C9bm3U=;
In-reply-to: <>
Original-recipient: rfc822;
It would be good idea to know which process hitting unaligned access and PC.
So that we can try to fix unaligned access when it causes the  performance bottleneck.
Could you please share details about logging the unaligned accesses using sysctl.
Thanks in advance

Ralf Baechle <> wrote:
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.


Here?s a new way to find what you're looking for - Yahoo! Answers
<Prev in Thread] Current Thread [Next in Thread>