Re: [PATCH v10 0/7] Use eoi to track RTC interrupt delivery status

[Marcelo Tosatti <mtosatti@redhat.com>]

On Thu, Apr 11, 2013 at 07:21:34PM +0800, Yang Zhang wrote:
> From: Yang Zhang <yang.z.zhang@Intel.com>
> 
> Current interrupt coalescing logci which only used by RTC has conflict
> with Posted Interrupt.
> 
> This patch introduces a new mechinism to use eoi to track interrupt:
> When delivering an interrupt to vcpu, the pending_eoi set to number of
> vcpu that received the interrupt. And decrease it when each vcpu writing
> eoi. No subsequent RTC interrupt can deliver to vcpu until all vcpus
> write eoi.
> 
> Changes from v9 to v10
> * Remove irq check and line_status check from rtc_irq_check_coalesced() to
>   kvm_ioapic_set_irq().
> * Rebase on top of KVM.
> 
> Changes from v8 to v9
> * Removing pass vector to __rtc_irq_eoi_tracking_restore_one.
> * Rebase on top of KVM.
> 
> Changes from v7 to v8
> * Revamping restore logic.
> * Add BUG_ON to check pending_eoi.
> * Rebase on top of KVM.
> 
> Yang Zhang (7):
>   KVM: Add vcpu info to ioapic_update_eoi()
>   KVM: Introduce struct rtc_status
>   KVM: Return destination vcpu on interrupt injection
>   KVM: Add reset/restore rtc_status support
>   KVM: Force vmexit with virtual interrupt delivery
>   KVM: Let ioapic know the irq line status
>   KVM: Use eoi to track RTC interrupt delivery status

Applied, thanks.