Hello! > - How do you find out that your guest is Linux?
Yes, i agree. No way. And it's not host kernel's job anyway. > - How do you ensure that the guest will not require the virtual timer? Agree again. Except device tree, no way. If the guest has its own hardcoded assumptions, it's doomed. (*) > - Who is going to maintain this new ABI that would exist for the sole > benefit of broken hardware? The ABI is simple, just one more exit code. And it's not only for broken hardware. It is quite legitimate thing to have GICv3 without v2 backwards compatibility. > - What is wrong with exposing another, memory mapped timer and remove > the architected timer entirely? Well... qemu guys don't want to remove CP15, i already proposed it, and it was very simple thing to do. :) But, again, this is also device-tree-based, the same concern applies as to (*). Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia -- 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
