From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "Yu, Mingli" <mingli.yu@eng.windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] qemuppc64: Set the default memory to 512M
Date: Thu, 3 Aug 2023 12:46:19 +0800 [thread overview]
Message-ID: <047729f7-53dd-e37f-f537-465fd0591958@windriver.com> (raw)
In-Reply-To: <CANNYZj_9iqUYACMUmXYLdJyHpZowjawTeGpPY7g+71AUQSDdew@mail.gmail.com>
On 8/2/23 16:32, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Wed, 2 Aug 2023 at 10:30, Yu, Mingli <mingli.yu@windriver.com> wrote:
>> Did a simple check against core-image-full-cmdline with qemuppc64 just
>> now and it can boot successfully with the default 256M memory.
>>
>> But it failed to boot with my customized image as the attached
>> messages(/var/log/messages). If not change the default memory, how to
>> resolve the OOM issue? Any hints?
>
> You can set QB_MEM directly in the recipe of the customized image?
> Oe-core does this in several images which have specific requirements
> for larger RAM amounts (e.g. test images where the tests require it).
> You can grep meta/ for examples.
>
Thanks for the hints! I will have a try.
Thanks,
> Alex
prev parent reply other threads:[~2023-08-03 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:48 [PATCH] qemuppc64: Set the default memory to 512M mingli.yu
2023-08-01 10:13 ` [OE-core] " Alexander Kanavin
2023-08-02 8:30 ` Yu, Mingli
2023-08-02 8:32 ` Alexander Kanavin
2023-08-03 4:46 ` Yu, Mingli [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=047729f7-53dd-e37f-f537-465fd0591958@windriver.com \
--to=mingli.yu@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=mingli.yu@eng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox