[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230526013534.76e5b613@rorschach.local.home>
Date: Fri, 26 May 2023 01:35:34 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Nadav Amit <nadav.amit@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel@...ts.infradead.org,
LKML <linux-kernel@...r.kernel.org>, linux-ia64@...r.kernel.org,
linux-um@...ts.infradead.org,
Linux-Arch <linux-arch@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, Andy Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Borislav Petkov <bp@...en8.de>, X86 ML <x86@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v2 2/3] compiler: inline does not imply notrace
On Thu, 25 May 2023 22:17:33 -0700
Nadav Amit <nadav.amit@...il.com> wrote:
> > FYI, I have a patch queued (still needs to go through testing) that
> > already does this ;-)
> >
> > https://lore.kernel.org/all/20230502164102.1a51cdb4@gandalf.local.home/
>
> Ugh. If you cc’d me, I wouldn’t bother you during your vacation. :)
I'm currently passed the vacation part and now in Taiwan for work.
>
> I think you may like the first patch in my series to precede this patch
> though as some of the function I marked as “notrace" are currently “inline”.
>
> Let me know how you want to proceed, so I would know how to break this
> series.
Currently there's a nasty bug in v6.4-rc3 I'm fighting where I can't
proceed on anything until it's resolved. But I could also just pull
your first and third patch too. I'll let you know when I'm finished
debugging.
-- Steve
Powered by blists - more mailing lists