[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAhV-H5y8Tckih4jd3C8Q-M6OZiw2szCYuxLQfBXehpWSvrstA@mail.gmail.com>
Date: Wed, 20 Aug 2025 11:03:05 +0800
From: Huacai Chen <chenhuacai@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Bibo Mao <maobibo@...ngson.cn>, LKML <linux-kernel@...r.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@...r.kernel.org>, kvm@...r.kernel.org,
loongarch@...ts.linux.dev, Tianrui Zhao <zhaotianrui@...ngson.cn>,
Paolo Bonzini <pbonzini@...hat.com>, Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Subject: Re: [PATCH] LoongArch: KVM: Move kvm_iocsr tracepoint out of generic code
On Wed, Aug 20, 2025 at 8:27 AM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Thu, 24 Jul 2025 19:56:42 +0800
> Huacai Chen <chenhuacai@...nel.org> wrote:
>
> > On Thu, Jul 24, 2025 at 9:51 AM Bibo Mao <maobibo@...ngson.cn> wrote:
> > >
> > >
> > >
> > > On 2025/7/24 上午9:46, Steven Rostedt wrote:
> > > > On Thu, 24 Jul 2025 09:39:40 +0800
> > > > Bibo Mao <maobibo@...ngson.cn> wrote:
> > > >
> > > >>> #define kvm_fpu_load_symbol \
> > > >>> {0, "unload"}, \
> > > >>> {1, "load"}
> > > >>>
> > > >> Reviewed-by: Bibo Mao <maobibo@...ngson.cn>
> > > >
> > > > Thanks,
> > > >
> > > > Should this go through the loongarch tree or should I take it?
> > > Huacai,
> > >
> > > What is your point about this?
> > I will take it, thanks.
> >
> > Huacai
>
> Did this fall through the cracks?
I don't know what this means, but I think you are pinging.
This patch appears after I sent the KVM PR for 6.17, and it isn't a
bugfix, so it will go to 6.18.
Huacai
>
> -- Steve
Powered by blists - more mailing lists