From: Tear <tarrqt@yahoo.com>
To: Len Brown <lenb@kernel.org>
Cc: mingo@redhat.com, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] IO-APIC blacklist
Date: Sat, 2 Jun 2007 13:39:21 -0700 (PDT) [thread overview]
Message-ID: <186376.4823.qm@web63604.mail.re1.yahoo.com> (raw)
In-Reply-To: <200706021346.57067.lenb@kernel.org>
--- Len Brown <lenb@kernel.org> wrote:
> > +static int __init disable_blacklisted_ioapic(struct dmi_system_id *d)
> > +{
> > + printk(KERN_WARNING "%s detected... Disabling IO-APIC\n", d->ident);
> > + skip_ioapic_setup = 1;
> > + return(0);
> > +}
>
> Wouldn't this also disable the IOAPIC in the (working) ACPI+IOAPIC case?
Yes, it would. However, I wanted to make my addition
to the kernel generic so that other people with
problematic IO-APIC implementations can blacklist
their systems without checking whether ACPI is enabled
or not.
Thank you for your question/attention.
Regards,
- Tear
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
next prev parent reply other threads:[~2007-06-02 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 14:10 Tear
2007-06-02 14:39 ` Heikki Orsila
2007-06-02 16:39 ` Linus Torvalds
2007-06-02 20:32 ` Tear
2007-06-02 21:28 ` Linus Torvalds
2007-06-02 22:54 ` Andrew Morton
2007-06-02 23:13 ` Len Brown
2007-06-02 23:33 ` Len Brown
2007-06-02 23:53 ` Tear
2007-06-03 4:16 ` Len Brown
2007-06-03 10:24 ` Tear
2007-06-03 11:25 ` Tear
2007-06-02 17:46 ` Len Brown
2007-06-02 20:39 ` Tear [this message]
2007-06-02 20:55 ` Linus Torvalds
2007-06-02 23:48 ` Tear
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=186376.4823.qm@web63604.mail.re1.yahoo.com \
--to=tarrqt@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®