[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 3 Mar 2018 21:25:45 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
Yang Bo <yangbo@...pin.com>, Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Laura Abbott <labbott@...hat.com>
Subject: Re: [PATCH -tip] x86: kprobes: Cleanup preempt disabling and
enabling
On Sat, 3 Mar 2018 10:58:23 +0100
Ingo Molnar <mingo@...nel.org> wrote:
>
> * Masami Hiramatsu <mhiramat@...nel.org> wrote:
>
> > +/*
> > + * Interrupts are disabled on entry as trap3 is an interrupt gate and they
> > + * remain disabled throughout this function.
> > + */
> > +int kprobe_int3_handler(struct pt_regs *regs)
> > +{
> > + struct kprobe_ctlblk *kcb;
> > + int ret;
> > +
> > + if (user_mode(regs))
> > + return 0;
> > +
> > + /*
> > + * We don't want to be preempted for the entire
> > + * duration of kprobe processing.
> > + */
> > + preempt_disable();
> > +
> > + kcb = get_kprobe_ctlblk();
> > + ret = kprobe_int3_dispatcher(regs, kcb);
> > +
> > + if (!kprobe_ready_for_singlestep(regs))
> > + preempt_enable_no_resched();
> > +
> > + return ret;
>
> What's the point of disabling preemption, if IRQs are disabled already?
>
> There's no preemption when IRQs are off...
Ahh, right! Whole the kprobe singlestepping, IRQs are off (kprobes drops
IF from regs->flags for single stepping) so we don't need to care about
preempt count anymore...
Thank you!
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists