From: George Guo <dongtai.guo@linux.dev>
To: chenhuacai@kernel.org
Cc: yangtiezhu@loongson.cn, hengqi.chen@gmail.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, kernel@xen0n.name,
martin.lau@linux.dev, eddyz87@gmail.com, memxor@gmail.com,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
guodongtai@kylinos.cn, bpf@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] LoongArch: BPF: per-CPU address resolution and timed may_goto
Date: Wed, 5 Aug 2026 17:10:30 +0800 [thread overview]
Message-ID: <20260805091030.12257-1-dongtai.guo@linux.dev> (raw)
In-Reply-To: <CAAhV-H7aPXsN_jami_2MKJ9CTcpr8YviSJXUxT8s1GMRUEP7wA@mail.gmail.com>
Hi Huacai,
On Wed, Aug 5, 2026 at 3:11 PM, Huacai Chen <chenhuacai@kernel.org> wrote:
> In V1 it is independent,
> In V2 it is part of [...] the 11-patch series
> In V3 it is independent again.
>
> What do you want?
You are right that the v1 -> v2 -> v3 shape looks inconsistent. The plan
has always been incremental: Tiezhu suggested sending this work as small,
stacked series -- A first, then B rebased on A, then C on B -- so each
round stays small enough to review carefully. My v2 bundled all 11 patches
to show the full picture, but that was too large to review effectively, so
v3 goes back to the incremental approach.
Concretely, this 2-patch series (per-CPU MOV + timed may_goto) is A. The
remaining pieces -- private stack, exceptions/bpf_throw, arena LDSX and
atomics, and the matching selftests -- will follow as separate series
stacked on top of it. The structure stays incremental from here.
> You can ask Tiezhu and Hengqi to review your patches, but don't do such
> confusing things.
Understood. I will keep the split stable and ask Tiezhu and Hengqi to
review this batch.
Thanks,
George
next prev parent reply other threads:[~2026-08-05 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 15:39 [PATCH v3 0/2] LoongArch: BPF: per-CPU address resolution and timed may_goto George Guo
2026-08-04 15:39 ` [PATCH v3 1/2] LoongArch: BPF: Support internal-only MOV to resolve per-CPU addrs George Guo
2026-08-04 15:39 ` [PATCH v3 2/2] LoongArch: BPF: Add timed may_goto support George Guo
2026-08-05 7:11 ` [PATCH v3 0/2] LoongArch: BPF: per-CPU address resolution and timed may_goto Huacai Chen
2026-08-05 9:10 ` George Guo [this message]
2026-08-06 12:22 ` Tiezhu Yang
2026-08-09 4:09 ` Huacai Chen
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=20260805091030.12257-1-dongtai.guo@linux.dev \
--to=dongtai.guo@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=guodongtai@kylinos.cn \
--cc=hengqi.chen@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=yangtiezhu@loongson.cn \
--cc=yonghong.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.