public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein <goldstein.w.n@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org, carlos@systemhalted.org
Subject: Re: [PATCH v1] x86: Fix incorrect scope of setting `shared_per_thread`
Date: Thu, 10 Aug 2023 21:51:25 -0500	[thread overview]
Message-ID: <CAFUsyf+B0qHrXUjrdovOr73L9uRpNLQzJ-41NCHE5ER0ui4R3g@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqa2gA-9fgpqx=qYejS1ra8pZh6WJWxMdcfkszzhS+OeA@mail.gmail.com>

On Thu, Aug 10, 2023 at 8:38 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Thu, Aug 10, 2023 at 5:31 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> >
> > The:
> >
> > ```
> >     if (shared_per_thread > 0 && threads > 0)
> >       shared_per_thread /= threads;
> > ```
> >
> > Code was accidentally moved to inside the else scope.  This doesn't
> > match how it was previously (before af992e7abd).
> >
> > This patch fixes that by putting the division after the `else` block.
>
> Since it is a regression, we should open a bug and backport this
> fix.

Done: See https://sourceware.org/bugzilla/show_bug.cgi?id=30745
FYI: I changed title to include BZ number so doesn't reply in chain.
>
> > ---
> >  sysdeps/x86/dl-cacheinfo.h | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/sysdeps/x86/dl-cacheinfo.h b/sysdeps/x86/dl-cacheinfo.h
> > index 285773039f..88316a7818 100644
> > --- a/sysdeps/x86/dl-cacheinfo.h
> > +++ b/sysdeps/x86/dl-cacheinfo.h
> > @@ -770,11 +770,10 @@ get_common_cache_info (long int *shared_ptr, long int * shared_per_thread_ptr, u
> >              level.  */
> >           threads = ((cpu_features->features[CPUID_INDEX_1].cpuid.ebx >> 16)
> >                      & 0xff);
> > -
> > +        }
> >           /* Get per-thread size of highest level cache.  */
> >           if (shared_per_thread > 0 && threads > 0)
> >             shared_per_thread /= threads;
> > -       }
> >      }
> >
> >    /* Account for non-inclusive L2 and L3 caches.  */
> > --
> > 2.34.1
> >
>
>
> --
> H.J.

  reply	other threads:[~2023-08-11  2:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  0:31 Noah Goldstein
2023-08-11  1:37 ` H.J. Lu
2023-08-11  2:51   ` Noah Goldstein [this message]
2023-08-11  2:50 ` [PATCH v2] x86: Fix incorrect scope of setting `shared_per_thread` [BZ# 30745] Noah Goldstein
2023-08-11  7:46   ` Andreas Schwab
2023-08-11 17:29     ` Noah Goldstein
2023-08-11 17:29 ` [PATCH v3] " Noah Goldstein
2023-08-11 17:31   ` H.J. Lu
2023-08-11 18:35     ` Carlos O'Donell
2023-08-11 19:38   ` Carlos O'Donell
2023-08-11 20:33     ` Noah Goldstein

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=CAFUsyf+B0qHrXUjrdovOr73L9uRpNLQzJ-41NCHE5ER0ui4R3g@mail.gmail.com \
    --to=goldstein.w.n@gmail.com \
    --cc=carlos@systemhalted.org \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@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).