All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] qemumips: Use 34Kf CPU emulation
Date: Wed, 29 Jul 2020 10:58:24 -0700	[thread overview]
Message-ID: <CAMKF1spTG7P72GKL9hZF-RkPRKyZ4557KeQidMLVCrnGKFw_sA@mail.gmail.com> (raw)
In-Reply-To: <e3b4f4fd4a29514b30cd8f170d5a518acff0fa02.camel@linuxfoundation.org>

On Wed, Jul 29, 2020 at 3:13 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Wed, 2020-07-29 at 10:56 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Tue, 2020-07-28 at 19:28 -0700, Khem Raj wrote:
> > > Few years ago we switched to using mips32r2 tunings for qemumips
> > > however
> > > the default CPU emulation still remained 24Kf which is not optimal
> > > for
> > > mips32r2 ISA for qemu [1], therefore switch to recommended 32Kf for
> > > CPU
> > > emulation when running qemu in system mode
> > >
> > > Boot time to console is ~1s faster with this setting, hopefully
> > > this
> > > should speed up qemumips in general
> > >
> > > [1]
> > > https://www.qemu.org/docs/master/system/target-mips.html#preferred-cpu-models-for-mips-hosts
> > >
> > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > > ---
> > >  meta/conf/machine/qemumips.conf | 2 ++
> > >  1 file changed, 2 insertions(+)
> > >
> > > diff --git a/meta/conf/machine/qemumips.conf
> > > b/meta/conf/machine/qemumips.conf
> > > index 31ad754483..4617c3c7b6 100644
> > > --- a/meta/conf/machine/qemumips.conf
> > > +++ b/meta/conf/machine/qemumips.conf
> > > @@ -12,3 +12,5 @@ KERNEL_ALT_IMAGETYPE = "vmlinux.bin"
> > >  SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyS1"
> > >
> > >  QB_SYSTEM_NAME = "qemu-system-mips"
> > > +
> > > +QB_CPU = "-cpu 34Kf"
> >
> > Thanks!
> >
> > I did run some tests locally, timing core-image-sato -c testimage
> > before and after this change. It took 999s before, 1018s after but
> > the difference looks like noise rather than any speedup or slowdown.
>
> Another try at "after" got 986s so who knows :)
>

Yeah I saw that first boot was slower but reboots were always 1s
faster, but hopefully it
will help with irregular timeouts on tests which is what we are looking for.

> Cheers,
>
> Richard
>

      reply	other threads:[~2020-07-29 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29  2:28 [PATCH] qemumips: Use 34Kf CPU emulation Khem Raj
2020-07-29  9:56 ` [OE-core] " Richard Purdie
     [not found] ` <162630A032FCBA1C.9067@lists.openembedded.org>
2020-07-29 10:13   ` Richard Purdie
2020-07-29 17:58     ` Khem Raj [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=CAMKF1spTG7P72GKL9hZF-RkPRKyZ4557KeQidMLVCrnGKFw_sA@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.