Re: [PATCH 0/3] x86/paravirt: Fix baremetal paravirt MSR ops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/17/2015 8:29 AM, Paolo Bonzini wrote:


On 17/09/2015 17:27, Arjan van de Ven wrote:

( We should double check that rdmsr()/wrmsr() results are never left
    uninitialized, but are set to zero or so, for cases where the
return code is not
    checked. )

It sure looks like native_read_msr_safe doesn't clear the output if
the rdmsr fails.

I'd suggest to return some poison not just 0...

What about 0 + WARN?

why 0?

0xdeadbeef or any other pattern (even 0x3636363636) makes more sense (of course also WARN... but most folks don't read dmesg for WARNs)

(it's the same thing we do for list or slab poison stuff)

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux