From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.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
User-Agent: KMail/1.8.2
Cc: Roberto Nibali <ratz@drugphish.ch>, linux-kernel@vger.kernel.org
References: <43EF6B7D.5080607@drugphish.ch>
In-Reply-To: <43EF6B7D.5080607@drugphish.ch>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602130157.36084.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1528
Lines: 38

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/