On 12/18/2015 06:19 PM, Pavel Fedin wrote:
I realize that it's perhaps too late, because patches are already on
Linux-next, but i have one concern... May be it's not too
I dislike implementing architecture-dependent exit code where we could
implement an architecture-independent one.
As far as i understand this code, KVM_EXIT_HYPERV is called when one of three
MSRs are accessed. But, shouldn't we have implemented
instead something more generic, like KVM_EXIT_REG_IO, which would work similar
to KVM_EXIT_PIO or KVM_EXIT_MMIO, but carry register
code and value?
This would allow us to solve the same task which we have done here, but this
solution would be reusable for other devices and other
archirectures. What if in future we have more system registers to emulate in
I write this because at one point i suggested similar thing for ARM64 (but i
never actually wrote it), to emulate physical CP15
timer. And it would require exactly the same capability - process some trapped
system register accesses in userspace.
Samsung Electronics Research center Russia
we have discussed this AFAIR. HyperV guest implementation
is available in Linux kernel and thus technically we can have
this stuff on any platform.
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html