From: Dave Hansen <dave.hansen@intel.com>
To: Yeoreum Yun <yeoreum.yun@arm.com>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
bpf@vger.kernel.org
Cc: catalin.marinas@arm.com, david@kernel.org, ryan.roberts@arm.com,
kevin.brodsky@arm.com, sebastian.osterlund@intel.com,
dave.hansen@linux.intel.com, rick.p.edgecombe@intel.com
Subject: Re: [LSF/MM/BPF TOPIC] eBPF isolation with pkeys
Date: Thu, 12 Feb 2026 08:36:53 -0800 [thread overview]
Message-ID: <f20ec2ee-90f2-4ef7-bc3d-088f9ef6c38a@intel.com> (raw)
In-Reply-To: <aY3+Raf8eZqipCd6@e129823.arm.com>
On 2/12/26 08:22, Yeoreum Yun wrote:
> Current status
> ==============
>
> An RFC series is planned for around Q2 2026, and the experimental
> implementations for eBPF isolation with pkey and pkey-aware memory
> allocators have already been completed internally. Using these
> implementations, we verified that eBPF programs running under isolation
> successfully execute several sched_ext applications provided by
> tools/sched_ext, as well as some bpf kselftest cases.
If you have code, post the code, please. It doesn't matter how ugly it is.
> To that end, this discussion introduces a set of new allocator APIs and
> explores more extensible API designs:
>
> - kmalloc_pkey series
> - vmalloc_pkey series
> - alloc_percpu_pkey series
It all sounds fun, but this doesn't exactly seem very generic. The meory
that sched_ext needs to access is super different from, say, what a
socket-filtering eBPF program would need.
So this doesn't seem to be likely to be true "eBPF isolation" as much as
sched_ext+eBPP isolation.
next prev parent reply other threads:[~2026-02-12 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 16:22 Yeoreum Yun
2026-02-12 16:36 ` Dave Hansen [this message]
2026-02-12 17:14 ` Yeoreum Yun
2026-02-12 18:14 ` Dave Hansen
2026-02-16 9:57 ` Yeoreum Yun
2026-02-12 17:44 ` Alexei Starovoitov
2026-02-12 18:01 ` Yeoreum Yun
2026-02-12 18:37 ` Alexei Starovoitov
2026-02-13 10:08 ` Yeoreum Yun
2026-02-13 21:37 ` Alexei Starovoitov
2026-02-16 14:27 ` James Bottomley
2026-02-20 2:50 ` Alexei Starovoitov
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=f20ec2ee-90f2-4ef7-bc3d-088f9ef6c38a@intel.com \
--to=dave.hansen@intel.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=rick.p.edgecombe@intel.com \
--cc=ryan.roberts@arm.com \
--cc=sebastian.osterlund@intel.com \
--cc=yeoreum.yun@arm.com \
/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