From: Gleb Natapov <gleb@redhat.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH v9 7/7] KVM: Use eoi to track RTC interrupt delivery status
Date: Thu, 11 Apr 2013 10:55:54 +0300 [thread overview]
Message-ID: <20130411075554.GQ17919@redhat.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E09A07C38@SHSMSX101.ccr.corp.intel.com>
On Thu, Apr 11, 2013 at 07:54:01AM +0000, Zhang, Yang Z wrote:
> Gleb Natapov wrote on 2013-04-11:
> > On Wed, Apr 10, 2013 at 09:22:20PM +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.
> >>
> >> Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com>
> >> ---
> >> virt/kvm/ioapic.c | 39 ++++++++++++++++++++++++++++++++++++++-
> >> 1 files changed, 38 insertions(+), 1 deletions(-)
> >> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> >> index a49fcd5..aeac154 100644
> >> --- a/virt/kvm/ioapic.c
> >> +++ b/virt/kvm/ioapic.c
> >> @@ -147,6 +147,26 @@ static void kvm_rtc_eoi_tracking_restore_all(struct
> > kvm_ioapic *ioapic)
> >> __rtc_irq_eoi_tracking_restore_one(vcpu);
> >> }
> >> +static void rtc_irq_eoi(struct kvm_ioapic *ioapic, struct kvm_vcpu *vcpu)
> >> +{
> >> + if (test_and_clear_bit(vcpu->vcpu_id, ioapic->rtc_status.dest_map))
> >> + --ioapic->rtc_status.pending_eoi;
> >> +
> >> + WARN_ON(ioapic->rtc_status.pending_eoi < 0);
> >> +}
> >> +
> >> +static bool rtc_irq_check_coalesced(struct kvm_ioapic *ioapic, int irq,
> >> + bool line_status)
> >> +{
> >> + if (irq != RTC_GSI || !line_status)
> >> + return false;
> > Please move the check from rtc_irq_check_coalesced() to
> > kvm_ioapic_set_irq() like this: if (irq == RTC_GSI && line_status &&
> > rtc_irq_check_coalesced(ioapic, irq, line_status)) ....
> >
> > I was going to fix it myself while applying, but since there will be
> > new posted interrupt series anyway you can as well fix this one too.
> You mean fix it and send out it with posted interrupt series? Or just rebase the posted interrupt series on the top of this fix, but needn't to send out it?
>
Send both series. RTC one with this change.
--
Gleb.
next prev parent reply other threads:[~2013-04-11 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 13:22 [PATCH v9 0/7] Use eoi to track RTC interrupt delivery status Yang Zhang
2013-04-10 13:22 ` [PATCH v9 1/7] KVM: Add vcpu info to ioapic_update_eoi() Yang Zhang
2013-04-10 13:22 ` [PATCH v9 2/7] KVM: Introduce struct rtc_status Yang Zhang
2013-04-10 13:22 ` [PATCH v9 3/7] KVM: Return destination vcpu on interrupt injection Yang Zhang
2013-04-10 13:22 ` [PATCH v9 4/7] KVM: Add reset/restore rtc_status support Yang Zhang
2013-04-10 13:22 ` [PATCH v9 5/7] KVM: Force vmexit with virtual interrupt delivery Yang Zhang
2013-04-10 13:22 ` [PATCH v9 6/7] KVM: Let ioapic know the irq line status Yang Zhang
2013-04-10 13:22 ` [PATCH v9 7/7] KVM: Use eoi to track RTC interrupt delivery status Yang Zhang
2013-04-11 7:09 ` Gleb Natapov
2013-04-11 7:54 ` Zhang, Yang Z
2013-04-11 7:55 ` Gleb Natapov [this message]
2013-04-11 7:56 ` Zhang, Yang Z
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=20130411075554.GQ17919@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.