All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Changqing Li <changqing.li@windriver.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] core-image-sato-sdk-ptest: use 3G of RAM
Date: Tue, 26 Jan 2021 08:20:34 +0000	[thread overview]
Message-ID: <5e3acf487208372321ba28aec286fdb7fef7e6bf.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210126053605.2003-1-changqing.li@windriver.com>

On Tue, 2021-01-26 at 13:36 +0800, Changqing Li wrote:
> [YOCTO #14164]
> 
> Some ptest cases, for example, libinput ptest intermittent failure on
> arm64, this should caused by OOM Killer.
> 
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
>  meta/recipes-sato/images/core-image-sato-sdk-ptest.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> 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 bf749acd79..b3ce859d76 100644
> --- a/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> +++ b/meta/recipes-sato/images/core-image-sato-sdk-ptest.bb
> @@ -17,7 +17,7 @@ IMAGE_ROOTFS_EXTRA_SPACE = "1124288"
>  
> 
> 
> 
>  # ptests need more memory than standard to avoid the OOM killer
>  # also lttng-tools needs /tmp that has at least 1G
> -QB_MEM = "-m 2048"
> +QB_MEM = "-m 3072"
> 

What is libinput doing that needs 3GB of memory? Is this because its
loading a whole graphics stack for testing or something? It seems odd
that we need that much memory for input drivers!

Cheers,

Richard



      reply	other threads:[~2021-01-26  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  5:36 [PATCH] core-image-sato-sdk-ptest: use 3G of RAM Changqing Li
2021-01-26  8:20 ` 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=5e3acf487208372321ba28aec286fdb7fef7e6bf.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=changqing.li@windriver.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 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.