From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Roberto Nibali <ratz@drugphish.ch>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] trap int3 problem while porting a user space application and small cleanup patch
Date: Mon, 13 Feb 2006 01:57:35 +0100 [thread overview]
Message-ID: <200602130157.36084.ak@suse.de> (raw)
In-Reply-To: <43EF6B7D.5080607@drugphish.ch>
On Sunday 12 February 2006 18:08, Roberto Nibali wrote:
> Hello,
>
> For a while I've been working on a little tool called mpt-status to be
> able to monitor LSI based controllers. The source can be found here:
>
> http://www.drugphish.ch/~ratz/mpt-status/
>
> The issue I'm trying to track down now is why I cannot get it to work on
> a x86_64 kernel (Sun Fire V20z with AMD Opteron(tm) Processor 252 on
> SLES 9 PL3). I suspect 32/64 bit issues between in my ioctl message
> passing between user space and kernel space.
Quite possible. The mpt ioctls would need a ioctl conversion handler
to allow a 32bit program to use the 64bit ioctls. Or just use a 64bit
executable.
> Unfortunately when I strace
> the kernel spits out tons of following entries:
Some kernel versions printed that with strace. I think I fixed it in
mainline, but I can't remember if it was fixed in SLES9 too (apparently not)
It's fairly harmless, just ignore it. If it really bothers you you can
turn it off with echo 0 > /proc/sys/debug/exception-trace
>
> Attached is a small code style cleanup patch that resulted from my
> skimming through the arch/x86_64/kernel/traps.c code to figure out what
> went haywire. If Andi is ok with it, please consider applying.
Hmm, ok applied.
-Andi
next prev parent reply other threads:[~2006-02-13 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 17:08 trap int3 problem while porting a user space application and small cleanup patch Roberto Nibali
2006-02-13 0:57 ` Andi Kleen [this message]
2006-02-13 7:55 ` [discuss] " Roberto Nibali
2006-02-13 9:25 ` Andi Kleen
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=200602130157.36084.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
/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