[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241020080919.v4zfqwgpjxhluxaq@treble>
Date: Sun, 20 Oct 2024 01:09:19 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: x86@...nel.org, Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, Indu Bhagat <indu.bhagat@...cle.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Namhyung Kim <namhyung@...nel.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
linux-perf-users@...r.kernel.org, Mark Brown <broonie@...nel.org>,
linux-toolchains@...r.kernel.org, Jordan Rome <jordalgo@...a.com>,
Sam James <sam@...too.org>
Subject: Re: [PATCH v2 02/11] unwind/x86: Add HAVE_USER_UNWIND
On Mon, Sep 16, 2024 at 01:46:05PM +0200, Peter Zijlstra wrote:
> > +#define ARCH_INIT_USER_FP_FRAME \
> > + .ra_off = (s32)sizeof(long) * -1, \
> > + .cfa_off = (s32)sizeof(long) * 2, \
> > + .fp_off = (s32)sizeof(long) * -2, \
> > + .use_fp = true,
>
> What about compat crap?
Sframe doesn't support x86 compat so I guess we don't need to worry
about that at least for now.
--
Josh
Powered by blists - more mailing lists