linux-kernel - Re: [tip:perf/core] jump label: x86 support

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: <1287400675.29097.1550.camel@twins>
Date:	Mon, 18 Oct 2010 13:17:55 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	rostedt@...dmis.org, tglx@...utronix.de, jbaron@...hat.com,
	"mathieu.desnoyers" <mathieu.desnoyers@...icios.com>
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] jump label: x86 support

On Fri, 2010-09-24 at 09:01 +0000, tip-bot for Jason Baron wrote:
> +void arch_jump_label_transform(struct jump_entry *entry,
> +                              enum jump_label_type type)
> +{
> +       union jump_code_union code;
> +
> +       if (type == JUMP_LABEL_ENABLE) {
> +               code.jump = 0xe9;
> +               code.offset = entry->target -
> +                               (entry->code + JUMP_LABEL_NOP_SIZE);
> +       } else
> +               memcpy(&code, ideal_nop5, JUMP_LABEL_NOP_SIZE);
> +       get_online_cpus();
> +       mutex_lock(&text_mutex);
> +       text_poke_smp((void *)entry->code, &code, JUMP_LABEL_NOP_SIZE);
> +       mutex_unlock(&text_mutex);
> +       put_online_cpus();
> +} 

hpa, mathieu, what's the status of stop_machine less text poking?
Because the above basically means we have to disable architecture
jump_label support for -rt.
--
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/