Re: [Xen-devel] Re: [PATCH 0/5] Collected vdso/vsyscall fixes for 3.1
From: Konrad Rzeszutek Wilk <hidden>
Date: 2011-07-27 16:59:35
Also in:
lkml, xen-devel
quoted
quoted
$ test_vsyscall test Testing gettimeofday... vDSO offset = 0.000001s vsyscall offset = 0.000001s Testing time... vDSO offset = 0 vsyscall offset = 0 Testing getcpu... ok! cpu=6 node=0
I bet if you pull a new copy or remove -mavx from Makefile it will work. I got a grossly hacked-up Xen domU booted and everything seems to work.
It did. Both Dom0 and DomU work on AMD and Intel. In regards to the last pv-ops patch - is there no better way? The reason I am asking is the pv-ops hook is just a bandaid for the problem. Is the Xen syscall suppose to be doingsomething extra with the stack perhaps?