From: Jan Kiszka <jan.kiszka@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel@vger.kernel.org, kvm <kvm@vger.kernel.org>,
Tom Lyon <pugs@cisco.com>,
Alex Williamson <alex.williamson@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v3 2/4] genirq: Inform handler about line sharing state
Date: Wed, 15 Dec 2010 00:00:26 +0100 [thread overview]
Message-ID: <4D07F70A.30209@web.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1012142147420.12146@localhost6.localdomain6>
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
Am 14.12.2010 21:54, Thomas Gleixner wrote:
> On Mon, 13 Dec 2010, Jan Kiszka wrote:
>> @@ -943,6 +950,9 @@ static struct irqaction *__free_irq(unsigned int irq, void *dev_id)
>> /* Make sure it's not being used on another CPU: */
>> synchronize_irq(irq);
>>
>> + if (single_handler)
>> + desc->irq_data.drv_status &= ~IRQS_SHARED;
>> +
>
> What's the reason to clear this flag outside of the desc->lock held
> region.
We need to synchronize the irq first before clearing the flag.
The problematic scenario behind this: An IRQ started in shared mode,
this the line was unmasked after the hardirq. Now we clear IRQS_SHARED
before calling into the threaded handler. And that handler may now think
that the line is still masked as IRQS_SHARED is set.
> I need this status for other purposes as well, where I
> definitely need serialization.
Well, two options: wrap all bit manipulations with desc->lock
acquisition/release or turn drv_status into an atomic. I don't know what
your plans with drv_status are, so...
>
>> + mutex_lock(®ister_lock);
>> +
>> + old_action = desc->action;
>> + if (old_action && (old_action->flags & IRQF_ADAPTIVE) &&
>> + !(desc->irq_data.drv_status & IRQS_SHARED)) {
>> + /*
>> + * Signal the old handler that is has to switch to shareable
>> + * handling mode. Disable the line to avoid any conflict with
>> + * a real IRQ.
>> + */
>> + disable_irq(irq);
>> + local_irq_disable();
>> +
>> + desc->irq_data.drv_status |= IRQS_SHARED | IRQS_MAKE_SHAREABLE;
>
> Unserialized access as well. Will think about it.
>
>> + old_action->handler(irq, old_action->dev_id);
>> + desc->irq_data.drv_status &= ~IRQS_MAKE_SHAREABLE;
>
> Thanks,
>
> tglx
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-12-14 23:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 22:59 [PATCH v3 0/4] KVM & genirq: Enable adaptive IRQ sharing for passed-through devices Jan Kiszka
2010-12-13 22:59 ` [PATCH v3 1/4] genirq: Introduce driver-readable IRQ status word Jan Kiszka
2010-12-14 20:47 ` Thomas Gleixner
2010-12-14 23:10 ` Jan Kiszka
2010-12-13 22:59 ` [PATCH v3 2/4] genirq: Inform handler about line sharing state Jan Kiszka
2010-12-14 20:54 ` Thomas Gleixner
2010-12-14 23:00 ` Jan Kiszka [this message]
2010-12-15 13:04 ` Thomas Gleixner
2010-12-15 14:18 ` Jan Kiszka
2010-12-15 14:49 ` Thomas Gleixner
2010-12-15 15:41 ` Thomas Gleixner
2010-12-15 15:49 ` Jan Kiszka
2010-12-15 16:02 ` Thomas Gleixner
2010-12-14 21:46 ` Thomas Gleixner
2010-12-14 23:01 ` Jan Kiszka
2010-12-15 8:05 ` Thomas Gleixner
2010-12-15 9:37 ` Jan Kiszka
2010-12-15 9:48 ` Thomas Gleixner
2010-12-16 13:13 ` Thomas Gleixner
2010-12-16 20:26 ` Jan Kiszka
2010-12-16 21:28 ` change of email address: pugs@cisco.com -> pugs@ieee.org Tom Lyon
2010-12-17 8:18 ` [PATCH v3 2/4] genirq: Inform handler about line sharing state Jan Kiszka
2010-12-17 10:23 ` Thomas Gleixner
2010-12-17 10:31 ` Jan Kiszka
2010-12-17 10:41 ` Thomas Gleixner
2010-12-17 10:48 ` Jan Kiszka
2010-12-17 15:25 ` Thomas Gleixner
2010-12-17 16:06 ` Jan Kiszka
2010-12-17 16:32 ` Thomas Gleixner
2010-12-18 18:11 ` Michael S. Tsirkin
2010-12-13 22:59 ` [PATCH v3 3/4] genirq: Add support for IRQF_COND_ONESHOT Jan Kiszka
2010-12-13 22:59 ` [PATCH v3 4/4] KVM: Allow host IRQ sharing for passed-through PCI 2.3 devices Jan Kiszka
2010-12-14 8:53 ` [PATCH v3 0/4] KVM & genirq: Enable adaptive IRQ sharing for passed-through devices Avi Kivity
2010-12-14 22:01 ` Thomas Gleixner
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=4D07F70A.30209@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pugs@cisco.com \
--cc=tglx@linutronix.de \
/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