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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 2 Apr 2014 17:02:18 -0700
From:	"David E. Box" <david.e.box@...ux.intel.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] x86/platforms for v3.15

Hi Linus,

My apologies for not getting to address hpa's issues sooner. FWIW I simply
didn't want to force a dependancy on the mbi driver for those drivers that run
on both big core and soc systems, risking that the driver wouldn't run on big
core systems that don't have the mbi compiled in. Luckily we should be able to
make the mbi modular and simply default m and avoid this issue.

David Box

On Tue, Apr 01, 2014 at 10:23:30AM -0700, H. Peter Anvin wrote:
> Hi Linus,
> 
> This one is largely my fault, but it is not for not asking the questions.
> 
> This patch is part of the work of modularizing the IOSF drivers, because
> of course standard distros don't want to compile them in.  However, this
> results in odd problems when IOSF-aware drivers (some of which are
> present on non-IOSF hardware, as there are drivers that operate on both
> PCI and IOSF, some of which are still coming down the pipe toward mainline.)
> 
> It is these dual-mode drivers that make things a bit more complicated
> than it ought to be.
> 
> I have explicitly asked David to work on modularizing the IOSF core,
> even though it is small, exactly to avoid this mess.  However, that
> change didn't make it in time, and I guess I should just have said "no"
> at that point.
> 
> I did not want to not have an option to disable it for EXPERT
> configurations, because we also have people working very hard at shaving
> down the size of the x86 kernel so that Linux rather than "random RTOS
> of the month" can be used in deep embedded configurations.
> 
> On this issue:
> 
> >  (a) people don't know about, so asking people about it is f*cking
> > retarded to begin with
> 
> Well, that is why it is an EXPERT option.
> 
> +	bool "IOSF MBI support" if EXPERT
> 
> 	-hpa
--
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