linux-kernel - Re: [PATCH] DCA: fix over-warning in ioat3_dca

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: <1399565636.122877.3.camel@djiang5-desk1.amr.corp.intel.com>
Date:	Thu, 8 May 2014 16:13:57 +0000
From:	"Jiang, Dave" <dave.jiang@...el.com>
To:	"Duyck, Alexander H" <alexander.h.duyck@...el.com>
CC:	"Williams, Dan J" <dan.j.williams@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Wu, Fengguang" <fengguang.wu@...el.com>,
	"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>,
	"Lin, Wei W" <wei.w.lin@...el.com>,
	"Chen, Jet" <jet.chen@...el.com>
Subject: Re: [PATCH] DCA: fix over-warning in ioat3_dca_init

On Thu, 2014-05-08 at 08:57 -0700, Alexander Duyck wrote:
> On 05/08/2014 08:28 AM, Jet Chen wrote:
> > I agree with your option that it is a real BIOS bug and it puts pressure on the BIOS guys to get this fixed. However, this warning message interferes with our kernel booting tests and kernel performance tests. We have to disable CONFIG_INTEL_IOATDMA in kconfig until this issue gets fixed. Before that, code of CONFIG_INTEL_IOATDMA will not be validated in our testing system :(.
> > Hope this issue could get fixed soon.
> > 
> > Thanks,
> > Jet
> > 
> 
> First I would recommend updating your BIOS.  If the updated BIOS also
> has the issue I would recommend taking this feedback to whoever provided
> the BIOS for your platform so that they can implement the fix.
> 
> If I am not mistaken some BIOSes have the option to disable DCA and/or
> IOATDMA.  You might want to check yours to see if you can just disable
> DCA on your platform until the issue can be resolved.

Disabling DCA is the preferred option. IOATDMA is functional without
DCA.

Jet,
What exactly are you attempting to test with IOATDMA? The only two
consumers of this DMA driver I know of are MDRAID and NTB. But support
for XOR/PQ ops on Xeon platforms have been removed due to various
reasons recently so it really is just NTB at the moment in the latest
kernels. 

> Thanks,
> 
> Alex
>