From: Sasha Levin <sashal@kernel.org>
To: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Cc: stable@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
kernel-dev@igalia.com
Subject: Re: [PATCH 5.15 0/5] Support static calls with LLVM-built kernels
Date: Sat, 16 Mar 2024 05:41:16 -0400 [thread overview]
Message-ID: <ZfVpPMl3JJakSHT1@sashalap> (raw)
In-Reply-To: <20240313104255.1083365-1-cascardo@igalia.com>
On Wed, Mar 13, 2024 at 07:42:50AM -0300, Thadeu Lima de Souza Cascardo wrote:
>Peter Zijlstra (4):
> arch: Introduce CONFIG_FUNCTION_ALIGNMENT
> x86/alternatives: Introduce int3_emulate_jcc()
> x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions
> x86/static_call: Add support for Jcc tail-calls
>
>Thomas Gleixner (1):
> x86/asm: Differentiate between code and function alignment
Is this not an issue on 6.1? I don't see d49a0626216b ("arch: Introduce
CONFIG_FUNCTION_ALIGNMENT") in that tree.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-03-16 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 10:42 [PATCH 5.15 0/5] Support static calls with LLVM-built kernels Thadeu Lima de Souza Cascardo
2024-03-13 10:42 ` [PATCH 5.15 1/5] arch: Introduce CONFIG_FUNCTION_ALIGNMENT Thadeu Lima de Souza Cascardo
2024-03-13 10:42 ` [PATCH 5.15 2/5] x86/asm: Differentiate between code and function alignment Thadeu Lima de Souza Cascardo
2024-03-13 10:42 ` [PATCH 5.15 3/5] x86/alternatives: Introduce int3_emulate_jcc() Thadeu Lima de Souza Cascardo
2024-03-13 10:42 ` [PATCH 5.15 4/5] x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions Thadeu Lima de Souza Cascardo
2024-03-13 10:42 ` [PATCH 5.15 5/5] x86/static_call: Add support for Jcc tail-calls Thadeu Lima de Souza Cascardo
2024-03-16 9:41 ` Sasha Levin [this message]
2024-03-16 10:02 ` [PATCH 5.15 0/5] Support static calls with LLVM-built kernels Thadeu Lima de Souza Cascardo
2024-03-16 11:01 ` Sasha Levin
2024-03-16 11:08 ` Thadeu Lima de Souza Cascardo
2024-03-29 12:43 ` Greg KH
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=ZfVpPMl3JJakSHT1@sashalap \
--to=sashal@kernel.org \
--cc=cascardo@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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