From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Greg Ungerer <gerg@kernel.org>
Cc: geert@linux-m68k.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, jserv@ccns.ncku.edu.tw, eleanor15x@gmail.com,
marscheng@google.com, linux-kernel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, bpf@vger.kernel.org,
Daniel Palmer <daniel@thingy.jp>
Subject: Re: [PATCH bpf-next v3] m68k, bpf: Add initial BPF JIT compiler support
Date: Tue, 19 May 2026 01:07:09 +0800 [thread overview]
Message-ID: <agtHPT7Oo4MZ6CBc@google.com> (raw)
In-Reply-To: <f30f7e98-4749-4925-b999-2653941b42ee@kernel.org>
Hi greg,
On Tue, May 12, 2026 at 09:57:11PM +1000, Greg Ungerer wrote:
> Hi Kuan-Wei,
>
> On 12/5/26 07:27, Kuan-Wei Chiu wrote:
> > Add a BPF JIT compiler for the m68k architecture.
> >
> > The JIT generates m68k machine code targeting m68020+ processors. It
> > currently excludes 68000/68010 and coldfire processors, as it relies on
> > 32 bit branch displacements (b<cc>.l) to handle large bpf programs.
>
> FWIW the ColdFire ISA_B and newer instruction set extensions do support
> the 32 bit branch displacement instruction forms. So that would mean that
> at least the MMU based version 4 cores may be able to be supported
> without too much extra effort.
>
Sorry for getting back to you so late, and thanks for the info!
I haven't thoroughly checked what else the current implementation might
lack for coldfire support, but I suspect it won't be as simple as just
modifying the kconfig. For instance, at least the exg instruction I'm
currently using is not supported on coldfire.
Since the current patch is already quite large, I'm inclined to focus
on getting everything running correctly on classic m68k first. Once
this initial support is merged in-tree, we can revisit it and figure
out the necessary adjustments for coldfire.
That being said, getting coldfire supported would definitely be cool!
Regards,
Kuan-Wei
next prev parent reply other threads:[~2026-05-18 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 21:27 [PATCH bpf-next v3] m68k, bpf: Add initial BPF JIT compiler support Kuan-Wei Chiu
2026-05-11 22:12 ` bot+bpf-ci
2026-05-18 17:21 ` Kuan-Wei Chiu
2026-05-12 11:57 ` Greg Ungerer
2026-05-18 17:07 ` Kuan-Wei Chiu [this message]
2026-05-12 17:32 ` Andreas Schwab
2026-05-18 17:12 ` Kuan-Wei Chiu
2026-05-13 1:03 ` sashiko-bot
2026-05-18 17:32 ` Kuan-Wei Chiu
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=agtHPT7Oo4MZ6CBc@google.com \
--to=visitorckw@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=daniel@thingy.jp \
--cc=eddyz87@gmail.com \
--cc=eleanor15x@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.org \
--cc=jolsa@kernel.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=marscheng@google.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox