[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMe9rOqL_TJW-XJz6e8_iewUypmsx8MXeaRfq-aATx3sFDBxcw@mail.gmail.com>
Date: Tue, 21 Jan 2014 04:22:59 -0800
From: "H.J. Lu" <hjl.tools@...il.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Christoph Hellwig <hch@...radead.org>,
linux-arch <linux-arch@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Will Deacon <Will.Deacon@....com>
Subject: Re: [PATCH 0/8] Update kernel uabi header files for x32
On Tue, Jan 21, 2014 at 4:04 AM, Catalin Marinas
<catalin.marinas@....com> wrote:
> On Mon, Jan 20, 2014 at 05:46:41PM +0000, H. Peter Anvin wrote:
>> On 12/28/2013 08:33 AM, Christoph Hellwig wrote:
>> > On Fri, Dec 27, 2013 at 02:14:16PM -0800, H.J. Lu wrote:
>> >> X32 uses the same kernel system call interface as x86-64 for many
>> >> system calls. However, "long" is 64-bit for x86-64 and is 32-bit for
>> >> x32. Where long or unsigned long are used in struct types for such
>> >> system calls, they are wrong for x32. __kernel_[u]long_t is [unsigned]
>> >> long for all ABIs other than x32. I am submitting 8 patches to replace
>> >> long or unsigned long with __kernel_[u]long_t so that those struct types
>> >> can be used with x32 system calls.
>
> Does this mean that you are changing the x32 ABI (or it hasn't been
> declared stable yet)?
We don't change x32 ABI. Today kernel uabi header files are
incompatible with x32 ABI in user space. My patches fix them
so that they can be used in user space.
--
H.J.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists