From: linuxtestproject.agent@gmail.com
To: Pavithra <pavrampu@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Fix hugeshmat05 test failure on lpar with 1GB hugepages.
Date: Mon, 20 Apr 2026 10:53:42 +0000 [thread overview]
Message-ID: <20260420105342.3941-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260420102339.729745-1-pavrampu@linux.ibm.com>
Hi Pavithra,
On Mon, 20 Apr 2026, Pavithra wrote:
> Fix hugeshmat05 test failure on lpar with 1GB hugepages.
>
> Modified the test to detect large hugepage sizes (≥1GB) and adjust test sizes accordingly.
The commit body describes what changed but not why the test was failing.
Is shmget failing because N*hpage_size=4GB exceeds what the LPAR can
allocate in one call, or is it a pool exhaustion issue? Please document
the root cause in the commit message.
> + if (hpage_size >= 1024 * 1024 * 1024)
> + multiplier = N / 2;
> + else
> + multiplier = N;
With multiplier=2 for 1GB pages the test needs at most 2 hugepages at
peak, but .hugepages = {N+1, TST_NEEDS} still requires 5 free 1GB pages
(5 GB). On an LPAR with 2–4 free 1GB hugepages the test still cannot
run. Update .hugepages to match the reduced requirement.
---
Note:
Our agent completed the review of the patch. The agent can sometimes
produce false positives although often its findings are genuine. If you
find issues with the review, please comment this email or ignore the
suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-04-20 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 10:23 [LTP] [PATCH] Fix hugeshmat05 test failure on lpar with 1GB hugepages Pavithra
2026-04-20 10:53 ` linuxtestproject.agent [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=20260420105342.3941-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=pavrampu@linux.ibm.com \
/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