From: Arnd Bergmann <arnd@arndb.de>
To: linux-arch@vger.kernel.org
Cc: Vineet.Gupta1@synopsys.com, linux-kernel@vger.kernel.org,
James Hogan <james.hogan@imgtec.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: new architectures, time_t __kernel_long_t
Date: Wed, 14 Nov 2012 12:18:01 +0000 [thread overview]
Message-ID: <201211141218.02105.arnd@arndb.de> (raw)
Since we are in the review phase for two new architectures that we
should be merging into the mainline kernel, I think we need to
come up with a solution for making them use a proper 64-bit time_t.
Right now, the only 32-bit user space interface we have to use 64-bit
time_t is the x32 side of x86-64, and that works by overriding all
"long" sized types to be 64 bit at the ABI level, which we don't
want for pure 32 bit architectures.
I would suggest we make 64-bit time_t, clock_t and suseconds_t the
default in include/asm-generic/posix_types.h and change all existing
32 bit users of that file to provide an override to define these
as "long".
The other types that are used as 64 bit on x32 are ino_t, nlink_t,
size_t, ssize_t, ptrdiff_t, and off_t.
Obviously, we want to use 64-bit off_t, but this is achieved already
through loff_t, which is used in all places in the asm-generic
ABI anyway (the syscalls using off_t are stripped out). I don't
think we want to have the other ones set to 64 bit on ARC or Meta,
although I'm not 100% sure about ino_t and nlink_t.
Arnd
next reply other threads:[~2012-11-14 12:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 12:18 Arnd Bergmann [this message]
2012-11-14 12:48 ` new architectures, time_t __kernel_long_t Geert Uytterhoeven
2012-11-14 16:26 ` H. Peter Anvin
2012-11-14 16:26 ` H. Peter Anvin
2012-11-15 9:14 ` Arnd Bergmann
2012-11-15 9:14 ` Arnd Bergmann
2012-11-15 13:59 ` H.J. Lu
2012-11-15 14:36 ` Arnd Bergmann
2012-11-15 14:42 ` H.J. Lu
2012-11-15 15:10 ` H. Peter Anvin
2012-12-21 4:57 ` Al Viro
2012-12-21 5:00 ` H. Peter Anvin
2012-12-21 5:02 ` Al Viro
2012-12-21 5:05 ` H. Peter Anvin
2012-12-21 5:19 ` Al Viro
2012-12-21 5:47 ` H. Peter Anvin
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=201211141218.02105.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Vineet.Gupta1@synopsys.com \
--cc=hpa@zytor.com \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).