[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190703102731.236024951@infradead.org>
Date: Wed, 03 Jul 2019 12:27:31 +0200
From: root <peterz@...radead.org>
To: tglx@...utronix.de, bp@...en8.de, mingo@...nel.org,
rostedt@...dmis.org, luto@...nel.org, torvalds@...ux-foundation.org
Cc: hpa@...or.com, dave.hansen@...ux.intel.com, jgross@...e.com,
linux-kernel@...r.kernel.org, zhe.he@...driver.com,
joel@...lfernandes.org, devel@...ukata.com, peterz@...radead.org
Subject: [PATCH 0/3] tracing vs CR2
Hi,
Eiichi-san re-discovered the bug earlier found by He Zhe which we've failed to
fix due to getting distracted by discussing how to untangle entry_64.S.
These 3 patches are basically a completion of the initial approach I suggested
in that earlier thread:
https://lkml.kernel.org/r/20190320221534.165ab87b@oasis.local.home
Yes, idtentry is a mess, and this doesn't help, but lets fix this now before
someone else trips over it.
This boots on x86_64 and builds on i386 so it must be perfect. No Xen testing
what so ever, because I wouldn't know where to begin.
Powered by blists - more mailing lists