[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250820093515.17afe135@gandalf.local.home>
Date: Wed, 20 Aug 2025 09:35:15 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Huacai Chen <chenhuacai@...nel.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, 20 Aug 2025 11:03:05 +0800
Huacai Chen <chenhuacai@...nel.org> wrote:
> > Did this fall through the cracks?
> I don't know what this means, but I think you are pinging.
Sorry for the colloquialism, it's not actually the same as a ping. A ping
is for something that had no response. This is more about the patch was
acknowledged but did not go further. "Falling through the cracks" is like
picking a bunch of things up with a bucket that has a crack in it. Some of
those things may "fall through the crack" and not be processed.
>
> 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.
Well, it will start causing warnings soon because it wastes memory. But
that will likely begin in 6.18 so we are OK, as long as it gets into
linux-next before the warning trigger does.
-- Steve
Powered by blists - more mailing lists