[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMzpN2j1zk854JnoFSP4uh+xJQpz3qfwE6T21J+ic7YrKJJ8yQ@mail.gmail.com>
Date: Mon, 12 May 2025 08:10:02 -0400
From: Brian Gerst <brgerst@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: "Xin Li (Intel)" <xin@...or.com>, linux-kernel@...r.kernel.org, luto@...nel.org,
tglx@...utronix.de, mingo@...nel.org, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com
Subject: Re: [PATCH v4 1/2] x86/fred: Allow variable-sized event frame
On Mon, May 12, 2025 at 5:30 AM Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Sun, May 11, 2025 at 11:43:52PM -0700, Xin Li (Intel) wrote:
>
>
> > -#define INIT_THREAD_INFO(tsk) \
> > -{ \
> > - .flags = 0, \
> > +extern unsigned long __top_init_kernel_stack[];
> > +
> > +#define INIT_THREAD_INFO(tsk) \
> > +{ \
> > + .flags = 0, \
> > + .user_pt_regs = (struct pt_regs *)__top_init_kernel_stack, \
>
> Should that not have a -1 on or something?
No, that symbol already accounts for subtracting the size of pt_regs.
Brian Gerst
Powered by blists - more mailing lists