mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	mathieu.desnoyers@polymtl.ca, hpa@zytor.com, tglx@linutronix.de,
	andi@firstfloor.org, roland@redhat.com, rth@redhat.com,
	mhiramat@redhat.com, fweisbec@gmail.com
Subject: Re: [PATCH 3/5] jump label: x86 support
Date: Mon, 22 Mar 2010 12:40:25 -0400	[thread overview]
Message-ID: <1269276025.2957.5.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <5492858ead53ab5c67d11acc620001abe8d36bcb.1269272444.git.jbaron@redhat.com>

On Mon, 2010-03-22 at 12:07 -0400, Jason Baron wrote:
> add x86 support for jump label. I'm keeping this patch separate so its clear to
> arch maintainers what was required for x86 support this new feature. hopefully,
> it wouldn't be too painful for other arches.
> 
> Signed-off-by: Jason Baron <jbaron@redhat.com>


> +#ifdef __HAVE_ARCH_JUMP_LABEL
> +
> +# ifdef CONFIG_X86_64
> +#  define JUMP_LABEL_NOP P6_NOP5
> +# else
> +#  define JUMP_LABEL_NOP ".byte 0xe9 \n\t .long 0\n\t"
> +# endif

Are you sure P6_NOP5 can't happen on non 64bit? Just because it is not
configured does not mean that the CPU can not handle it. Look at the
code I did in arch/x86/kernel/ftrace.c to determine what nop to use.
Maybe we can make that generic and have at boot up, the kernel determine
a proper 5byte nop.

> +
> +# 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)
> +
> +# endif
> +
> +#endif
> diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
> index 4c58352..7cd3bf4 100644
> --- a/arch/x86/kernel/Makefile
> +++ b/arch/x86/kernel/Makefile
> @@ -32,7 +32,7 @@ GCOV_PROFILE_paravirt.o		:= n
>  obj-y			:= process_$(BITS).o signal.o entry_$(BITS).o
>  obj-y			+= traps.o irq.o irq_$(BITS).o dumpstack_$(BITS).o
>  obj-y			+= time.o ioport.o ldt.o dumpstack.o
> -obj-y			+= setup.o x86_init.o i8259.o irqinit.o
> +obj-y			+= setup.o x86_init.o i8259.o irqinit.o jump_label.o
>  obj-$(CONFIG_X86_VISWS)	+= visws_quirks.o
>  obj-$(CONFIG_X86_32)	+= probe_roms_32.o
>  obj-$(CONFIG_X86_32)	+= sys_i386_32.o i386_ksyms_32.o
> diff --git a/arch/x86/kernel/jump_label.c b/arch/x86/kernel/jump_label.c
> new file mode 100644
> index 0000000..7fc4f84
> --- /dev/null
> +++ b/arch/x86/kernel/jump_label.c
> @@ -0,0 +1,53 @@
> +/*
> + * jump label x86 support
> + *
> + * Copyright (C) 2009 Jason Baron <jbaron@redhat.com>
> + *
> + */
> +#include <linux/jump_label.h>
> +#include <linux/memory.h>
> +#include <linux/uaccess.h>
> +#include <linux/module.h>
> +#include <linux/list.h>
> +#include <linux/jhash.h>
> +#include <linux/cpu.h>
> +#include <asm/kprobes.h>
> +
> +#ifdef __HAVE_ARCH_JUMP_LABEL
> +
> +union jump_code_union {
> +	char code[RELATIVEJUMP_SIZE];
> +	struct {
> +		char jump;
> +		int offset;
> +	} __attribute__((packed));
> +};
> +
> +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 + RELATIVEJUMP_SIZE);
> +	} else {
> +#ifdef CONFIG_X86_64
> +		/* opcode for P6_NOP5 */
> +		code.code[0] = 0x0f;
> +		code.code[1] = 0x1f;
> +		code.code[2] = 0x44;
> +		code.code[3] = 0x00;
> +		code.code[4] = 0x00;
> +#else
> +		code.jump = 0xe9;
> +		code.offset = 0;
> +#endif

Same here, and this should also just use the JUMP_LABEL_NOP insead of
spelling it out as it does here. memcpy should work.

-- Steve


> +	}
> +	get_online_cpus();
> +	mutex_lock(&text_mutex);
> +	text_poke_smp((void *)entry->code, &code, RELATIVEJUMP_SIZE);
> +	mutex_unlock(&text_mutex);
> +	put_online_cpus();
> +}
> +
> +#endif



  reply	other threads:[~2010-03-22 16:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 16:07 [PATCH 0/5] jump label v5 Jason Baron
2010-03-22 16:07 ` [PATCH 1/5] jump label: notifier atomic call chain notrace Jason Baron
2010-03-22 17:55   ` Masami Hiramatsu
2010-03-22 16:07 ` [PATCH 2/5] jump label: base patch Jason Baron
2010-03-22 20:04   ` Steven Rostedt
2010-03-22 21:01   ` Avi Kivity
2010-03-26 21:30   ` Masami Hiramatsu
2010-03-22 16:07 ` [PATCH 3/5] jump label: x86 support Jason Baron
2010-03-22 16:40   ` Steven Rostedt [this message]
2010-03-22 20:40     ` Jason Baron
2010-03-22 16:07 ` [PATCH 4/5] jump label: tracepoint support Jason Baron
2010-03-22 16:43   ` Steven Rostedt
2010-03-22 20:44     ` Jason Baron
2010-03-22 16:07 ` [PATCH 5/5] jump label: add module support Jason Baron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1269276025.2957.5.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=andi@firstfloor.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mhiramat@redhat.com \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=rth@redhat.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®