From: Mark Brown <broonie@kernel.org>
To: Song Liu <song@kernel.org>
Cc: Puranjay Mohan <puranjay12@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Alexei Starovoitov <ast@kernel.org>,
Will Deacon <will@kernel.org>,
kernelci-results@groups.io, bot@kernelci.org,
linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
bpf@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: next/master bisection: baseline.login on qemu_arm64-virt-gicv3-uefi
Date: Thu, 7 Mar 2024 18:34:02 +0000 [thread overview]
Message-ID: <4ce67bde-3bd4-4a59-bce7-4a2764445783@sirena.org.uk> (raw)
In-Reply-To: <CAPhsuW7c+OgFcZ9qWF7nes3SbaQdf5GYZZA+jyHAOzJ5omuZ8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On Thu, Mar 07, 2024 at 10:16:21AM -0800, Song Liu wrote:
> On Thu, Mar 7, 2024 at 8:36 AM Mark Brown <broonie@kernel.org> wrote:
> > The KernelCI bisection bot found a boot regression n today's -next on
> > qemu arm64 UEFI platforms with 64K pages which was bisected to commit
> > 1dad391daef1 ("bpf, arm64: use bpf_prog_pack for memory management").
> > We OOM quite early in boot:
> IIUC, 64kB pages means 512MB PMD. I think that's indeed too big. We
> will need some logic to limit such cases.
These qemu instances are only configured with 1G of RAM so that's rather
large indeed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-03-07 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65e9e748.a70a0220.606f7.53c0@mx.google.com>
2024-03-07 16:36 ` next/master bisection: baseline.login on qemu_arm64-virt-gicv3-uefi Mark Brown
2024-03-07 18:16 ` Song Liu
2024-03-07 18:34 ` Mark Brown [this message]
2024-03-07 19:02 ` Puranjay Mohan
2024-03-07 23:00 ` Song Liu
2024-03-08 12:12 ` Puranjay Mohan
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=4ce67bde-3bd4-4a59-bce7-4a2764445783@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ast@kernel.org \
--cc=bot@kernelci.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=song@kernel.org \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).