linux-kernel - RE: [BUILD_FAILURE] 2.6.27-git2 - allyesconfig on powerpc selectsCONFIG_INTEL

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: <36D9DB17C6DE9E40B059440DB8D95F52066E2EAE@orsmsx418.amr.corp.intel.com>
Date:	Mon, 13 Oct 2008 11:05:43 -0700
From:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
To:	"Adrian Bunk" <bunk@...nel.org>,
	"Kamalesh Babulal" <kamalesh@...ux.vnet.ibm.com>,
	"Brice Goglin" <brice@...i.com>,
	"Jeff Garzik" <jgarzik@...hat.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
Cc:	<linux-kernel@...r.kernel.org>, <apw@...dowen.org>,
	<linuxppc-dev@...abs.org>, <sam@...nborg.org>,
	<e1000-devel@...ts.sourceforge.net>, <netdev@...r.kernel.org>,
	"Sosnowski, Maciej" <maciej.sosnowski@...el.com>
Subject: RE: [BUILD_FAILURE] 2.6.27-git2 - allyesconfig on powerpc selectsCONFIG_INTEL_IOATDMA=y

Adrian Bunk wrote:
> On Mon, Oct 13, 2008 at 03:45:59PM +0530, Kamalesh Babulal wrote:
>> Hi,
>> 
>>    2.6.27-git2 kernel build fails, while building the kernel with

from subject, on PPC.

>> allyesconfig option. The allyesconfig selects CONFIG_INTEL_IOATDMA=y
>> 
>> CC   drivers/dma/ioat_dca.o
>> drivers/dma/ioat_dca.c: In function âdca_enabled_in_biosâ:
>> drivers/dma/ioat_dca.c:81: error: implicit declaration of function
>> âcpuid_eaxâ drivers/dma/ioat_dca.c: In function
>> âsystem_has_dca_enabledâ: 
>> drivers/dma/ioat_dca.c:91: error: implicit declaration of function
>> âboot_cpu_hasâ drivers/dma/ioat_dca.c:91: error:
>> âX86_FEATURE_DCAâ undeclared (first use in this function)
>> drivers/dma/ioat_dca.c:91: error: (Each undeclared identifier is
>> reported only once drivers/dma/ioat_dca.c:91: error: for each
>> function it appears in.)  
>> drivers/dma/ioat_dca.c: In function âioat_dca_get_tagâ:
>> drivers/dma/ioat_dca.c:190: error: implicit declaration of function
>> âcpu_physical_idâ make[2]: *** [drivers/dma/ioat_dca.o] Error 1
>> make[1]: *** [drivers/dma] Error 2
>> make: *** [drivers] Error 2
>> ...
> 
> Thanks for the report, the MYRI10GE and IXGBE commits that introduced
> the select's are really broken.

it fixed an obvious bug with CONFIG_IXGBE=y and CONFIG_INTEL_IOATDMA=m, unfortunate that it is so difficult to use Kconfig for the uninitiated.
 
> For fixing it I need to know the intended semantics.
> 
> Brian, Jesse, is it OK to limit the drivers to m with
> CONFIG_INTEL_IOATDMA=m ?

why is the IOATDMA driver not depending on x86?  x86 hardware (32 and 64 bit) are the only machines that will have ioatdma support, since the ioatdma (and dca) device is only in Intel server chipsets since S5000 (aka S5000, S5400, S7400 and derivatives/followons)

What we want, is myri10ge and ixgbe drivers that can build whether or not CONFIG_INTEL_IOATDMA is enabled.  IF CONFIG_INTEL_IOATDMA *is* enabled (which it should not be on PPC) then there are several cases we want to work:
CONFIG_INTEL_IOATDMA=m  ---> CONFIG_IXGBE=[m|n]
CONFIG_INTEL_IOATDMA=y  ---> CONFIG_IXGBE=[m|y|n]
CONFIG_INTEL_IOATDMA=n  ---> CONFIG_IXGBE=[m|y|n]
CONFIG_INTEL_IOATDMA depends on X86

same for myri10ge I think.  I hope that cleared something up, we can seriously use some help from the experts to get Kconfig correct for this.
--
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/