[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very earl
From: |
Samuel Thibault |
Subject: |
Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early |
Date: |
Sat, 22 Apr 2023 13:59:21 +0200 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
Sergey Bugaev, le ven. 21 avril 2023 16:56:57 +0300, a ecrit:
> On Fri, Apr 21, 2023 at 3:58 PM Adhemerval Zanella Netto
> <adhemerval.zanella@linaro.org> wrote:
> > > Yes, sure, I wasn't really suggesting we do that change. My point is,
> > > I would like to make the same memcpy callsites both work during early
> > > startup and start calling the more efficient implementation once early
> > > startup is done -- if that's possible.
> >
> > That's the whole idea of dl-symbol-redir-ifunc.h, since it is explicit
> > enable by TU.
>
> Then I must be misunderstanding how dl-symbol-redir-ifunc.h works
> (please explain!),
>
> because I don't see how it would achieve that. Doesn't it change all
> memcpy calls in the current translation unit (.c file) to always call
> the baseline memcpy -- not only during startup, but even after the
> startup has been completed?
Perhaps we can generate "init" variants of the RPCs that we need at
initialization, that are made to use the base memcpy implementation, and
only use them in the init code?
Samuel
- [PATCH 1/2] hurd: Don't migrate reply port into __init1_tcbhead, Sergey Bugaev, 2023/04/20
- [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/20
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, H.J. Lu, 2023/04/20
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Adhemerval Zanella Netto, 2023/04/20
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/21
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Adhemerval Zanella Netto, 2023/04/21
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/21
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Adhemerval Zanella Netto, 2023/04/21
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/21
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Adhemerval Zanella Netto, 2023/04/21
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early,
Samuel Thibault <=
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/22
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Samuel Thibault, 2023/04/22
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/22
- Re: [VERY RFC PATCH 2/2] hurd: Make it possible to call memcpy very early, Sergey Bugaev, 2023/04/21
Re: [PATCH 1/2] hurd: Don't migrate reply port into __init1_tcbhead, Samuel Thibault, 2023/04/20