[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190704195555.580363209@infradead.org>
Date: Thu, 04 Jul 2019 21:55:55 +0200
From: Peter Zijlstra <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 v2 0/7] Tracing vs CR2 (and cleanups)
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
Since v1:
- idtentry_part 'cleanup'
- extra sanity check and comment
- read_cr2=1 for do_double_fault
- #BP vs IST cleanup
- IDTENTRYx() C wrapper
The thing boots on x86_64 with lockdep on, survives function-trace,
selftests/x86 and perf-test.
Powered by blists - more mailing lists