From: Andi Kleen <ak@suse.de>
To: Roberto Nibali <ratz@drugphish.ch>
Subject: Re: [discuss] trap int3 problem while porting a user space application and small cleanup patch
Date: Mon, 13 Feb 2006 10:25:43 +0100
User-Agent: KMail/1.8.2
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
References: <43EF6B7D.5080607@drugphish.ch> <200602130157.36084.ak@suse.de> <43F03B7F.2030701@drugphish.ch>
In-Reply-To: <43F03B7F.2030701@drugphish.ch>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200602131025.43826.ak@suse.de>
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 981
Lines: 27

On Monday 13 February 2006 08:55, Roberto Nibali wrote:
> Hello Andi,
> 
> Thanks for your comments.
> 
> >> 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.
> 
> It is a 64bit executable:

Then whatever problem the program has is not enabled to 32bit ioctl emulation.
Maybe it has some generic 64bit issues.

Thanks for looking into it.

-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/