linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lei <tom.leiming@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: Question on irq autoprobe
Date: Fri, 14 Sep 2012 10:02:16 +0800	[thread overview]
Message-ID: <CACVXFVOV9GfWxmbxDhKCOd0UWRPoORj5=dSiKdQrwnkf3cdNJw@mail.gmail.com> (raw)

Hi,

I see the below comments on probe_irq_off:

     *  BUGS: When used in a module (which arguably shouldn't happen)
     *  nothing prevents two IRQ probe callers from overlapping. The
     *  results of this are non-optimal.
     */

But from the code of probe_irq_on and probe_irq_off, the mutex of
probing_active is held during the whole irq probe procedure, so
I don't understand why the above said that 'nothing prevents two
IRQ probe callers from overlapping", and why isn't the mutex of
probing_active enough to avoid the overlapping?


Thanks,
-- 
Ming Lei

             reply	other threads:[~2012-09-14  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  2:02 Ming Lei [this message]
2012-09-27  4:08 ` Question on irq autoprobe Ming Lei

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='CACVXFVOV9GfWxmbxDhKCOd0UWRPoORj5=dSiKdQrwnkf3cdNJw@mail.gmail.com' \
    --to=tom.leiming@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).