linux-kernel - Re: [PATCH 03/13] jump label v9: 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: <1276172131.2077.205.camel@twins>
Date:	Thu, 10 Jun 2010 14:15:31 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jason Baron <jbaron@...hat.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu,
	mathieu.desnoyers@...ymtl.ca, hpa@...or.com, tglx@...utronix.de,
	rostedt@...dmis.org, andi@...stfloor.org, roland@...hat.com,
	rth@...hat.com, mhiramat@...hat.com, fweisbec@...il.com,
	avi@...hat.com, davem@...emloft.net, vgoyal@...hat.com,
	sam@...nborg.org
Subject: Re: [PATCH 03/13] jump label v9: x86 support

On Wed, 2010-06-09 at 17:39 -0400, Jason Baron wrote:
> +#define JUMP_LABEL(tag, label, cond)                           \
> +       do {                                                    \
> +               extern const char __jlstrtab_##tag[];           \
> +               asm goto("1:"                                   \
> +                       JUMP_LABEL_NOP                          \
> +                       ".pushsection __jump_table,  \"a\" \n\t"\
> +                       _ASM_PTR "1b, %l[" #label "], %c0 \n\t" \
> +                       ".popsection \n\t"                      \
> +                       : :  "i" (__jlstrtab_##tag) :  : label);\
> +       } while (0) 

Would it make sense to have that macro at least evaluate cond in some
way?
--
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/