linux-kernel - Re: [PATCH RFC] remove jump_label optimization for perf sched events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1322144284.2921.59.camel@twins>
Date:	Thu, 24 Nov 2011 15:18:04 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Gleb Natapov <gleb@...hat.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu,
	Jason Baron <jbaron@...hat.com>, rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH RFC] remove jump_label optimization for perf sched events

On Thu, 2011-11-24 at 15:45 +0200, Gleb Natapov wrote:
> Yes, I contemplated this. I didn't realized that there are tons of
> jump_labels though.

Yeah, every tracepoint has one, that's by far the biggest user
currently.

> > But is there really any other user for this? All the trace bits are root
> > only iirc and kvm itself only sets them on the guest kernel I think for
> > paravirt, so that's not a problem.
> > 
> The problem I am trying to fix with this patch is not strictly
> virtualization related. 

No I know, its about user-trigerably jump_label conversions, but afaik
that's only perf. The others: tracepoints, and paravirt can't be toggled
by unpriv. users.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/