From: Avi Kivity <avi@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [RFC][PATCH 1/3] Introduce a workqueue to deliver PIT timer interrupts.
Date: Wed, 09 Jun 2010 13:55:15 +0300 [thread overview]
Message-ID: <4C0F7313.1000608@redhat.com> (raw)
In-Reply-To: <1276019703-18136-2-git-send-email-clalance@redhat.com>
On 06/08/2010 08:55 PM, Chris Lalancette wrote:
> We really want to "kvm_set_irq" during the hrtimer callback,
> but that is risky because that is during interrupt context.
> Instead, offload the work to a workqueue, which is a bit safer
> and should provide most of the same functionality.
>
>
>
>
> +static void pit_do_work(struct work_struct *work)
> +{
> + struct kvm_pit *pit = container_of(work, struct kvm_pit, expired);
> + struct kvm *kvm = pit->kvm;
> + struct kvm_vcpu *vcpu;
> + int i;
> + struct kvm_kpit_state *ps =&pit->pit_state;
> + int inject = 0;
> +
> + /* Try to inject pending interrupts when
> + * last one has been acked.
> + */
> + raw_spin_lock(&ps->inject_lock);
> + if (ps->irq_ack) {
> + ps->irq_ack = 0;
> + inject = 1;
> + }
> + raw_spin_unlock(&ps->inject_lock);
>
I don't think this needs to be a raw spinlock any longer (a nice side
effect).+
> +static enum hrtimer_restart pit_timer_fn(struct hrtimer *data)
> +{
> + struct kvm_timer *ktimer = container_of(data, struct kvm_timer, timer);
> + struct kvm_pit *pt = ktimer->kvm->arch.vpit;
> +
> + queue_work(pit_wq,&pt->expired);
> +
> + if (ktimer->t_ops->is_periodic(ktimer)) {
> + hrtimer_add_expires_ns(&ktimer->timer, ktimer->period);
>
spaces/tabs
> + return HRTIMER_RESTART;
> + }
> + else
> + return HRTIMER_NORESTART;
> +}
> +
>
Somewhere, you have to cancel a pending work struct. At least during
destruction, but perhaps also if the pit is configured not to generate
interrupts any more.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-09 10:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 17:55 [RFC][PATCH 0/3]: Fixes to IRQ routing Chris Lalancette
2010-06-08 17:55 ` [RFC][PATCH 1/3] Introduce a workqueue to deliver PIT timer interrupts Chris Lalancette
2010-06-09 2:36 ` Zachary Amsden
2010-06-09 13:23 ` Marcelo Tosatti
2010-06-09 14:16 ` Avi Kivity
2010-06-09 14:40 ` Marcelo Tosatti
2010-06-09 21:17 ` Zachary Amsden
2010-06-10 9:24 ` Avi Kivity
2010-06-10 19:17 ` Zachary Amsden
2010-06-10 16:18 ` Marcelo Tosatti
2010-06-09 10:55 ` Avi Kivity [this message]
2010-06-09 13:49 ` Marcelo Tosatti
2010-06-09 14:20 ` Avi Kivity
2010-06-08 17:55 ` [RFC][PATCH 2/3] Allow any LAPIC to accept PIC interrupts Chris Lalancette
2010-06-08 17:55 ` [RFC][PATCH 3/3] In DM_LOWEST, only deliver interrupts to vcpus with enabled LAPIC's Chris Lalancette
2010-06-09 11:01 ` Gleb Natapov
2010-06-09 11:08 ` Avi Kivity
2010-06-09 11:20 ` Gleb Natapov
2010-06-09 11:22 ` Avi Kivity
2010-06-09 11:02 ` [RFC][PATCH 0/3]: Fixes to IRQ routing Avi Kivity
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=4C0F7313.1000608@redhat.com \
--to=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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