Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "sathesh babu" <sathesh_edara2003@yahoo.co.in>,
	"Rajat Jain" <rajat.noida.india@gmail.com>
Cc: <linux-mips@linux-mips.org>
Subject: Re: unaligned access
Date: Thu, 22 Feb 2007 16:06:57 +0100	[thread overview]
Message-ID: <01fc01c75693$195858b0$10eca8c0@grendel> (raw)
In-Reply-To: 80178.32924.qm@web7903.mail.in.yahoo.com

[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]

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.

            Regards,

            Kevin K.
  ----- Original Message ----- 
  From: sathesh babu 
  To: Rajat Jain 
  Cc: linux-mips@linux-mips.org 
  Sent: Thursday, February 22, 2007 10:18 AM
  Subject: Re: unaligned access


  Thanks Rajan.

  In case of arm processor, the alignment trap behavior can be changed by simply echo a number into  /proc/sys/debug/alignment 

  bit             behavior when set
  ---             -----------------
  0               A user process performing an unaligned memory access
                  will cause the kernel to print a message indicating
                  process name, pid, pc, instruction, address, and the
                  fault code.
  1               The kernel will attempt to fix up the user process
                  performing the unaligned access.  This is of course
                  slow (think about the floating point emulator) and
                  not recommended for production use.
  2               The kernel will send a SIGBUS signal to the user process
                  performing the unaligned access.

  I would like to know  Is there similar type of implimentation avalilable for MIPS processor in linux-2.6.12 kernel to view or log the unaligned access addresses and corresponding processor ID.

  Regards,
  Sathesh


  Rajat Jain <rajat.noida.india@gmail.com> wrote:
    On 2/22/07, sathesh babu wrote:
    > Hi,
    > I have ported linux-2.6.12 kernel on MIPS processor.I would like to
    > print the warning messges whenenver kernel or user code try to access
    > unaligned address ( including proceor ID ).
    > Is there any configuration option avaliable in the kernel to view
    > the unaligned address?

    Ummm ... not sure about MIPS, but in i386, exception 17 is raised for
    every unaligned access. alignment_check() is invoked for every such
    access.

    Regards,

    Rajat






------------------------------------------------------------------------------
  Here's a new way to find what you're looking for - Yahoo! Answers 

[-- Attachment #2: Type: text/html, Size: 5625 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: sathesh babu <sathesh_edara2003@yahoo.co.in>,
	Rajat Jain <rajat.noida.india@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: unaligned access
Date: Thu, 22 Feb 2007 16:06:57 +0100	[thread overview]
Message-ID: <01fc01c75693$195858b0$10eca8c0@grendel> (raw)
Message-ID: <20070222150657.5AiLoRmGlaqnnpgUObuh231cs2zv6v1ReHKnWnKsI6k@z> (raw)
In-Reply-To: 80178.32924.qm@web7903.mail.in.yahoo.com

[-- Attachment #1: Type: text/plain, Size: 2531 bytes --]

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.

            Regards,

            Kevin K.
  ----- Original Message ----- 
  From: sathesh babu 
  To: Rajat Jain 
  Cc: linux-mips@linux-mips.org 
  Sent: Thursday, February 22, 2007 10:18 AM
  Subject: Re: unaligned access


  Thanks Rajan.

  In case of arm processor, the alignment trap behavior can be changed by simply echo a number into  /proc/sys/debug/alignment 

  bit             behavior when set
  ---             -----------------
  0               A user process performing an unaligned memory access
                  will cause the kernel to print a message indicating
                  process name, pid, pc, instruction, address, and the
                  fault code.
  1               The kernel will attempt to fix up the user process
                  performing the unaligned access.  This is of course
                  slow (think about the floating point emulator) and
                  not recommended for production use.
  2               The kernel will send a SIGBUS signal to the user process
                  performing the unaligned access.

  I would like to know  Is there similar type of implimentation avalilable for MIPS processor in linux-2.6.12 kernel to view or log the unaligned access addresses and corresponding processor ID.

  Regards,
  Sathesh


  Rajat Jain <rajat.noida.india@gmail.com> wrote:
    On 2/22/07, sathesh babu wrote:
    > Hi,
    > I have ported linux-2.6.12 kernel on MIPS processor.I would like to
    > print the warning messges whenenver kernel or user code try to access
    > unaligned address ( including proceor ID ).
    > Is there any configuration option avaliable in the kernel to view
    > the unaligned address?

    Ummm ... not sure about MIPS, but in i386, exception 17 is raised for
    every unaligned access. alignment_check() is invoked for every such
    access.

    Regards,

    Rajat






------------------------------------------------------------------------------
  Here's a new way to find what you're looking for - Yahoo! Answers 

[-- Attachment #2: Type: text/html, Size: 5625 bytes --]

  reply	other threads:[~2007-02-22 15:06 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 [this message]
2007-02-22 15:06       ` Kevin D. Kissell
2007-02-23  3:06       ` Ralf Baechle
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='01fc01c75693$195858b0$10eca8c0@grendel' \
    --to=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