linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Runtime patch udiv/sdiv instructions into __aeabi_{u}idiv()
Date: Mon, 4 Jan 2016 17:23:19 -0800	[thread overview]
Message-ID: <20160105012319.GC22188@codeaurora.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1512111842280.26920@knanqh.ubzr>

On 12/11, Nicolas Pitre wrote:
> On Fri, 11 Dec 2015, Arnd Bergmann wrote:
> 
> > On Friday 11 December 2015 12:22:20 Nicolas Pitre wrote:
> > > Subject: [PATCH] ARM: Runtime patch udiv/sdiv instructions into __aeabi_{u}idiv()
> > > 
> 
> Thanks.
> 
> > Before you put it in the patch tracker, I think it would be good to
> > give Stephen a chance to comment as well, since he did a lot of
> > work upfront and this obsoletes his original patch series.
> 
> Given he'll get back from vacation only after the new year, I'll put the 
> patch in the tracker now so it can go in before the next merge window.  
> 
> Stephen's series could still be relevant by extending what is done here, 
> and it requires what this patch is doing anyway for those call sites 
> that can't be substituted by a div instruction (like conditional 
> branches, tail call optimizations, etc.)
> 

I'm back from vacation now. Where have we left off on this topic?

I can update the patches to be based on this patch here and
handle the conditional branches and tail call optimization cases
by adding some safety checks like we have for the ftrace branch
patching. But I'd rather not do that work unless we all agree
that it's worthwhile pursuing it.

Is there still any concern about the benefit of patching each
call site vs. patching the functions? The micro benchmark seems
to show some theoretical improvement on cortex-a7 and I can run
it on Scorpion and Krait processors to look for any potential
benefits there, but I'm not sure of any good kernel benchmark for
this. If it will be rejected due to complexity vs. benefit
arguments I'd rather work on something else.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2016-01-05  1:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  6:26 [PATCH] ARM: Runtime patch udiv/sdiv instructions into __aeabi_{u}idiv() Nicolas Pitre
2015-12-11  9:24 ` Arnd Bergmann
2015-12-11 17:10   ` Nicolas Pitre
2015-12-11 17:22     ` Nicolas Pitre
2015-12-11 22:26       ` Arnd Bergmann
2015-12-11 23:57         ` Nicolas Pitre
2016-01-05  1:23           ` Stephen Boyd [this message]
2016-01-05  1:42             ` Nicolas Pitre
2016-01-08  2:44               ` Stephen Boyd
2016-01-12 19:09                 ` Nicolas Pitre
2015-12-11 21:50     ` Arnd Bergmann
2015-12-11 22:00       ` Nicolas Pitre
2015-12-11 22:48         ` Arnd Bergmann
2015-12-11 22:34       ` Russell King - ARM Linux
2015-12-11 22:51         ` Arnd Bergmann
2015-12-12  0:01           ` Nicolas Pitre
2015-12-12  0:04             ` Arnd Bergmann
2015-12-12  1:17               ` Nicolas Pitre
2015-12-12 20:41                 ` Arnd Bergmann

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=20160105012319.GC22188@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).