Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: <ralf@linux-mips.org>, "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Cc: <sathesh_edara2003@yahoo.co.in>, <rajat.noida.india@gmail.com>,
	<linux-mips@linux-mips.org>
Subject: Re: unaligned access
Date: Fri, 23 Feb 2007 09:18:59 +0100	[thread overview]
Message-ID: <005701c7573f$6aca0890$10eca8c0@grendel> (raw)
In-Reply-To: 20070223.123630.92584856.nemoto@toshiba-tops.co.jp

> So how about this interface?
> 
> 1. echo show > /sys/kernel/unaligned_action
> 
> Show register dump and processor name at each unaligned exception,
> using show_regs() or someting.
> 
> 2. echo quiet > /sys/kernel/unaligned_action
> 
> Siliently fixup unaligned exceptions.
> 
> 3. cat /sys/kernel/unaligned_instructions
> 
> Print unaligned_instructions variable.
> 
> 
> Creating files in /sys/kernel is fairly simple:
> 
> subsys_create_file(&kernel_subsys, &foo_attr);
> 
> Any comments?

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.

            Regards,

            Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: ralf@linux-mips.org, Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: sathesh_edara2003@yahoo.co.in, rajat.noida.india@gmail.com,
	linux-mips@linux-mips.org
Subject: Re: unaligned access
Date: Fri, 23 Feb 2007 09:18:59 +0100	[thread overview]
Message-ID: <005701c7573f$6aca0890$10eca8c0@grendel> (raw)
Message-ID: <20070223081859.r41k2KkUO7oikwYSfxw9xvxkRwVDD1gDRLd3szy2xJM@z> (raw)
In-Reply-To: 20070223.123630.92584856.nemoto@toshiba-tops.co.jp

> So how about this interface?
> 
> 1. echo show > /sys/kernel/unaligned_action
> 
> Show register dump and processor name at each unaligned exception,
> using show_regs() or someting.
> 
> 2. echo quiet > /sys/kernel/unaligned_action
> 
> Siliently fixup unaligned exceptions.
> 
> 3. cat /sys/kernel/unaligned_instructions
> 
> Print unaligned_instructions variable.
> 
> 
> Creating files in /sys/kernel is fairly simple:
> 
> subsys_create_file(&kernel_subsys, &foo_attr);
> 
> Any comments?

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.

            Regards,

            Kevin K.

  reply	other threads:[~2007-02-23 11:39 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
2007-02-23  3:36         ` Atsushi Nemoto
2007-02-23  8:18           ` Kevin D. Kissell [this message]
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='005701c7573f$6aca0890$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=rajat.noida.india@gmail.com \
    --cc=ralf@linux-mips.org \
    --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