[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191008145423.GG14765@zn.tnic>
Date: Tue, 8 Oct 2019 16:54:24 +0200
From: Borislav Petkov <bp@...en8.de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, rostedt@...dmis.org,
mhiramat@...nel.org, bristot@...hat.com, jbaron@...mai.com,
torvalds@...ux-foundation.org, tglx@...utronix.de,
mingo@...nel.org, namit@...are.com, hpa@...or.com, luto@...nel.org,
ard.biesheuvel@...aro.org, jpoimboe@...hat.com
Subject: Re: [PATCH v3 1/6] x86/alternatives: Teach text_poke_bp() to emulate
instructions
On Tue, Oct 08, 2019 at 04:48:34PM +0200, Peter Zijlstra wrote:
> Can, but why? That's more lines for no raisin ;-)
Here's a raisin: I was looking at this and then all of a sudden went:
"W00t, why is this do_sync part of the loop at all? Do they belong
together? Nope."
If we're going to save on lines, we've lost long ago.
> Very first pass, we write INT3's everywhere.
Doh.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists