Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1206568
| From | Paolo Bonzini <pbonzini@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/2] KVM: x86: set TMR when the interrupt is accepted |
| Date | 2015-08-13 09:40 +0200 |
| Message-ID | <pWVhg-53B-29@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <pTlah-fp-9@gated-at.bofh.it> <pTlDk-NT-1@gated-at.bofh.it> <pTyAy-2Qy-5@gated-at.bofh.it> <pTEwh-3hI-15@gated-at.bofh.it> <pWUlc-3IA-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 13/08/2015 08:35, Zhang, Yang Z wrote: >> 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. I guess I can cause a vmexit on level-triggered interrupts, it's not a big deal, but no weasel words, please. What's going to break, and where is it documented? Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
RE: [PATCH 1/2] KVM: x86: set TMR when the interrupt is accepted "Zhang, Yang Z" <yang.z.zhang@intel.com> - 2015-08-13 08:40 +0200 Re: [PATCH 1/2] KVM: x86: set TMR when the interrupt is accepted Paolo Bonzini <pbonzini@redhat.com> - 2015-08-13 09:40 +0200
csiph-web