From: Thomas Gleixner <tglx@linutronix.de>
To: Leo Li <pku.leo@gmail.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Marc Zyngier <maz@misterjones.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: recommended use of request_any_context_irq()
Date: Thu, 22 Sep 2016 22:47:13 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1609222239500.5640@nanos> (raw)
In-Reply-To: <CADRPPNSZx126D9XMGTLPdjZXBg3o9BNwJ+djMaTVJyf4RY9Rqw@mail.gmail.com>
On Thu, 22 Sep 2016, Leo Li wrote:
> On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
> > There is strictly no reason to perform a blanket change of all the
> > drivers. What would be the reason to change them other than to cater for
> > a contrived use case that may never happen?
>
> Maybe we could do blanket change to drivers that meet certain
> criteria? At least we should improve the messaging when a driver
> cannot request interrupt due to nested threading.
Nested threading is a result of requesting an any context interrupt not
something which is there already.
> Right now, it might take quite some time for a developer unfamiliar with
> the threaded interrupt to figure out the problem.
Did you have issues with a driver which was not able to request an
interrupt? If yes, please explain in detail what the failure was and why
you think that this should be changed. If not, please explain which problem
you are trying to solve.
Thanks,
tglx
next prev parent reply other threads:[~2016-09-22 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 21:14 Leo Li
2016-09-22 8:10 ` Marc Zyngier
2016-09-22 9:29 ` Thomas Gleixner
2016-09-22 20:38 ` Leo Li
2016-09-22 20:47 ` Thomas Gleixner [this message]
2016-09-22 21:52 ` Leo Li
2016-09-22 22:03 ` Thomas Gleixner
2016-09-23 18:33 ` Leo Li
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.DEB.2.20.1609222239500.5640@nanos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=maz@misterjones.org \
--cc=pku.leo@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®