From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
gleb@kernel.org, mtosatti@redhat.com, alex.williamson@redhat.com,
jan.kiszka@siemens.com
Subject: Re: [PATCH v2 3/4] KVM: ioapic: extract body of kvm_ioapic_set_irq
Date: Fri, 21 Mar 2014 19:58:59 +0100 [thread overview]
Message-ID: <20140321185858.GA22118@potion.brq.redhat.com> (raw)
In-Reply-To: <1395394081-16252-4-git-send-email-pbonzini@redhat.com>
2014-03-21 10:28+0100, Paolo Bonzini:
> We will reuse it to process a nonzero IRR that is passed to KVM_SET_IRQCHIP.
>
> Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> v1->v2:
> more comments
> change argument name from level to irq_level
>
> virt/kvm/ioapic.c | 74 +++++++++++++++++++++++++++++++++++++------------------
> 1 file changed, 50 insertions(+), 24 deletions(-)
>
> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> index 25e16a6898ed..270f7fe73f39 100644
> --- a/virt/kvm/ioapic.c
> +++ b/virt/kvm/ioapic.c
> @@ -163,6 +163,55 @@ static bool rtc_irq_check_coalesced(struct kvm_ioapic *ioapic)
> return false;
> }
>
> +static int ioapic_set_irq(struct kvm_ioapic *ioapic, unsigned int irq,
> + int irq_level, bool line_status)
> +{
> + union kvm_ioapic_redirect_entry entry;
> + u32 mask = 1 << irq;
> + u32 old_irr;
> + int edge, ret;
> +
> + entry = ioapic->redirtbl[irq];
> + edge = (entry.fields.trig_mode == IOAPIC_EDGE_TRIG);
> +
> + if (!irq_level) {
> + ioapic->irr &= ~mask;
> + ret = 1;
> + goto out;
> + }
> +
> + /*
> + * Return 0 for coalesced interrupts; for edge-triggered interrupts,
> + * this only happens if a previous edge has not been delivered due
> + * do masking. For level interrupts, the remote_irr field tells
(^ to)
> + * us if the interrupt is waiting for an EOI.
How do we know we haven't delivered an edge-triggered interrupt when
ioapic_service() always clears this IRR bit?
> + *
> + * RTC is special: it is edge-triggered, but userspace likes to know
> + * if it has been already ack-ed via EOI because coalesced RTC
> + * interrupts lead to time drift in Windows guests. So we track
> + * EOI manually for the RTC interrupt.
> + */
The comment makes me think we should not be coalescing more, but we do.
> + if (irq == RTC_GSI && line_status &&
> + rtc_irq_check_coalesced(ioapic)) {
> + ret = 0;
> + goto out;
> + }
> +
> + old_irr = ioapic->irr;
> + ioapic->irr |= mask;
> + if ((edge && old_irr == ioapic->irr) ||
> + (!edge && entry.fields.remote_irr)) {
(Fun fact: GCC 4.8.2 doesn't optimize it as well as
edge ? old_irr == ioapic->irr : entry.fields.remote_irr)
> + ret = 0;
> + goto out;
> + }
> +
> + ret = ioapic_service(ioapic, irq, line_status);
> +
> +out:
> + trace_kvm_ioapic_set_irq(entry.bits, irq, ret == 0);
> + return ret;
> +}
> +
> static void update_handled_vectors(struct kvm_ioapic *ioapic)
> {
> DECLARE_BITMAP(handled_vectors, 256);
> @@ -308,38 +357,15 @@ static int ioapic_service(struct kvm_ioapic *ioapic, int irq, bool line_status)
> int kvm_ioapic_set_irq(struct kvm_ioapic *ioapic, int irq, int irq_source_id,
> int level, bool line_status)
> {
> - u32 old_irr;
> - u32 mask = 1 << irq;
> - union kvm_ioapic_redirect_entry entry;
> int ret, irq_level;
>
> BUG_ON(irq < 0 || irq >= IOAPIC_NUM_PINS);
>
> spin_lock(&ioapic->lock);
> - old_irr = ioapic->irr;
> irq_level = __kvm_irq_line_state(&ioapic->irq_states[irq],
> irq_source_id, level);
> - entry = ioapic->redirtbl[irq];
> - if (!irq_level) {
> - ioapic->irr &= ~mask;
> - ret = 1;
> - } else {
> - int edge = (entry.fields.trig_mode == IOAPIC_EDGE_TRIG);
> + ret = ioapic_set_irq(ioapic, irq, irq_level, line_status);
>
> - if (irq == RTC_GSI && line_status &&
> - rtc_irq_check_coalesced(ioapic)) {
> - ret = 0; /* coalesced */
> - goto out;
> - }
> - ioapic->irr |= mask;
> - if ((edge && old_irr != ioapic->irr) ||
> - (!edge && !entry.fields.remote_irr))
> - ret = ioapic_service(ioapic, irq, line_status);
> - else
> - ret = 0; /* report coalesced interrupt */
> - }
> -out:
> - trace_kvm_ioapic_set_irq(entry.bits, irq, ret == 0);
> spin_unlock(&ioapic->lock);
>
> return ret;
> --
> 1.8.3.1
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-21 19:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 9:27 [PATCH v2 0/4] KVM: cleanup ioapic and fix KVM_SET_IRQCHIP with irr != 0 Paolo Bonzini
2014-03-21 9:27 ` [PATCH v2 1/4] KVM: ioapic: merge ioapic_deliver into ioapic_service Paolo Bonzini
2014-03-21 17:39 ` Eduardo Habkost
2014-03-21 9:27 ` [PATCH v2 2/4] KVM: ioapic: clear IRR for edge-triggered interrupts at delivery Paolo Bonzini
2014-03-21 18:34 ` Eduardo Habkost
2014-03-22 7:48 ` Paolo Bonzini
2014-03-21 9:28 ` [PATCH v2 3/4] KVM: ioapic: extract body of kvm_ioapic_set_irq Paolo Bonzini
2014-03-21 18:58 ` Radim Krčmář [this message]
2014-03-23 8:44 ` Paolo Bonzini
2014-03-24 17:55 ` Radim Krčmář
2014-03-21 9:28 ` [PATCH v2 4/4] KVM: ioapic: reinject pending interrupts on KVM_SET_IRQCHIP Paolo Bonzini
2014-03-21 14:00 ` Alex Williamson
2014-03-24 17:58 ` Radim Krčmář
2014-03-24 18:14 ` Paolo Bonzini
2014-03-24 19:28 ` Radim Krčmář
2014-03-24 17:59 ` [PATCH v2 0/4] KVM: cleanup ioapic and fix KVM_SET_IRQCHIP with irr != 0 Radim Krčmář
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=20140321185858.GA22118@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=gleb@kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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