Avi Kivity wrote:
On 10/28/2009 12:13 PM, Chris Lalancette wrote:
The kick from i8254 code is pretty bad, as you mention. I forget why it
is needed at all - shouldn't kvm_set_irq() end up kicking the correct
As I understand it, that's not quite how it works. From what I can see, what
On 10/29/2009 10:34 AM, Chris Lalancette wrote:
I'm starting to take a look at this. While this may be a generically useful
cleanup, it occurs to me that even if we call set_irq from the hrtimer
callback, we still have to do the kick_vcpus type thing. Otherwise, we still
have the problem
On 10/27/2009 06:41 PM, Chris Lalancette wrote:
This patch series aims to get kdump working inside a KVM guest.
The current problem with using kdump is that KVM always delivers
PIT interrupts to the BSP, and the BSP only. While this is
technically allowed by the MPS spec, most motherboards
On 10/28/2009 12:13 PM, Chris Lalancette wrote:
The kick from i8254 code is pretty bad, as you mention. I forget why it
is needed at all - shouldn't kvm_set_irq() end up kicking the correct
As I understand it, that's not quite how it works. From what I can see, what
happens is that
This patch series aims to get kdump working inside a KVM guest.
The current problem with using kdump is that KVM always delivers
PIT interrupts to the BSP, and the BSP only. While this is
technically allowed by the MPS spec, most motherboards actually
deliver timer interrupts to *any* LAPIC in