sched_setaffinity usability
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]
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]
Quoted 7 lines · Ingo Molnar
Quoted 1 line · Ingo Molnar
x86-64 has a VDSO page as well, [...]
hm, i'm not sure this is the case. It does have a vsyscall page but doesnt fill out
AT_SYSINFO. ia64 seems to have something like a vdso, passed down viaAT_SYSINFO.
Yes, the x86-64 64bit vsyscalls predate all the vDSO work and haven't been updated. It has a vDSO for 32bit programs though.
I guess it would be not that much work to add it for 64bit too. I would not be opposed to it if somebody sends me patches.
This means my only objection is that an dwarf2 unwind table written without the .cfi_* support in the assembler is incredibly ugly and unmaintainable. I really don't want to have more such ugly tables. I guess it would be best to force an binutils update for dwarf2 information.
-Andi