public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Evan Green <evan@rivosinc.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	libc-alpha@sourceware.org,  slewis@rivosinc.com,
	palmer@rivosinc.com, vineetg@rivosinc.com
Subject: Re: [PATCH v6 5/5] riscv: Add and use alignment-ignorant memcpy
Date: Mon, 7 Aug 2023 15:30:53 -0700	[thread overview]
Message-ID: <CALs-HsuD=87VasML7KiQ-6XZqE1s9+quzgMsuuu-C32GpyqK9g@mail.gmail.com> (raw)
In-Reply-To: <878ramebon.fsf@oldenburg.str.redhat.com>

On Mon, Aug 7, 2023 at 3:21 PM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Evan Green:
>
> > Right, this is what we had in the previous iteration of this series,
> > and it did work ok. But it wasn't as good since it meant ifunc
> > selectors always got stuck in the null/fallback case and were forced
> > to make the syscall. With this mechanism they get to take advantage of
> > the vDSO.
>
> The system call is only required when the IFUNC resolver is called in
> advance of relocation.  In most cases, the ELF dependencies work as
> expected and ensure that the object containing the IFUNC resolver is
> already relocation, and use of the fallback is avoided.

Ah that's true, we did have to go through some hoops with LD_BIND_NOW
and LD_PRELOAD to observe problems. So the cases where the
__riscv_hwprobe_early() approach doesn't get to use the vDSO isn't
"always" as I stated above but "certain exotic cases". I'm still
leaning towards the ifunc parameter (now with inline helper in the
header), but could be convinced to go back to the _early() function if
there's some advantage to it.

-Evan


>
> Thanks,
> Florian
>

  reply	other threads:[~2023-08-07 22:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 15:58 [PATCH v6 0/5] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green
2023-08-02 15:58 ` [PATCH v6 1/5] riscv: Add Linux hwprobe syscall support Evan Green
2023-08-02 16:52   ` Joseph Myers
2023-08-03  7:24   ` Florian Weimer
2023-08-02 15:59 ` [PATCH v6 2/5] riscv: Add hwprobe vdso call support Evan Green
2023-08-02 15:59 ` [PATCH v6 3/5] riscv: Add __riscv_hwprobe pointer to ifunc calls Evan Green
2023-08-02 15:59 ` [PATCH v6 4/5] riscv: Enable multi-arg ifunc resolvers Evan Green
2023-08-02 15:59 ` [PATCH v6 5/5] riscv: Add and use alignment-ignorant memcpy Evan Green
2023-08-03  7:25   ` Florian Weimer
2023-08-03 17:50     ` Richard Henderson
2023-08-03 18:42       ` Evan Green
2023-08-03 22:30         ` Richard Henderson
2023-08-07 22:10           ` Evan Green
2023-08-07 22:21             ` Florian Weimer
2023-08-07 22:30               ` Evan Green [this message]
2023-08-07 22:48             ` enh
2023-08-08  0:01               ` Evan Green
2023-08-12  0:01                 ` enh
2023-08-15 16:40                   ` Evan Green
2023-08-15 21:53                     ` enh
2023-08-15 23:01                       ` Evan Green
2023-08-16 23:18                         ` enh
2023-08-17 16:27                           ` Evan Green
2023-08-17 16:37                             ` enh
2023-08-17 17:40                               ` Evan Green
2023-08-22 15:06                                 ` enh
2023-08-02 16:03 ` [PATCH v6 0/5] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green

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='CALs-HsuD=87VasML7KiQ-6XZqE1s9+quzgMsuuu-C32GpyqK9g@mail.gmail.com' \
    --to=evan@rivosinc.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@rivosinc.com \
    --cc=richard.henderson@linaro.org \
    --cc=slewis@rivosinc.com \
    --cc=vineetg@rivosinc.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).