mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
	Jinyang He <hejinyang@loongson.cn>,
	 WANG Rui <wangrui@loongson.cn>, Mingcong Bai <jeffbai@aosc.io>,
	Zixing Liu <liushuyu@aosc.io>, "H . Peter Anvin"	 <hpa@zytor.com>,
	stable@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
	 Menglong Dong <menglong8.dong@gmail.com>,
	Bibo Mao <maobibo@loongson.cn>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	 Hanlu Li <lihanlu@loongson.cn>,
	Nathan Chancellor <nathan@kernel.org>,
	Jiaxun Yang	 <jiaxun.yang@flygoat.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Wentao Guan	 <guanwentao@uniontech.com>,
	loongarch@lists.linux.dev, 	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] LoongArch: vDSO: Emit GNU_EH_FRAME correctly
Date: Fri, 27 Feb 2026 18:08:23 +0800	[thread overview]
Message-ID: <dfc96603201cf067e341c13e5aa5e9bee9712e2f.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H6+Q_b4cr8jj3hmy1__h3060geMohx7hm1V8NvmeKPSiQ@mail.gmail.com>

On Fri, 2026-02-27 at 18:04 +0800, Huacai Chen wrote:
> On Fri, Feb 27, 2026 at 5:57 PM Xi Ruoyao <xry111@xry111.site> wrote:
> > 
> > On Fri, 2026-02-27 at 16:58 +0800, Huacai Chen wrote:
> > 
> > /* snip */
> > 
> > > > diff --git a/arch/loongarch/include/asm/sigframe.h b/arch/loongarch/include/asm/sigframe.h
> > > > new file mode 100644
> > > > index 000000000000..59db3de6db85
> > > > --- /dev/null
> > > > +++ b/arch/loongarch/include/asm/sigframe.h
> > > > @@ -0,0 +1,12 @@
> > > > +/* SPDX-License-Identifier: GPL-2.0+ */
> > > > +/*
> > > > + * Separated from arch/loongarch/kernel/signal.c.
> > > I think this is also unnecessary.
> > 
> > Will remove this comment.
> > 
> > /* snip */
> > 
> > > > +        * This is also the reason we don't use SYM_FUNC_START.
> > > > +        */
> > > > +       nop
> > > > +SYM_START(__vdso_rt_sigreturn, SYM_L_GLOBAL, SYM_A_ALIGN)
> > > Is it possible to define SYM_SIGFUNC_START/SYM_SIGFUNC_END in
> > > linkage.h, and then use them here?
> > 
> > How about SYM_FUNC_{START,END}_NOCFI instead?
> Of course I don't know how to name them, I just want to define a
> wrapper to contain all .cfi_xxxx in this patch.

Will do it.  If they contain all the .cfi_ directives your naming is
better.

-- 
Xi Ruoyao <xry111@xry111.site>

      reply	other threads:[~2026-02-27 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  7:18 Xi Ruoyao
2026-02-27  8:58 ` Huacai Chen
2026-02-27  9:57   ` Xi Ruoyao
2026-02-27 10:04     ` Huacai Chen
2026-02-27 10:08       ` Xi Ruoyao [this message]

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=dfc96603201cf067e341c13e5aa5e9bee9712e2f.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=ardb@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=guanwentao@uniontech.com \
    --cc=hejinyang@loongson.cn \
    --cc=hpa@zytor.com \
    --cc=jeffbai@aosc.io \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=lihanlu@loongson.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liushuyu@aosc.io \
    --cc=loongarch@lists.linux.dev \
    --cc=maobibo@loongson.cn \
    --cc=menglong8.dong@gmail.com \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=wangrui@loongson.cn \
    --cc=yangtiezhu@loongson.cn \
    /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

all inboxes | Powered by JetHome®