From: Anton Blanchard <anton@samba•org>
To: Nicholas Piggin <npiggin@gmail•com>
Cc: benh@kernel•crashing.org, paulus@samba•org, mpe@ellerman•id.au,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] powerpc: Add POWER9 copy_page() loop
Date: Mon, 3 Apr 2017 10:54:34 +1000 [thread overview]
Message-ID: <20170403105434.60309d3e@kryten> (raw)
In-Reply-To: <20170321142139.3072b9b6@roar.ozlabs.ibm.com>
Hi Nick,
> > Good idea, I hadn't thought of embedding it all in a feature
> > section.
>
> It may not work currently because you get those ftr_alt_97 relocation
> errors with the "else" parts because relative branches to other code
> need to be direct and I think reachable from both places.
I thought about this a bit more. One potential issue will be
profiling - perf annotate will match the samples against the unpatched
code which could be very confusing.
Anton
next prev parent reply other threads:[~2017-04-03 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:40 [PATCH] powerpc: Add POWER9 copy_page() loop Anton Blanchard
2017-03-21 3:01 ` Nicholas Piggin
2017-03-21 4:01 ` Anton Blanchard
2017-03-21 4:21 ` Nicholas Piggin
2017-04-03 0:54 ` Anton Blanchard [this message]
2017-04-03 1:01 ` Benjamin Herrenschmidt
2018-01-27 10:06 ` Michael Ellerman
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=20170403105434.60309d3e@kryten \
--to=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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