RE: [PATCH 1/2] KVM: x86: set TMR when the interrupt is accepted
From: Zhang, Yang Z
Date: Thu Aug 13 2015 - 02:36:10 EST
Zhang, Yang Z wrote on 2015-08-04:
> Paolo Bonzini wrote on 2015-08-04:
>> On 04/08/2015 02:46, Zhang, Yang Z wrote:
>>>> It is a problem for split irqchip, where the EOI exit bitmap can
>>>> be inferred from the IOAPIC routes but the TMR cannot. The
>>>> hardware behavior on the other hand can be implemented purely within the LAPIC.
>>> So updating the TMR within LAPIC is the only solution to handle it?
>> It's the simplest and the one that makes most sense. Considering
>> that TMR is a pretty obscure feature, it's unlikely that it will be
>> accelerated in the future.
> You may be right. It is safe if no future hardware plans to use it.
> Let me check with our hardware team to see whether it will be used or not in future.
After checking with Jun, there is no guarantee that the guest running on another CPU will operate properly if hypervisor modify the vTMR from another CPU. So the hypervisor should not to do it.
> Best regards,
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/