From: Huacai Chen <chenhuacai@kernel.org>
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: Tiezhu Yang <yangtiezhu@loongson.cn>,
loongarch@lists.linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] LoongArch: BPF: Support more features for trampoline
Date: Wed, 22 Apr 2026 16:06:59 +0800 [thread overview]
Message-ID: <CAAhV-H7PXGyTotvTnw6PKYUdVYzeWVHf5CxP_WxvC5cAdtqBFw@mail.gmail.com> (raw)
In-Reply-To: <CAEyhmHQVTzOohJUAL5FfP39pY=8q=ui7LYE3Z4+n1s71GK3Shw@mail.gmail.com>
On Fri, Feb 27, 2026 at 5:55 PM Hengqi Chen <hengqi.chen@gmail.com> wrote:
>
> On Tue, Feb 24, 2026 at 3:35 PM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
> >
> > This series is based on Linux 7.0-rc1, tested on Loongson-3A6000,
> > the main aim is to support small struct arguments and 12 function
> > arguments for LoongArch BPF trampoline.
> >
> > Tiezhu Yang (3):
> > LoongArch: BPF: Open code and remove invoke_bpf_mod_ret()
> > LoongArch: BPF: Support small struct arguments for trampoline
> > LoongArch: BPF: support 12 function arguments for trampoline
> >
>
> For the series:
> Acked-by: Hengqi Chen <hengqi.chen@gmail.com>
> Tested-by: Hengqi Chen <hengqi.chen@gmail.com>
Applied, thanks.
Huacai
>
> > arch/loongarch/net/bpf_jit.c | 109 +++++++++++++++++++++++------------
> > 1 file changed, 71 insertions(+), 38 deletions(-)
> >
> > --
> > 2.42.0
> >
prev parent reply other threads:[~2026-04-22 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 7:35 [PATCH v1 0/3] LoongArch: BPF: Support more features for trampoline Tiezhu Yang
2026-02-24 7:35 ` [PATCH v1 1/3] LoongArch: BPF: Open code and remove invoke_bpf_mod_ret() Tiezhu Yang
2026-02-24 7:35 ` [PATCH v1 2/3] LoongArch: BPF: Support small struct arguments for trampoline Tiezhu Yang
2026-02-24 7:35 ` [PATCH v1 3/3] LoongArch: BPF: support 12 function " Tiezhu Yang
2026-02-27 9:55 ` [PATCH v1 0/3] LoongArch: BPF: Support more features " Hengqi Chen
2026-04-22 8:06 ` Huacai Chen [this message]
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=CAAhV-H7PXGyTotvTnw6PKYUdVYzeWVHf5CxP_WxvC5cAdtqBFw@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hengqi.chen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=yangtiezhu@loongson.cn \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).