Bug#676360: xen: oops at atomic64_read_cx8+0x4

2012-06-07 Thread Jonathan Nieder
Sergio Gelato wrote[1]: That 3.4.1-1~experimental.1 build (3.4-trunk-686-pae #1 SMP Wed Jun 6 15:11:31 UTC 2012 i686 GNU/Linux) is even less well-behaved under Xen: I'm getting a kernel OOPS at EIP: [c1168e54] atomic64_read_cx8+0x4/0xc SS:ESP e021:ca853c6c The top of

Bug#676360: xen: oops at atomic64_read_cx8+0x4

2012-06-07 Thread Andrea Arcangeli
On Thu, Jun 07, 2012 at 02:33:33AM -0500, Jonathan Nieder wrote: Sergio Gelato wrote[1]: That 3.4.1-1~experimental.1 build (3.4-trunk-686-pae #1 SMP Wed Jun 6 15:11:31 UTC 2012 i686 GNU/Linux) is even less well-behaved under Xen: I'm getting a kernel OOPS at

Bug#676360: xen: oops at atomic64_read_cx8+0x4

2012-06-07 Thread Sergio Gelato
* Andrea Arcangeli [2012-06-07 12:33:55 +0200]: I guess if Xen can't be updated to handle an atomic64_read on a pmd in the guest, I'm not sure if it makes a difference, but just in case: I observed the problem in a dom0. we can add a pmd_read paravirt op? Or if we don't want to