From: Mark Rutland <mark.rutland@arm.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Will Deacon <will.deacon@arm.com>, Torsten Duwe <duwe@lst.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Julien Thierry <julien.thierry@arm.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@redhat.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 <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: Re: [PATCH v8 0/5] arm64: ftrace with regs
Date: Wed, 16 Oct 2019 18:58:42 +0100 [thread overview]
Message-ID: <20191016175841.GF46264@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1910161341520.13160@cbobk.fhfr.pm>
On Wed, Oct 16, 2019 at 01:42:59PM +0200, Jiri Kosina wrote:
> On Wed, 24 Jul 2019, Mark Rutland wrote:
>
> > > > > > So what's the status now? Besides debatable minor style
> > > > > > issues there were no more objections to v8. Would this
> > > > > > go through the ARM repo or via the ftrace repo?
> > > > >
> > > > > Sorry agains for the delay on this. I'm now back in the office and in
> > > > > front of a computer daily, so I can spend a bit more time on this.
> > > > >
> > > > > Regardless of anything else, I think that we should queue the first
> > > > > three patches now. I've poked the relevant maintainers for their acks so
> > > > > that those can be taken via the arm64 tree.
> > > > >
> > > > > I'm happy to do the trivial cleanups on the last couple of patches (e.g.
> > > > > s/lr/x30), and I'm actively looking at the API rework I requested.
> > > >
> > > > Ok, I've picked up patches 1-3 and I'll wait for you to spin updates to the
> > > > last two.
> > >
> > > Ok, I see that patches 1-3 are picked up and are already present in recent
> > > kernels.
> > >
> > > Is there any progress on remaining two patches?
> >
> > I'm afraid that I've been distracted on other fronts, so I haven't made
> > progress there.
> >
> > > Any help required?
> >
> > If you'd be happy to look at the cleanup I previously suggested for the
> > core, that would be great. When I last looked, it was simple to rework
> > things so that arch code doesn't have to define MCOUNT_ADDR, but I
> > hadn't figured out exactly how to split the core mcount assumptions from
> > the important state machine bits.
> >
> > I'll take another look and see if I can provide more detail. :)
>
> Hi Mark,
Hi Jiri,
> has any progress been made on any front? Feels like this got stuck a bit.
Sorry about this; I've been a bit distracted.
I've just done the core (non-arm64) bits today, and pushed that out:
https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=arm64/ftrace-with-regs
... I'll fold the remainging bits of patches 4 and 5 together tomorrow
atop of that.
Thanks,
Mark.
next prev parent reply other threads:[~2019-10-16 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190208150826.44EBC68DD2@newverein.lst.de>
[not found] ` <0f8d2e77-7e51-fba8-b179-102318d9ff84@arm.com>
[not found] ` <20190311114945.GA5625@lst.de>
[not found] ` <20190408153628.GL6139@lakrids.cambridge.arm.com>
[not found] ` <20190409175238.GE9255@fuggles.cambridge.arm.com>
2019-07-10 12:27 ` [PATCH v8 0/5] arm64: ftrace with regs Ruslan Bilovol
2019-07-24 16:15 ` Mark Rutland
2019-10-16 11:42 ` Jiri Kosina
2019-10-16 17:58 ` Mark Rutland [this message]
2019-10-18 17:41 ` Mark Rutland
2019-10-19 11:01 ` Torsten Duwe
2019-10-21 11:37 ` Mark Rutland
2019-10-21 13:20 ` Josh Poimboeuf
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=20191016175841.GF46264@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=amit.kachhap@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=duwe@lst.de \
--cc=jikos@kernel.org \
--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=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ruslan.bilovol@gmail.com \
--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).