From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Roger Pau Monné" <roger@xenproject.org>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/3] x86/alternatives: Rework get_ideal_nops()
Date: Wed, 5 Aug 2026 10:46:55 +0200 [thread overview]
Message-ID: <ffbe1886-553c-499d-bbbc-fa239b671850@suse.com> (raw)
In-Reply-To: <20260805075303.23105-1-andrew.cooper3@citrix.com>
On 05.08.2026 09:53, Andrew Cooper wrote:
> The {k8,p6}_nops[] arrays are both 80-byte structures indexing 45-byte
> structures. Furthermore, perhaps unusually for C, the source layout is an
> obvious hint about the triangular nature of the structure.
>
> Therefore, we can replace the pointer chase with some simple arithmetic.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
next prev parent reply other threads:[~2026-08-05 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 15:00 [PATCH 0/3] x86/alt: Simplify nops handling Andrew Cooper
2025-05-22 15:00 ` [PATCH 1/3] x86/alternatives: Factor out access to ideal_nops[] Andrew Cooper
2025-06-02 9:50 ` Jan Beulich
2025-05-22 15:00 ` [PATCH 2/3] x86/alternatives: Rework get_ideal_nops() Andrew Cooper
2025-06-02 9:57 ` Jan Beulich
2026-08-04 17:13 ` Andrew Cooper
2026-08-05 6:04 ` Jan Beulich
2026-08-05 6:34 ` Andrew Cooper
2026-08-05 6:49 ` Jan Beulich
2026-08-05 7:53 ` [PATCH v2 " Andrew Cooper
2026-08-05 8:46 ` Jan Beulich [this message]
2025-05-22 15:00 ` [PATCH 3/3] x86/alternatives: Introduce init_or_livepatch_ro_after_init Andrew Cooper
2025-06-02 9:59 ` Jan Beulich
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=ffbe1886-553c-499d-bbbc-fa239b671850@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger@xenproject.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.