All of lore.kernel.org
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: mm: remove the redundant code
Date: Tue, 19 Apr 2016 09:37:32 +0100	[thread overview]
Message-ID: <20160419083732.GA8482@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20160419071627.GA722@sha-win-210.asiapac.arm.com>

On Tue, Apr 19, 2016 at 03:16:29PM +0800, Huang Shijie wrote:
> On Mon, Apr 18, 2016 at 02:08:20PM +0100, Catalin Marinas wrote:
> > > @@ -212,10 +212,6 @@ static int __kprobes do_page_fault(unsigned long addr, unsigned int esr,
> > >     tsk = current;
> > >     mm  = tsk->mm;
> > >
> > > -   /* Enable interrupts if they were enabled in the parent context. */
> > > -   if (interrupts_enabled(regs))
> > > -           local_irq_enable();
> >
> > We indeed don't have to re-enable interrupts here as they have been
> > enabled by the calling code in entry.S. But have you run this with
> > CONFIG_TRACE_IRQFLAGS enabled? I don't think there is any issue, just a
> > sanity check.
> I tested this patch with the CONFIG_TRACE_IRQFLAGS/CONFIG_PROVE_LOCKING/CONFIG_DEBUG_LOCKDEP
> enabled, in my Juno board, it works fine.
> 
> Also I find that with this patch, if we want to check the lockdep stat with:
>     #cat /proc/lockdep_stats
> 
> The "redundant hardirq ons" become 0. Without this patch, the redundant
> hardirq ons" is a big number, such as 123444.

Thanks for checking.

Acked-by: Catalin Marinas <catalin.marinas@arm.com>

Will can pick this up for 4.7.

-- 
Catalin

      reply	other threads:[~2016-04-19  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18  1:49 [PATCH] arm64: mm: remove the redundant code Huang Shijie
2016-04-18 13:08 ` Catalin Marinas
2016-04-19  7:16   ` Huang Shijie
2016-04-19  8:37     ` Catalin Marinas [this message]

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=20160419083732.GA8482@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.