Has it been determined that this change is correct? If yes is it going to be
committed?
Mike
diff -r b6a47b43f4df src/arch/x86/process.cc
--- a/src/arch/x86/process.cc Mon Mar 18 11:24:56 2013 +0100
+++ b/src/arch/x86/process.cc Mon Mar 25 09:46:20 2013 -0600
@@ -98,7 +98,7 @@
vsyscallPage.base = 0xffffffffff600000ULL;
vsyscallPage.size = VMPageSize;
vsyscallPage.vtimeOffset = 0x400;
- vsyscallPage.vgettimeofdayOffset = 0x410;
+ vsyscallPage.vgettimeofdayOffset = 0x0;
On Jan 30, 2013, at 10:59 PM, Nilay wrote:
>
> On Wed, January 30, 2013 3:43 pm, Steve Reinhardt wrote:
>> The offset would have to be part of the kernel ABI... that is, different
>> versions of the library would still have to use the same offsets if they
>> want to work on the same kernel. It's possible that there was a version
>> change in the kernel that changed the ABI, and if we at some point updated
>> the fake kernel version we report to glibc without updating the offset
>> then
>> that could explain why things are breaking.
>>
>
> We changed the kernel version in August last year. The file which contains
> the kernel version should contain a comment that this syscall setup needs
> to be checked. I am guessing we should accept this patch. We would also
> need to check if other architectures are affected since kernel versions
> were updated for all of them.
>
> --
> Nilay
>
> _______________________________________________
> gem5-dev mailing list
> [email protected]
> http://m5sim.org/mailman/listinfo/gem5-dev
>
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
