public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Sunil Pandey <skpgkp2@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>,
	 Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>,
	 "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: PING^2: V4 [PATCH] x86: Initialize CPU info via IFUNC relocation [BZ 26203]
Date: Mon, 2 May 2022 06:59:42 -0700	[thread overview]
Message-ID: <CAMAf5_eyAXfPe3knfgka6Ax1xgRQn4C_-jknejYZ7O5Fyx-5PQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpK-d_0u08j7b5PecErpM+FDxK0cSYXwxG776RMXB8o0Q@mail.gmail.com>

On Thu, Oct 15, 2020 at 5:54 AM H.J. Lu via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> On Thu, Oct 8, 2020 at 6:22 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On Thu, Oct 1, 2020 at 12:50 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >
> > > On Thu, Oct 1, 2020 at 1:46 AM Florian Weimer <fweimer@redhat.com> wrote:
> > > >
> > > > * H. J. Lu:
> > > >
> > > > > diff --git a/sysdeps/x86/cacheinfo.c b/sysdeps/x86/cacheinfo.c
> > > > > index dadec5d58f..65ab29123d 100644
> > > > > --- a/sysdeps/x86/cacheinfo.c
> > > > > +++ b/sysdeps/x86/cacheinfo.c
> > > > > @@ -16,7 +16,9 @@
> > > > >     License along with the GNU C Library; if not, see
> > > > >     <https://www.gnu.org/licenses/>.  */
> > > > >
> > > > > -#if IS_IN (libc)
> > > > > +/* NB: In libc.a, this file is included in libc-static.c.  In libc.so,
> > > > > +   this file is standalone.  */
> > > > > +#if IS_IN (libc) && (defined SHARED || defined _PRIVATE_CPU_FEATURES_H)
> > > >
> > > > libc-static.c should be libc-start.c, I believe.  The “defined
> > > > _PRIVATE_CPU_FEATURES_H” part seems rather indirect.  What exactly are
> > > > you trying to accomplish here?
> > > >
> > > > It looks to me as if this file should included in libc.so, but not
> > > > pulled into ld.so via the rebuild, so maybe you can add an empty
> > > > sysdeps/x86/rtld-cacheinfo.c file instead?
> > > >
> > >
> > > Here is the updated patch.   I also moved files around to prepare
> > > for moving x86 processor cache info to cpu_features in ld.so to
> > > support --list-tunables.
> > >
> >
> > PING:
> >
> > https://sourceware.org/pipermail/libc-alpha/2020-October/118228.html
> >
>
> I will check it in tomorrow if there are no objections.
>
> Thanks.
>
> --
> H.J.

I would like to backport this patch to release branches.
Any comments or objections?

--Sunil

       reply	other threads:[~2022-05-02 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200918160709.949608-1-hjl.tools@gmail.com>
     [not found] ` <20200918160709.949608-2-hjl.tools@gmail.com>
     [not found]   ` <87imby6obw.fsf@oldenburg2.str.redhat.com>
     [not found]     ` <CAMe9rOo_OUmsikKWj_pXiy-G+NJZGGJwzn2_YTczXPvd09FaRA@mail.gmail.com>
     [not found]       ` <87y2ku574k.fsf@oldenburg2.str.redhat.com>
     [not found]         ` <CAMe9rOqjzDHL+O04FSCzRdnANJK0_3o5pDCd2UGyFsce+mU8Kg@mail.gmail.com>
     [not found]           ` <87lfgu56c8.fsf@oldenburg2.str.redhat.com>
     [not found]             ` <CAMe9rOoR_m6L7XUyMBjtqT_c80eiNUjuSOD112iX-Wne6cCYvQ@mail.gmail.com>
     [not found]               ` <87pn663qm5.fsf@oldenburg2.str.redhat.com>
     [not found]                 ` <CAMe9rOr7g6YCD3V+B-bUGvRbzZbBfMB5pYuiOibunBYpdaT57g@mail.gmail.com>
     [not found]                   ` <87ft71yq64.fsf@oldenburg2.str.redhat.com>
     [not found]                     ` <CAMe9rOpJWfY8rrNYycusxdnfEXe70ehXK2EJ1NCpNLPks=nEXw@mail.gmail.com>
     [not found]                       ` <87362yl4fh.fsf@oldenburg2.str.redhat.com>
     [not found]                         ` <CAMe9rOpfdPx_0nKT74Ay6zZ7AQBB2Emk7JQtNzk46_+gue9gwg@mail.gmail.com>
     [not found]                           ` <CAMe9rOpR=hoQwxMouCGE0mtDD5U3OYc9FWvOEtNEqpg2rbbHVQ@mail.gmail.com>
     [not found]                             ` <CAMe9rOpK-d_0u08j7b5PecErpM+FDxK0cSYXwxG776RMXB8o0Q@mail.gmail.com>
2022-05-02 13:59                               ` Sunil Pandey [this message]
2022-05-03 18:51                                 ` Sunil Pandey

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=CAMAf5_eyAXfPe3knfgka6Ax1xgRQn4C_-jknejYZ7O5Fyx-5PQ@mail.gmail.com \
    --to=skpgkp2@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@sourceware.org \
    /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).