[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E6AF1AFDEA62A94A97508F458CBDD47F7A264595@SHSMSX101.ccr.corp.intel.com>
Date: Fri, 9 Aug 2019 07:07:32 +0000
From: "Zhuo, Qiuxu" <qiuxu.zhuo@...el.com>
To: Stephen Douthit <stephend@...icom-usa.com>,
"Luck, Tony" <tony.luck@...el.com>, Borislav Petkov <bp@...en8.de>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
James Morse <james.morse@....com>
CC: "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] EDAC, pnd2: Fix ioremap() size in dnv_rd_reg() from 64K
-> 32K
>
> BIOS has marked the 32K MCHBAR window as reserved, so when dnv_rd_reg()
> tries to ioremap() a 64KB region you get warnings like:
>
> resource sanity check: requesting [mem 0xfed10000-0xfed1ffff], which spans
> more than reserved [mem 0xfed10000-0xfed17fff] caller
> dnv_rd_reg+0xc8/0x240 [pnd2_edac] mapping multiple BARs
>
> ioremap() the correct size on Denverton platforms to get rid of those warnings.
I've several dmesg logs for loading the pnd2_edac driver on a Denverton server successfully. But the logs haven't got such warning.
-Qiuxu
Powered by blists - more mailing lists