mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
	Nathan Chancellor <nathan@kernel.org>,
	Calvin Owens <calvin@wbinvd.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 8aeb879baf12 - significant system call latency regression, bisected
Date: Fri, 19 Jun 2026 13:18:48 +0200	[thread overview]
Message-ID: <20260619111848.GO42921@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <6B52EE70-FB51-4053-B888-DD3EC6D66C54@zytor.com>

On Fri, Jun 19, 2026 at 03:23:52AM -0700, H. Peter Anvin wrote:
> On June 19, 2026 1:14:27 AM PDT, Peter Zijlstra <peterz@infradead.org> wrote:
> >On Wed, Jun 17, 2026 at 02:37:18PM +0200, Peter Zijlstra wrote:
> >>  - makes -fno-jump-tables unconditional
> >>  - removes array_index_nospec() from the syscall dispatch
> >
> >FWIW, this also allows making all SYSCALLs __noendbr, very much
> >including the 'legacy' sys_call_table :-)
> >
> >Compile tested with IA32_EMULATION=n and reliably yields:
> >
> >vmlinux.o: warning: objtool: sys_call_table+0x0: data relocation to !ENDBR: __x64_sys_read+0x0
> >...
> >vmlinux.o: warning: objtool: sys_call_table+0xeb0: data relocation to !ENDBR: __x64_sys_listns+0x0
> >
> >(which is just one little objtool patch away from being fixed)
> >
> >and boots fine (in kvm).

> *Very* nice indeed. 
> 
> I was definitely hoping this would be the next step.

A few patches here:

  git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/syscall

That now includes IA32_EMULATION and a few terse changelogs. The
alignment thing went missing since that didn't seem to be very good.


  reply	other threads:[~2026-06-19 11:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-13  1:45 "H. Peter Anvin" (Intel)
2026-06-13  8:59 ` Peter Zijlstra
2026-06-13 20:34   ` H. Peter Anvin
2026-06-13 23:52     ` H. Peter Anvin
2026-06-14  1:50       ` H. Peter Anvin
2026-06-14 18:08         ` Xin Li
2026-06-14 18:31           ` H. Peter Anvin
2026-06-15  0:19         ` H. Peter Anvin
2026-06-15  2:07           ` H. Peter Anvin
2026-06-15  3:41             ` Linus Torvalds
2026-06-15 18:30               ` H. Peter Anvin
2026-06-16  7:12                 ` Peter Zijlstra
2026-06-16  7:38             ` Peter Zijlstra
2026-06-16  7:53             ` Peter Zijlstra
2026-06-18 23:05               ` H. Peter Anvin
2026-06-19  7:50                 ` Peter Zijlstra
2026-06-19 10:22                   ` H. Peter Anvin
2026-06-16  8:28         ` Peter Zijlstra
2026-06-16  8:46           ` Linus Torvalds
2026-06-16  9:51             ` Ingo Molnar
2026-06-16 17:44               ` H. Peter Anvin
2026-06-17  9:54                 ` Ingo Molnar
2026-06-17 10:05                   ` Ingo Molnar
2026-06-17 12:37             ` Peter Zijlstra
2026-06-18 22:40               ` H. Peter Anvin
2026-06-19  1:11                 ` H. Peter Anvin
2026-06-19  2:08                   ` Linus Torvalds
2026-06-19  2:11                     ` Linus Torvalds
2026-06-19  4:32                       ` H. Peter Anvin
2026-06-19  7:35                         ` Peter Zijlstra
2026-06-19  2:11                     ` H. Peter Anvin
2026-06-19  7:31                 ` Peter Zijlstra
2026-06-19  8:14               ` Peter Zijlstra
2026-06-19 10:23                 ` H. Peter Anvin
2026-06-19 11:18                   ` Peter Zijlstra [this message]
2026-06-19 21:53                     ` syscall path improvements (was: syscall performance regression, debunked) H. Peter Anvin
2026-06-16 13:53           ` 8aeb879baf12 - significant system call latency regression, bisected David Laight
2026-06-18 23:03             ` H. Peter Anvin
2026-06-14  2:11       ` Calvin Owens
2026-06-14  2:14         ` Calvin Owens

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=20260619111848.GO42921@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=calvin@wbinvd.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nathan@kernel.org \
    --cc=tglx@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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

Powered by JetHome