From: Paolo Bonzini <pbonzini@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Yang Zhang <yang.z.zhang@intel.com>,
kvm@vger.kernel.org, mtosatti@redhat.com,
xiantao.zhang@intel.com
Subject: Re: [PATCH v8 0/7] Use eoi to track RTC interrupt delivery status
Date: Tue, 09 Apr 2013 18:27:10 +0200 [thread overview]
Message-ID: <5164415E.9090101@redhat.com> (raw)
In-Reply-To: <20130409070815.GP17919@redhat.com>
Il 09/04/2013 09:08, Gleb Natapov ha scritto:
>> > 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.
>> >
> Only minor comment from me to this one. Paolo, Marcelo any comments?
>
No, thanks.
Paolo
prev parent reply other threads:[~2013-04-09 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 14:17 [PATCH v8 0/7] Use eoi to track RTC interrupt delivery status Yang Zhang
2013-04-08 14:17 ` [PATCH v8 1/7] KVM: Add vcpu info to ioapic_update_eoi() Yang Zhang
2013-04-08 14:17 ` [PATCH v8 2/7] KVM: Introduce struct rtc_status Yang Zhang
2013-04-08 14:17 ` [PATCH v8 3/7] KVM: Return destination vcpu on interrupt injection Yang Zhang
2013-04-08 14:17 ` [PATCH v8 4/7] KVM: Add reset/restore rtc_status support Yang Zhang
2013-04-09 7:01 ` Gleb Natapov
2013-04-09 7:06 ` Zhang, Yang Z
2013-04-08 14:17 ` [PATCH v8 5/7] KVM: Force vmexit with virtual interrupt delivery Yang Zhang
2013-04-08 14:17 ` [PATCH v8 6/7] KVM: Let ioapic know the irq line status Yang Zhang
2013-04-08 14:17 ` [PATCH v8 7/7] KVM: Use eoi to track RTC interrupt delivery status Yang Zhang
2013-04-09 7:06 ` Gleb Natapov
2013-04-09 7:08 ` [PATCH v8 0/7] " Gleb Natapov
2013-04-09 16:27 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5164415E.9090101@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiantao.zhang@intel.com \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox