Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] core-image-sato-sdk-ptest: Increase qemu memory to 1GB
Date: Fri, 01 Feb 2019 19:10:52 +0000	[thread overview]
Message-ID: <da60a762d6120336beae979ea45175a4b8ec6d70.camel@linuxfoundation.org> (raw)
In-Reply-To: <450c4826-18f3-d000-0995-f03c0bd05605@gmail.com>

On Fri, 2019-02-01 at 08:17 -0800, akuster808 wrote:
> 
> On 1/31/19 3:05 PM, Richard Purdie wrote:
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> >  meta/recipes-sato/images/core-image-sato-sdk-ptest.bb | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> > b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> > index 531571ee877..7e3152b4a11 100644
> > --- a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> > +++ b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> > @@ -9,3 +9,6 @@ IMAGE_FEATURES += "ptest-pkgs"
> >  # box) and explicitly add just 500MB.
> >  IMAGE_OVERHEAD_FACTOR = "1.0"
> >  IMAGE_ROOTFS_EXTRA_SPACE = "524288"
> > +
> > +# ptests need more memory than standard to avoid the OOM killer
> > +QB_MEM = "-m 1024"
> 
> Did we have an issue with mips not working with anything larger than
> 256? or am I miss remembering?

I think the runqemu code knows about that and limits anything that is
too large to work so this should be safe...

Cheers,

Richard



      reply	other threads:[~2019-02-01 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 23:05 [PATCH 1/2] core-image-sato-sdk-ptest: Increase qemu memory to 1GB Richard Purdie
2019-01-31 23:05 ` [PATCH 2/2] oeqa/runtime/ptest: Ensure OOM errors are logged Richard Purdie
2019-02-01 16:17 ` [PATCH 1/2] core-image-sato-sdk-ptest: Increase qemu memory to 1GB akuster808
2019-02-01 19:10   ` Richard Purdie [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=da60a762d6120336beae979ea45175a4b8ec6d70.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.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