From: "Tiwei Bie" <tiwei.btw@antgroup.com>
To: benjamin@sipsolutions.net, linux-um@lists.infradead.org
Cc: Benjamin Berg <benjamin.berg@intel.com>
Subject: Re: [PATCH 00/12] Rework stub syscall and page table handling
Date: Mon, 22 Apr 2024 10:35:35 +0800 [thread overview]
Message-ID: <e213cf20-bf70-4e53-a5f2-5ec88cfa6ff5@antgroup.com> (raw)
In-Reply-To: <20240418092327.860135-1-benjamin@sipsolutions.net>
Hello Benjamin,
On 4/18/24 5:23 PM, benjamin@sipsolutions.net wrote:
> From: Benjamin Berg <benjamin.berg@intel.com>
>
> This patchset reworks the stub syscall handling and also redos how page
> table updates are tracked and synchronized. Some of this originated in
> the SECCOMP patchset, but it became clear that these refactorings make
> sense independently as they result in a considerably fewer page faults.
I saw your SECCOMP patchset. It's pretty cool! Just wondering if you're about
to post a new version soon. :)
PS. Just FYI, gVisor also implemented a SECCOMP based platform which is
also very interesting:
https://gvisor.dev/blog/2023/04/28/systrap-release/
https://github.com/google/gvisor/tree/master/pkg/sentry/platform/systrap
Regards,
Tiwei
next prev parent reply other threads:[~2024-04-22 2:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 9:23 [PATCH 00/12] Rework stub syscall and page table handling benjamin
2024-04-18 9:23 ` [PATCH 01/12] um: Remove stub-data.h include from common-offsets.h benjamin
2024-04-18 9:23 ` [PATCH 02/12] um: Create signal stack memory assignment in stub_data benjamin
2024-04-18 9:23 ` [PATCH 03/12] um: Add generic stub_syscall6 function benjamin
2024-04-18 9:23 ` [PATCH 04/12] um: Rework syscall handling benjamin
2024-04-18 9:23 ` [PATCH 05/12] um: compress memory related stub syscalls while adding them benjamin
2024-04-18 9:23 ` [PATCH 06/12] um: remove LDT support benjamin
2024-04-18 9:23 ` [PATCH 07/12] um: remove copy_context_skas0 benjamin
2024-04-18 9:23 ` [PATCH 08/12] um: Delay flushing syscalls until the thread is restarted benjamin
2024-04-18 9:23 ` [PATCH 09/12] um: Do not flush MM in flush_thread benjamin
2024-04-18 9:23 ` [PATCH 10/12] um: remove force_flush_all from fork_handler benjamin
2024-04-18 9:23 ` [PATCH 11/12] um: simplify and consolidate TLB updates benjamin
2024-04-18 9:23 ` [PATCH 12/12] um: refactor TLB update handling benjamin
2024-04-22 2:51 ` Tiwei Bie
2024-04-22 7:22 ` Benjamin Berg
2024-04-22 7:51 ` Anton Ivanov
2024-04-22 2:35 ` Tiwei Bie [this message]
2024-04-22 7:41 ` [PATCH 00/12] Rework stub syscall and page table handling Benjamin Berg
2024-04-22 12:08 ` Tiwei Bie
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=e213cf20-bf70-4e53-a5f2-5ec88cfa6ff5@antgroup.com \
--to=tiwei.btw@antgroup.com \
--cc=benjamin.berg@intel.com \
--cc=benjamin@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
/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