From: will schmidt <will_schmidt@vnet.ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"cel@us.ibm.com" <cel@us.ibm.com>
Cc: Rogerio Alves Cardoso <rogealve@br.ibm.com>
Subject: Re: [PATCH] PowerPC: bp-permanent.exp, kill-after-signal fix
Date: Mon, 02 May 2022 12:18:58 -0500 [thread overview]
Message-ID: <02f8062ee4eb348878f76ba7f2cb1a7a518db763.camel@vnet.ibm.com> (raw)
In-Reply-To: <1dcf7a9570b13e68d035840261dc1dc9a9baad5c.camel@de.ibm.com>
On Mon, 2022-05-02 at 15:10 +0000, Ulrich Weigand wrote:
> will schmidt <will_schmidt@vnet.ibm.com> wrote:
>
> > So.. Is this directly related to the amount of kernel code
> > handling
> > the signals? i.e. Would this need to be updated if another
> instruction
> > is added to the kernel code?
>
> To clarify, this not *kernel* code, it's user space code, but code
> that is placed by the kernel into user space (in the vdso).
>
> Many platforms today use the vdso in the signal *return* path, but
> Power seems special in that it is using a vdso instruction also to
> *enter* a signal handler in the first place. (So instead of the
> kernel directly dispatching to the installed signal handler, it
> first dispatches to vdso code which in turn calls into the signal
> handler.)
>
> Reading the kernel logs, this seems to have been a performance
> optimization to prevent the call/return stack from getting out
> of balance.
>
> That vdso code path when entering a signal handler is just a
> single "brctl"; I don't see any particular reason why this would
> ever need to become any longer.
Ok, thanks for clarifying.
I look forward to seeing the updated
comments in the next version of the patch by Carl. :-)
Thanks
-Will
>
> Bye,
> Ulrich
>
prev parent reply other threads:[~2022-05-02 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 1:06 Carl Love
2022-05-02 14:09 ` Ulrich Weigand
2022-05-02 14:32 ` Pedro Alves
2022-05-02 14:55 ` will schmidt
2022-05-02 15:19 ` Carl Love
2022-05-02 15:24 ` Pedro Alves
2022-05-03 20:10 ` Carl Love
2022-05-06 16:16 ` Pedro Alves
2022-05-09 17:35 ` Tom de Vries
2022-05-09 19:22 ` Carl Love
2022-05-09 20:43 ` [PATCH Fixup] " Carl Love
2022-05-10 9:27 ` Tom de Vries
2022-05-10 15:13 ` Carl Love
2022-05-10 19:07 ` [PATCH Fixup V2] " Carl Love
2022-05-16 15:46 ` [PATCH PING " Carl Love
2022-05-18 7:33 ` Tom de Vries
2022-05-02 15:04 ` [PATCH] " will schmidt
2022-05-02 15:10 ` Ulrich Weigand
2022-05-02 17:18 ` will schmidt [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=02f8062ee4eb348878f76ba7f2cb1a7a518db763.camel@vnet.ibm.com \
--to=will_schmidt@vnet.ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=rogealve@br.ibm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).