Skip to contentSkip to conversation

year 2038 problem on x86-64

DISCUSSION Andi Kleen 1 participant 1 message Sep 22, 2004 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#4 lore raw
Quoted 9 lines · Pavel Machek

Hi!

Quoted 5 lines
Quoted 2 lines

... __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