linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Eduardo de Paula <me@carlosedp.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Changing SiFive Unleashed core clock rate on 5.x kernel
Date: Fri, 16 Aug 2019 18:44:00 -0300	[thread overview]
Message-ID: <CADnnUqfUMLhHviuooyi_msTtRCykyG10dSCERWieu1vzZOOH5w@mail.gmail.com> (raw)
In-Reply-To: <CADnnUqfakeD49FhGGJaUT9Jut16=wK1rrQcoaZXZuwdzkk-f3g@mail.gmail.com>

On Fri, Aug 16, 2019 at 6:17 PM Carlos Eduardo de Paula
<me@carlosedp.com> wrote:
>
> On Fri, Aug 16, 2019 at 5:57 PM Paul Walmsley <paul.walmsley@sifive.com> wrote:
> >
> > On Fri, 16 Aug 2019, Carlos Eduardo de Paula wrote:
> >
> > > Hi Paul
> >
> > Hi.  Just as an aside, kernel list etiquette usually disapproves of
> > top-posting.  Better to find out sooner rather than later, I guess...
> >
> > > I've built that 5.3 kernel and also used the DTs on my 5.2 Kernel but on
> > > both cases the network interface didn't come up.
> > >
> > > I used both defconfig and my own .config, after this I've built latest
> > > OpenSBI with the DT with command:
> > >
> > > make CROSS_COMPILE=riscv64-unknown-linux-gnu- \
> > >     PLATFORM=sifive/fu540 \
> > >     FW_PAYLOAD_PATH=../linux/arch/riscv/boot/Image \
> > >     FW_PAYLOAD_FDT_PATH=../linux/arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dtb
> > >
> > >
> > > Any adjustment I need?
> >
> > For v5.3-rc4, you'll probably need this patch:
> >
> > https://lore.kernel.org/linux-riscv/1563534631-15897-2-git-send-email-yash.shah@sifive.com/
> >
> > and you'll also need something like this for v5.2:
> >
> > https://lore.kernel.org/linux-riscv/1563534631-15897-3-git-send-email-yash.shah@sifive.com/
> >
> >
> > - Paul
>
> Thanks for the tip Paul and for being very helpful!
>
> I've applied the 5.3 patch you pointed and it worked!
>
> Thanks again!
>
> --
> ________________________________________
> Carlos Eduardo de Paula
> me@carlosedp.com
> http://carlosedp.com
> http://twitter.com/carlosedp
> Linkedin
> ________________________________________

BTW, here are some results with 1Ghz and 1.4Ghz using 7zip benchmark:

## With 1Ghz clock

7-Zip 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs LE)

LE
CPU Freq: 32000000 64000000 64000000 64000000 128000000 256000000
512000000 1024000000 2048000000

RAM size:    7973 MB,  # CPU hardware threads:   4
RAM usage:    882 MB,  # Benchmark threads:      4

                       Compressing  |                  Decompressing
Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
         KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS

22:       1333   297    437   1298  |      27862   398    597   2377
23:       1322   303    445   1347  |      27705   400    600   2397
24:       1301   306    457   1400  |      27273   399    601   2394
25:       1300   314    473   1484  |      26903   399    600   2394
----------------------------------  | ------------------------------
Avr:             305    453   1382  |              399    599   2391
Tot:             352    526   1886

## With 1.4Ghz Clock

7-Zip 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs LE)

LE
CPU Freq: 64000000 - 64000000 - 128000000 256000000 512000000
1024000000 2048000000

RAM size:    7973 MB,  # CPU hardware threads:   4
RAM usage:    882 MB,  # Benchmark threads:      4

                       Compressing  |                  Decompressing
Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
         KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS

22:       1805   307    573   1757  |      38545   399    823   3289
23:       1785   313    581   1819  |      37999   399    824   3288
24:       1583   288    592   1703  |      37377   399    823   3281
25:       1733   324    611   1979  |      36908   399    822   3285
----------------------------------  | ------------------------------
Avr:             308    589   1814  |              399    823   3286
Tot:             354    706   2550

Thanks!

-- 
________________________________________
Carlos Eduardo de Paula
me@carlosedp.com
http://carlosedp.com
http://twitter.com/carlosedp
Linkedin
________________________________________

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2019-08-16 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 20:32 Changing SiFive Unleashed core clock rate on 5.x kernel Carlos Eduardo de Paula
2019-08-13 21:22 ` Paul Walmsley
2019-08-14  2:09   ` Paul Walmsley
2019-08-16 18:59     ` Carlos Eduardo de Paula
2019-08-16 19:50       ` Paul Walmsley
2019-08-16 20:50         ` Carlos Eduardo de Paula
2019-08-16 20:57           ` Paul Walmsley
2019-08-16 21:17             ` Carlos Eduardo de Paula
2019-08-16 21:44               ` Carlos Eduardo de Paula [this message]

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=CADnnUqfUMLhHviuooyi_msTtRCykyG10dSCERWieu1vzZOOH5w@mail.gmail.com \
    --to=me@carlosedp.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.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 NNTP newsgroup(s).