From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH tip] x86: vdso: Compute timens page offset statically
Date: Mon, 18 Nov 2024 03:18:59 +0100 [thread overview]
Message-ID: <ZzqkEzxJ69dBSps_@zx2c4.com> (raw)
In-Reply-To: <ZuA5gaOhJNwDSb4x@zx2c4.com>
On Tue, Sep 10, 2024 at 02:20:17PM +0200, Jason A. Donenfeld wrote:
> On Tue, Sep 10, 2024 at 02:08:11PM +0200, Thomas Gleixner wrote:
> > On Mon, Sep 09 2024 at 17:44, Jason A. Donenfeld wrote:
> > > On Fri, Sep 06, 2024 at 09:06:55PM +0200, Jason A. Donenfeld wrote:
> > >> The expression `((void *)&__timens_vdso_data - (void *)&__vdso_data)`
> > >> seems harmless, but it actually results in quite a bit of code and two
> > >> jumps, in a place that's supposed to be somewhat lean on code. The value
> > >> of that calculation is always 3*PAGE_SIZE, as it turns out. Changing it
> > >> to that results in a more modest cmov instruction being emitted. It also
> > >> makes it a bit more clear what's happening.
> > >>
> > >> To accomplish this, define offset macros in vvar.h, which can be shared
> > >> by C code and by the linker script that decides where these pages will
> > >> actually go.
> > >
> > > I noticed we've only got a week left til the merge window opens, so I
> > > thought I should poke you about this, if you want to take this through
> > > tip. I can also take it through my random.git tree with your ack, if
> > > that's easier for you. (Assuming, of course, that this patch is actually
> > > correct.) Let me know.
> >
> > It's not the end of the world if this does not go in now. It's in my
> > back log and that VDSO stuff needs more care than this particular thing
> > as the recent discussion about vdso random on other architectures show.
>
> Okay, that makes sense. And thanks for taking a look.
Thought I'd poke again about this. It looks like this still applies to
tip.
Jason
next prev parent reply other threads:[~2024-11-18 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 19:06 [PATCH tip] x86: vdso: Compute timens page offset statically Jason A. Donenfeld
2024-09-09 15:44 ` Jason A. Donenfeld
2024-09-10 12:08 ` Thomas Gleixner
2024-09-10 12:20 ` Jason A. Donenfeld
2024-11-18 2:18 ` Jason A. Donenfeld [this message]
2024-12-01 13:03 ` Thomas Gleixner
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=ZzqkEzxJ69dBSps_@zx2c4.com \
--to=jason@zx2c4.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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