>>> On 22.04.14 at 20:34, <konrad.w...@oracle.com> wrote: > With this patch: > [...] > And with an HVM guest poking at the rest of VCPUOPs: VCPUOP_get_physid, > VCPUOP_initialise, and VCPUOP_send_nmi - either before the CPU is up or > when it is up - work. > > That is: the VCPUOP_get_physid would return -EINVAL; VCPUOP_initialise > would return either -EEXIST or 0, and in either case > the content of the ctxt was full of zeros.
Good. > The VCPUOP_send_nmi did cause the HVM to get an NMI and it spitted out > 'Dazed and confused'. It also noticed corruption: > > [ 3.611742] Corrupted low memory at c000fffc (fffc phys) = 00029b00 > [ 2.386785] Corrupted low memory at ffff88000000fff8 (fff8 phys) = > 2990000000000 > > Which is odd because there does not seem to be anything in the path > of hypervisor that would cause this. Indeed. This looks a little like a segment descriptor got modified here with a descriptor table base of zero and a selector of 0xfff8. That corruption needs to be hunted down in any case before enabling VCPUOP_send_nmi for HVM. Jan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
