lkml.org 
[lkml]   [2011]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: RFD: x32 ABI system call numbers
Date
On Thursday 01 September 2011 15:13:30, H. Peter Anvin wrote:
> On 09/01/2011 06:30 AM, Avi Kivity wrote:
> > On 08/31/2011 08:09 PM, H. Peter Anvin wrote:
> >>> I really think that "x32" should try to aim *VERY* hard at using the
> >>> 64-bit system calls, and seeing itself as being a "32-bit application
> >>> in a 64-bit world". That's not just true for time_t (which I think
> >>> should be 64-bit on anything new that expects to survive for any
> >>> amount of time), but in general.
> >>
> >> We're trying for it. The things we're trying to avoid is to muck (too
> >> much) with the compat layer for the mega-multiplex system calls like
> >> ioctl. We can't just use the 64-bit ioctl because ioctl structures
> >> generally contain pointers.
> >>
> >
> > struct iovec
> > {
> > void __user *iov_base; /* BSD uses caddr_t (1003.1g requires
> > void *) */
> > __kernel_size_t iov_len; /* Must be size_t (1003.1g) */
> > } __attribute__((x32_abi_64));
> >
> > typedef long time_t __attribute__((x32_abi_64));
> >
> > The x32_abi_64 attribute converts pointers and longs back to 64-bit and
> > adjusts the alignment accordingly. If we tag all userspace visible
> > structures with this attribute, we can use the 64-bit ABI without changes.

I would expect no new gcc extension to be needed for that -- there's the
mode attribute (you can read DI as 64-bit):

typedef void * __kernel_ptr64 __attribute ((mode(DI)));

struct iovec
{
__kernel_ptr64 iov_base;
...
};

--
Pedro Alves


\
 
 \ /
  Last update: 2011-09-02 02:51    [W:0.081 / U:23.240 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site