lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <186376.4823.qm@web63604.mail.re1.yahoo.com>
Date:	Sat, 2 Jun 2007 13:39:21 -0700 (PDT)
From:	Tear <tarrqt@...oo.com>
To:	Len Brown <lenb@...nel.org>
Cc:	mingo@...hat.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] IO-APIC blacklist


--- Len Brown <lenb@...nel.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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ