All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Anton Arapov <anton@redhat.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Rabin Vincent <rabin@rab.in>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] uprobes/x86: Cleanup the single-stepping code
Date: Fri, 2 Nov 2012 18:21:13 +0530	[thread overview]
Message-ID: <20121102125113.GG11125@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121028173931.GA14652@redhat.com>

* Oleg Nesterov <oleg@redhat.com> [2012-10-28 18:39:31]:

> No functional changes.
> 
> Now that default arch_uprobe_enable/disable_step() helpers do nothing,
> x86 has no reason to reimplement them. Change arch_uprobe_*_xol() hooks
> to do the necessary work and remove the x86-specific hooks.
> 
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>


Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>

> ---
>  arch/x86/kernel/uprobes.c |   54 +++++++++++++++-----------------------------
>  1 files changed, 19 insertions(+), 35 deletions(-)
> 
> diff --git a/arch/x86/kernel/uprobes.c b/arch/x86/kernel/uprobes.c
> index aafa555..c71025b 100644
> --- a/arch/x86/kernel/uprobes.c
> +++ b/arch/x86/kernel/uprobes.c
> @@ -478,6 +478,11 @@ int arch_uprobe_pre_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
>  	regs->ip = current->utask->xol_vaddr;
>  	pre_xol_rip_insn(auprobe, regs, autask);
> 
> +	autask->saved_tf = !!(regs->flags & X86_EFLAGS_TF);
> +	regs->flags |= X86_EFLAGS_TF;
> +	if (test_tsk_thread_flag(current, TIF_BLOCKSTEP))
> +		set_task_blockstep(current, false);
> +
>  	return 0;
>  }
> 
> @@ -603,6 +608,16 @@ int arch_uprobe_post_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
>  	if (auprobe->fixups & UPROBE_FIX_CALL)
>  		result = adjust_ret_addr(regs->sp, correction);
> 
> +	/*
> +	 * arch_uprobe_pre_xol() doesn't save the state of TIF_BLOCKSTEP
> +	 * so we can get an extra SIGTRAP if we do not clear TF. We need
> +	 * to examine the opcode to make it right.
> +	 */
> +	if (utask->autask.saved_tf)
> +		send_sig(SIGTRAP, current, 0);
> +	else if (!(auprobe->fixups & UPROBE_FIX_SETF))
> +		regs->flags &= ~X86_EFLAGS_TF;
> +
>  	return result;
>  }
> 
> @@ -647,6 +662,10 @@ void arch_uprobe_abort_xol(struct arch_uprobe *auprobe, struct pt_regs *regs)
>  	current->thread.trap_nr = utask->autask.saved_trap_nr;
>  	handle_riprel_post_xol(auprobe, regs, NULL);
>  	instruction_pointer_set(regs, utask->vaddr);
> +
> +	/* clear TF if it was set by us in arch_uprobe_pre_xol() */
> +	if (!utask->autask.saved_tf)
> +		regs->flags &= ~X86_EFLAGS_TF;
>  }
> 
>  /*
> @@ -676,38 +695,3 @@ bool arch_uprobe_skip_sstep(struct arch_uprobe *auprobe, struct pt_regs *regs)
>  		send_sig(SIGTRAP, current, 0);
>  	return ret;
>  }
> -
> -void arch_uprobe_enable_step(struct arch_uprobe *auprobe)
> -{
> -	struct task_struct *task = current;
> -	struct arch_uprobe_task	*autask	= &task->utask->autask;
> -	struct pt_regs *regs = task_pt_regs(task);
> -
> -	autask->saved_tf = !!(regs->flags & X86_EFLAGS_TF);
> -
> -	regs->flags |= X86_EFLAGS_TF;
> -	if (test_tsk_thread_flag(task, TIF_BLOCKSTEP))
> -		set_task_blockstep(task, false);
> -}
> -
> -void arch_uprobe_disable_step(struct arch_uprobe *auprobe)
> -{
> -	struct task_struct *task = current;
> -	struct arch_uprobe_task	*autask	= &task->utask->autask;
> -	bool trapped = (task->utask->state == UTASK_SSTEP_TRAPPED);
> -	struct pt_regs *regs = task_pt_regs(task);
> -	/*
> -	 * The state of TIF_BLOCKSTEP was not saved so we can get an extra
> -	 * SIGTRAP if we do not clear TF. We need to examine the opcode to
> -	 * make it right.
> -	 */
> -	if (unlikely(trapped)) {
> -		if (!autask->saved_tf)
> -			regs->flags &= ~X86_EFLAGS_TF;
> -	} else {
> -		if (autask->saved_tf)
> -			send_sig(SIGTRAP, task, 0);
> -		else if (!(auprobe->fixups & UPROBE_FIX_SETF))
> -			regs->flags &= ~X86_EFLAGS_TF;
> -	}
> -}
> -- 
> 1.5.5.1
> 


  reply	other threads:[~2012-11-02 12:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 17:39 [PATCH 0/4] uprobes: Kill arch_uprobe_enable/disable_step() hooks Oleg Nesterov
2012-10-28 17:39 ` [PATCH 1/4] uprobes/powerpc: Don't clear TIF_UPROBE in do_notify_resume() Oleg Nesterov
2012-10-29  5:27   ` Ananth N Mavinakayanahalli
2012-10-29  7:02     ` Srikar Dronamraju
2012-10-29 12:43     ` Oleg Nesterov
2012-10-29 13:28       ` Ananth N Mavinakayanahalli
2012-11-02  5:02       ` Srikar Dronamraju
2012-10-28 17:39 ` [PATCH 2/4] uprobes/powerpc: Do not use arch_uprobe_*_step() helpers Oleg Nesterov
2012-10-29  5:33   ` Ananth N Mavinakayanahalli
2012-11-02  5:03   ` Srikar Dronamraju
2012-10-28 17:39 ` [PATCH 3/4] uprobes/x86: Cleanup the single-stepping code Oleg Nesterov
2012-11-02 12:51   ` Srikar Dronamraju [this message]
2012-10-28 17:39 ` [PATCH 4/4] uprobes: Kill arch_uprobe_enable/disable_step() hooks Oleg Nesterov
2012-11-02 12:50   ` Srikar Dronamraju

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=20121102125113.GG11125@linux.vnet.ibm.com \
    --to=srikar@linux.vnet.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=anton@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rabin@rab.in \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.