[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1912011205350.2748@hp-x360n>
Date: Sun, 1 Dec 2019 12:09:31 -0800 (PST)
From: "Kenneth R. Crudup" <kenny@...ix.com>
To: Ingo Molnar <mingo@...nel.org>
cc: Linus Torvalds <torvalds@...ux-foundation.org>, mceier@...il.com,
Davidlohr Bueso <dave@...olabs.net>,
kernel test robot <rong.a.chen@...el.com>,
Davidlohr Bueso <dbueso@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org
Subject: Re: [PATCH] x86/pat: Fix off-by-one bugs in interval tree search
> > uncached-minus @ 0xfed91000-0xfed92000
> > uncached-minus @ 0xff340000-0xff341000
> > write-combining @ 0x4000000000-0x4010000000
> > uncached-minus @ 0x4010000000-0x4010001000
On Sun, 1 Dec 2019, Ingo Molnar wrote:
> I believe this is the region that caused the problem, the 0x4010000000
> 'end' address of the WC region is the same as the 0x4010000000 'start'
> address of the UC- region that follows it.
> > write-combining @ 0x604a800000-0x604b000000
> > uncached-minus @ 0x604b100000-0x604b110000
> This WC region was probably unaffected by the bug.
For my education, and for completeness' sake, is there a proc/sys entry
that would tell me which device/module has reserved which PAT region?
-Kenny
--
Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Silicon Valley
Powered by blists - more mailing lists