public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zong Li <zong.li@sifive.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Darius Rad <darius@bluespec.com>,
	Andrew Waterman <andrew@sifive.com>,
	dj@redhat.com,  joseph@codesourcery.com, schwab@suse.de,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] riscv: Get level 3 cache's information
Date: Wed, 9 Nov 2022 09:12:59 +0800	[thread overview]
Message-ID: <CANXhq0q8_YRjRe+1RyLHSCptR=awfC4DH6xu+2kvORVc-Ezo8A@mail.gmail.com> (raw)
In-Reply-To: <mhng-1583e9a6-5bd1-47a4-8135-e6bc9ee772a7@palmer-ri-x1c9a>

On Wed, Nov 2, 2022 at 10:19 AM Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> On Tue, 01 Nov 2022 18:58:46 PDT (-0700), zong.li@sifive.com wrote:
> > On Fri, Oct 21, 2022 at 3:28 PM Zong Li <zong.li@sifive.com> wrote:
> >>
> >> On Fri, Oct 21, 2022 at 3:23 PM Zong Li <zong.li@sifive.com> wrote:
> >> >
> >> > RISC-V architecture extends the cache information for level 3 cache
> >> > in AUX vector in Linux v.6.1-rc1. This patch supports sysconf to get
> >> > the level 3 cache information.
> >> > ---
> >> >  sysdeps/unix/sysv/linux/riscv/sysconf.c | 7 +++++++
> >> >  1 file changed, 7 insertions(+)
> >> >
> >> > diff --git a/sysdeps/unix/sysv/linux/riscv/sysconf.c b/sysdeps/unix/sysv/linux/riscv/sysconf.c
> >> > index b768ebf781..4772a9fc11 100644
> >> > --- a/sysdeps/unix/sysv/linux/riscv/sysconf.c
> >> > +++ b/sysdeps/unix/sysv/linux/riscv/sysconf.c
> >> > @@ -90,6 +90,13 @@ __sysconf (int name)
> >> >         return sysconf_get_cache_associativity (AT_L2_CACHEGEOMETRY);
> >> >        case _SC_LEVEL2_CACHE_LINESIZE:
> >> >         return sysconf_get_cache_linesize (AT_L2_CACHEGEOMETRY);
> >> > +      case _SC_LEVEL3_CACHE_SIZE:
> >> > +       return sysconf_get_cache_size (AT_L3_CACHESIZE);
> >> > +      case _SC_LEVEL3_CACHE_ASSOC:
> >> > +       return sysconf_get_cache_associativity (AT_L3_CACHEGEOMETRY);
> >> > +      case _SC_LEVEL3_CACHE_LINESIZE:
> >> > +       return sysconf_get_cache_linesize (AT_L3_CACHEGEOMETRY);
> >> > +
> >> >        default:
> >> >         return linux_sysconf (name);
> >> >      }
> >> > --
> >> > 2.17.1
> >> >
> >
> > Hi all,
> > Because I didn't get any feedback here, could I know whether this
> > patch is good for all? Are you all willing to help me to pick it up if
> > it looks good to you? Thanks a lot :)
>
> Sorry, for some reason I thought I'd replied to this one.
>
> Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> Thanks!

Hi Palmer, thanks a lot for your review. May I ask who might help me
to pick up this patch? I couldn't find this patch in master yet.

>
> >> Sorry for missing libc-alpha. Add libc-alpha in this loop.

  reply	other threads:[~2022-11-09  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221021072311.26918-1-zong.li@sifive.com>
2022-10-21  7:28 ` Zong Li
2022-11-02  1:58   ` Zong Li
2022-11-02  2:19     ` Palmer Dabbelt
2022-11-09  1:12       ` Zong Li [this message]
2022-11-09 14:42         ` Adhemerval Zanella Netto
2022-11-09 21:11           ` Palmer Dabbelt

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='CANXhq0q8_YRjRe+1RyLHSCptR=awfC4DH6xu+2kvORVc-Ezo8A@mail.gmail.com' \
    --to=zong.li@sifive.com \
    --cc=andrew@sifive.com \
    --cc=darius@bluespec.com \
    --cc=dj@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@rivosinc.com \
    --cc=schwab@suse.de \
    /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).