From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: mingo@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: 2.6.10 - Misrouted IRQ recovery for review
Date: Sat, 1 Jan 2005 18:59:34 +0100 [thread overview]
Message-ID: <20050101175934.GB1345@elf.ucw.cz> (raw)
In-Reply-To: <1104249508.22366.101.camel@localhost.localdomain>
Hi!
> Ported to the new kernel/irq code.
Perhaps some Documentation/ patch would be nice?
I always thought manually polling interrupt handlers might be usefull,
and it indeed was very usefull on philips velo 1...
Pavel
> +static int __init irqfixup_setup(char *str)
> +{
> + irqfixup = 1;
> + printk(KERN_WARNING "Misrouted IRQ fixup support enabled.\n");
> + printk(KERN_WARNING "This may impact system performance.\n");
> + return 1;
> +}
> +
> +__setup("irqfixup", irqfixup_setup);
> +
> +static int __init irqpoll_setup(char *str)
> +{
> + irqfixup = 2;
> + printk(KERN_WARNING "Misrouted IRQ fixup and polling support enabled.\n");
> + printk(KERN_WARNING "This may significantly impact system performance.\n");
> + return 1;
> +}
> +
> +__setup("irqpoll", irqpoll_setup);
>
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-01-01 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 15:58 Alan Cox
2004-12-28 17:11 ` Arjan van de Ven
2004-12-28 16:37 ` Alan Cox
2004-12-28 17:28 ` Dmitry Torokhov
2004-12-28 18:25 ` David S. Miller
2004-12-28 18:50 ` Dmitry Torokhov
2004-12-28 18:53 ` David S. Miller
2004-12-28 19:21 ` Dmitry Torokhov
2004-12-28 19:26 ` David S. Miller
2004-12-29 13:57 ` Ingo Molnar
2005-01-01 17:59 ` Pavel Machek [this message]
2005-01-01 20:41 ` Bill Davidsen
2005-01-02 15:18 ` Alan Cox
2005-01-02 17:47 ` Bill Davidsen
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=20050101175934.GB1345@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®