From: jeffxu@chromium.org
To: akpm@linux-foundation.org, pedro.falcato@gmail.com
Cc: jeffxu@google.com, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, Jeff Xu <jeffxu@chromium.org>
Subject: [PATCH v1 0/1] branch prediction hint
Date: Tue, 23 Apr 2024 19:28:24 +0000 [thread overview]
Message-ID: <20240423192825.1273679-1-jeffxu@chromium.org> (raw)
From: Jeff Xu <jeffxu@chromium.org>
This is followup patch on discussion happened during mseal v10 discussion [1]
Add branch perdiction hint to mseal code.
Please apply on top of mseal v10 patch
(which already in mm-unstable)
[1]
https://lore.kernel.org/lkml/CAJuCfpFLwJg4n7wPpT+u9vC4XHoLE_BPPZ0tDKf7W45hGky4_Q@mail.gmail.com/T/#m20917ddbc4f817ebeb99276108b1f3ceffacb5c1
Thanks!
-Jeff
Jeff Xu (1):
mseal: Add branch prediction hint.
mm/madvise.c | 2 +-
mm/mmap.c | 4 ++--
mm/mprotect.c | 2 +-
mm/mremap.c | 4 ++--
mm/mseal.c | 6 +++---
5 files changed, 9 insertions(+), 9 deletions(-)
--
2.44.0.769.g3c40516874-goog
next reply other threads:[~2024-04-23 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 19:28 jeffxu [this message]
2024-04-23 19:28 ` [PATCH v1 1/1] mseal: Add " jeffxu
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=20240423192825.1273679-1-jeffxu@chromium.org \
--to=jeffxu@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=jeffxu@google.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pedro.falcato@gmail.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