From: Greg KH <greg@kroah.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
Harald Arnesen <skogtun.linux@gmail.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Peter Hurley <peter@hurleysoftware.com>,
Thomas Meyer <thomas@m3y3r.de>,
Shawn Starr <shawn.starr@rogers.com>,
USB list <linux-usb@vger.kernel.org>,
linux-acpi@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>,
Imre Deak <imre.deak@intel.com>,
Daniel Kurtz <djkurtz@chromium.org>,
dri-devel@lists.freedesktop.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Subject: Re: [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo))
Date: Wed, 20 Mar 2013 16:37:23 -0700 [thread overview]
Message-ID: <20130320233723.GA4156@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1303210018430.16237@pobox.suse.cz>
On Thu, Mar 21, 2013 at 12:21:21AM +0100, Jiri Kosina wrote:
> On Wed, 20 Mar 2013, Alan Stern wrote:
>
> > > Ok, so how about this?
> > > Daniel, is it enough to make the problem appear on your system (by
> > > building this into the kernel and booting with dummy-irq.irq=16)?
> > >
> > > Thanks.
> > >
> > > From: Jiri Kosina <jkosina@suse.cz>
> > > Subject: [PATCH] dummy-irq: introduce a dummy IRQ handler driver
> > >
> > > This module accepts a single 'irq' parameter, which it should register for.
> > >
> > > Its sole purpose is to help with debugging of IRQ sharing problems, by
> > > force-enabling IRQ that would otherwise be disabled.
> > >
> > > Suggested-by: Alan Stern <stern@rowland.harvard.edu>
> > > Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> >
> > This is just what I was thinking of. Three extremely minor
> > suggestions...
>
> Thanks Alan. Updated version below.
>
> Greg, willing to merge this simple debugging facility?
Yes, I'll take it, give me a few days to catch up with my pending queue,
don't worry, it's not lost.
greg k-h
next prev parent reply other threads:[~2013-03-20 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 15:12 gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses))) Daniel Vetter
2013-03-19 15:38 ` gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses Alan Stern
2013-03-19 16:54 ` Daniel Vetter
2013-03-19 18:18 ` gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo Alan Stern
2013-03-20 16:29 ` Jiri Kosina
2013-03-20 17:23 ` Alan Stern
2013-03-20 23:21 ` [PATCH] dummy-irq: introduce a dummy IRQ handler driver (was Re: gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt respo)) Jiri Kosina
2013-03-20 23:37 ` Greg KH [this message]
2013-03-21 14:45 ` Daniel Vetter
2013-03-31 19:55 ` Jiri Kosina
2013-04-01 18:30 ` Daniel Vetter
2013-03-19 19:14 ` gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses Yinghai Lu
2013-03-20 23:14 ` Jiri Kosina
2013-03-24 19:44 ` gm45 intel gfx can generate non-MSI irq# in MSI mode (was Re: [PATCH] drm/i915: stop using GMBUS IRQs on Gen4 chips (was Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses))) Shawn Starr
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=20130320233723.GA4156@kroah.com \
--to=greg@kroah.com \
--cc=a.miskiewicz@gmail.com \
--cc=bhelgaas@google.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hpa@zytor.com \
--cc=imre.deak@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=rjw@sisk.pl \
--cc=shawn.starr@rogers.com \
--cc=skogtun.linux@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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).