From: Torsten Duwe <duwe@lst.de>
To: Julien Thierry <julien.thierry@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: Re: [PATCH v6] arm64: implement ftrace with regs
Date: Thu, 17 Jan 2019 16:48:21 +0100 [thread overview]
Message-ID: <20190117154821.GC9094@lst.de> (raw)
In-Reply-To: <8eb70db4-92a2-95a2-075c-f26690aab3ed@arm.com>
On Wed, Jan 16, 2019 at 09:57:39AM +0000, Julien Thierry wrote:
>
> I wanted to test this patch (and try to benchmark having the "mov x9,
> x30" always present in function prelude vs having two nops), but I
> cannot get this patch to apply (despite having a version including both
> commits below).
>
> Could you provide a git branch from which I could try to rebase the
> patch? (Or a new version of the series)
It also applies with just a single, harmless fuzz 1 onto 5.0-rc2.
Does that help?
I'm currently over v7, with Mark's requests included and the mov patching
done only once at bootup...
Torsten
prev parent reply other threads:[~2019-01-17 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 14:10 [PATCH v6] arm64: implement ftrace with regs Torsten Duwe
2019-01-04 17:50 ` Mark Rutland
2019-01-04 18:06 ` Steven Rostedt
2019-01-04 22:41 ` Torsten Duwe
2019-01-05 11:05 ` Torsten Duwe
2019-01-05 20:00 ` Steven Rostedt
2019-01-07 11:19 ` Mark Rutland
2019-01-14 12:13 ` Balbir Singh
2019-01-14 12:26 ` Mark Rutland
2019-01-16 15:56 ` Julien Thierry
2019-01-16 18:01 ` Julien Thierry
2019-01-07 4:57 ` Amit Daniel Kachhap
2019-01-16 9:57 ` Julien Thierry
2019-01-16 10:08 ` Julien Thierry
2019-01-17 15:48 ` Torsten Duwe [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=20190117154821.GC9094@lst.de \
--to=duwe@lst.de \
--cc=amit.kachhap@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=jpoimboe@redhat.com \
--cc=julien.thierry@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
/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).