From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andreas Fenkart <andreas.fenkart@streamunlimited.com>,
zonque@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: use irq_mask as fallback for irq_disable.
Date: Tue, 23 Apr 2013 14:46:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1304231445140.21884@ionos> (raw)
In-Reply-To: <20130422162409.e66b1e6ac3111bd3995c5fd6@linux-foundation.org>
On Mon, 22 Apr 2013, Andrew Morton wrote:
> On Fri, 19 Apr 2013 15:41:02 +0200 Andreas Fenkart <andreas.fenkart@streamunlimited.com> wrote:
>
> > This is in line with irq_enable that uses the same fallback.
> > When masked, interrupts are still latched into the status register
> > so when unmasked there is an interrupt straight away.
> >
> > ...
> >
> > --- a/kernel/irq/chip.c
> > +++ b/kernel/irq/chip.c
> > @@ -216,10 +216,11 @@ void irq_enable(struct irq_desc *desc)
> > void irq_disable(struct irq_desc *desc)
> > {
> > irq_state_set_disabled(desc);
> > - if (desc->irq_data.chip->irq_disable) {
> > + if (desc->irq_data.chip->irq_disable)
> > desc->irq_data.chip->irq_disable(&desc->irq_data);
> > - irq_state_set_masked(desc);
> > - }
> > + else
> > + desc->irq_data.chip->irq_mask(&desc->irq_data);
> > + irq_state_set_masked(desc);
> > }
> >
> > void irq_percpu_enable(struct irq_desc *desc, unsigned int cpu)
>
> Well I hope Thomas knows what this patch does, because I sure don't.
I know what it does, but the changelog is completely useless.
> Does it fix a bug? Does it add a bug? Does it have any
> runtime-observable effects at all? If so, what are they?
It fixes a state inconsistency. Have to think about observable
effects.
Thanks
tglx
prev parent reply other threads:[~2013-04-23 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 13:41 Andreas Fenkart
2013-04-22 23:24 ` Andrew Morton
2013-04-23 12:46 ` Thomas Gleixner [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=alpine.LFD.2.02.1304231445140.21884@ionos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=andreas.fenkart@streamunlimited.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zonque@gmail.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
all inboxes | Powered by JetHome®