[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F3A00723E@ORSMSX114.amr.corp.intel.com>
Date: Sat, 12 Mar 2016 01:56:13 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Peter Zijlstra <peterz@...radead.org>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>
CC: "Shivappa, Vikas" <vikas.shivappa@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>, "hpa@...or.com" <hpa@...or.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...nel.org" <mingo@...nel.org>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"Anvin, H Peter" <h.peter.anvin@...el.com>
Subject: RE: [PATCH V6 0/6] Intel memory b/w monitoring support
Some tracing printk() show that we are calling update_sample() with totally bogus arguments.
There are a few good calls, then I see rmid=-380863112 evt_type=-30689 first=0
That turns into a wild vrmid, and we fault accessing mbm_current->prev_msr
-Tony
Powered by blists - more mailing lists