From: Alan Stern <stern@rowland.harvard.edu> To: Jiri Kosina <jkosina@suse.cz> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Chris Wilson <chris@chris-wilson.co.uk>, Greg KH <greg@kroah.com>, 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: 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 13:23:13 -0400 (EDT) [thread overview] Message-ID: <Pine.LNX.4.44L0.1303201319190.1208-100000@iolanthe.rowland.org> (raw) In-Reply-To: <alpine.LNX.2.00.1303201728070.17295@pobox.suse.cz> On Wed, 20 Mar 2013, Jiri Kosina wrote: > > I don't know of any way. In fact, I have been thinking of writing a > > test driver module, with a module parameter telling it which IRQ number > > to register for. It seems like the sort of thing that would be useful > > to have, from time to time. > > 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... > +static irqreturn_t dummy_interrupt(int irq, void *dev_id) > +{ > + static int count = 0; > + > + if (count == 0) { > + printk("dummy-irq: interrupt occured on IRQ %d\n", irq); You probably should put a severity level here. KERN_INFO? > + count++; > + } > + > + return IRQ_NONE; > +} > + > +static int __init dummy_irq_init(void) > +{ > + if (request_irq(irq, &dummy_interrupt, IRQF_SHARED, "dummy_irq", &irq)) { > + printk(KERN_ERR "dummy-irq: cannot register IRQ %d\n", irq); > + return -EIO; > + } > + printk(KERN_INFO "dummy-irq: registered for IRQ %d\n", irq); > + return 0; > +} > + > +static void __exit dummy_irq_exit(void) > +{ > + printk(KERN_INFO "dummy-irq unloaded\n"); > + free_irq(irq, &irq); > + return; A return statement isn't needed here. > +} > + > +module_init(dummy_irq_init); > +module_exit(dummy_irq_exit); > + > +MODULE_LICENSE("GPL"); > +MODULE_AUTHOR("Jiri Kosina"); > +module_param_named(irq, irq, uint, 0444); module_param is good enough when the parameter's name is the same as the variable's name. > +MODULE_PARM_DESC(irq, "The IRQ to register for"); Alan Stern
WARNING: multiple messages have this Message-ID (diff)
From: Alan Stern <stern@rowland.harvard.edu> To: Jiri Kosina <jkosina@suse.cz> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Chris Wilson <chris@chris-wilson.co.uk>, Greg KH <greg@kroah.com>, 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: 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 13:23:13 -0400 (EDT) [thread overview] Message-ID: <Pine.LNX.4.44L0.1303201319190.1208-100000@iolanthe.rowland.org> (raw) In-Reply-To: <alpine.LNX.2.00.1303201728070.17295@pobox.suse.cz> On Wed, 20 Mar 2013, Jiri Kosina wrote: > > I don't know of any way. In fact, I have been thinking of writing a > > test driver module, with a module parameter telling it which IRQ number > > to register for. It seems like the sort of thing that would be useful > > to have, from time to time. > > 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... > +static irqreturn_t dummy_interrupt(int irq, void *dev_id) > +{ > + static int count = 0; > + > + if (count == 0) { > + printk("dummy-irq: interrupt occured on IRQ %d\n", irq); You probably should put a severity level here. KERN_INFO? > + count++; > + } > + > + return IRQ_NONE; > +} > + > +static int __init dummy_irq_init(void) > +{ > + if (request_irq(irq, &dummy_interrupt, IRQF_SHARED, "dummy_irq", &irq)) { > + printk(KERN_ERR "dummy-irq: cannot register IRQ %d\n", irq); > + return -EIO; > + } > + printk(KERN_INFO "dummy-irq: registered for IRQ %d\n", irq); > + return 0; > +} > + > +static void __exit dummy_irq_exit(void) > +{ > + printk(KERN_INFO "dummy-irq unloaded\n"); > + free_irq(irq, &irq); > + return; A return statement isn't needed here. > +} > + > +module_init(dummy_irq_init); > +module_exit(dummy_irq_exit); > + > +MODULE_LICENSE("GPL"); > +MODULE_AUTHOR("Jiri Kosina"); > +module_param_named(irq, irq, uint, 0444); module_param is good enough when the parameter's name is the same as the variable's name. > +MODULE_PARM_DESC(irq, "The IRQ to register for"); Alan Stern
next prev parent reply other threads:[~2013-03-20 17:23 UTC|newest] Thread overview: 22+ 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 15:38 ` 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-19 18:18 ` Alan Stern 2013-03-20 16:29 ` Jiri Kosina 2013-03-20 17:23 ` Alan Stern [this message] 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 [not found] ` <alpine.LNX.2.00.1303210018430.16237-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org> 2013-03-20 23:37 ` Greg KH 2013-03-20 23:37 ` Greg KH 2013-03-21 14:45 ` Daniel Vetter 2013-03-21 14:45 ` Daniel Vetter 2013-03-31 19:55 ` Jiri Kosina [not found] ` <alpine.LNX.2.00.1303312153520.22069-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org> 2013-04-01 18:30 ` Daniel Vetter 2013-04-01 18:30 ` Daniel Vetter [not found] ` <CAKMK7uGtLcuSsoumAgdB7ri+fR5ReNYcZELbqDcSueXVsewppg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 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-19 19:14 ` Yinghai Lu 2013-03-20 23:14 ` Jiri Kosina 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=Pine.LNX.4.44L0.1303201319190.1208-100000@iolanthe.rowland.org \ --to=stern@rowland.harvard.edu \ --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=greg@kroah.com \ --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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.