From: Andi Kleen <ak@muc.de>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: year 2038 problem on x86-64
Date: Thu, 23 Sep 2004 00:51:21 +0200 [thread overview]
Message-ID: <m3y8j19aty.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2HnWp-3b7-25@gated-at.bofh.it> (Pavel Machek's message of "Thu, 23 Sep 2004 00:40:09 +0200")
Pavel Machek <pavel@suse.cz> writes:
> Hi!
>
>> >
>> > ... __ARCH_WANT_SYS_TIME actually is set on x86-64.
>>
>> But it's not used. It declares an own sys_time64 in arch/x86_64
>> By default the vsyscall code is used.
>
> So should __ARCH_WANT_SYS_TIME be killed from x86_64?
No. The 32bit emulation uses it.
In theory you could make it conditional on CONFIG_IA32_EMULATION,
but that would be probably overkill.
-Andi
next parent reply other threads:[~2004-09-22 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2HnMR-35F-55@gated-at.bofh.it>
[not found] ` <2HnMR-35F-57@gated-at.bofh.it>
[not found] ` <2HnMR-35F-53@gated-at.bofh.it>
[not found] ` <2HnWp-3b7-25@gated-at.bofh.it>
2004-09-22 22:51 ` Andi Kleen [this message]
[not found] <2Hn0k-2wz-9@gated-at.bofh.it>
[not found] ` <2HnjK-2Ha-3@gated-at.bofh.it>
2004-09-22 22:27 ` year 2038 problem on x86-64 Andi Kleen
2004-09-22 22:34 ` Pavel Machek
2004-09-22 21:30 year 9223372034708485227 problem Pavel Machek
2004-09-22 21:45 ` year 2038 problem on x86-64 Pavel Machek
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=m3y8j19aty.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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