3 May
2019
3 May
'19
4:32 p.m.
On Fri, May 03, 2019 at 09:20:55AM -0700, Andy Lutomirski wrote:
On May 3, 2019, at 6:22 AM, Steven Rostedt rostedt@goodmis.org wrote:
On Fri, 3 May 2019 11:29:59 +0200 Peter Zijlstra peterz@infradead.org wrote:
OMG, WTF, ARGH... That code is fsck'ing horrible. I'd almost argue to always do the INT3 thing, just to avoid games like that.
So here’s a somewhat nutty suggestion: how about we tweak the 32-bit entry code to emulate the sane 64-bit frame, not just for int3 but always?
Basically what I wrote above, right? I'd be fine with that... Linus?