mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Bobby Eshleman <bobbyeshleman@meta.com>,
	Stanislav Fomichev <sdf@fomichev.me>,
	Breno Leitao <leitao@debian.org>,
	thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: drv-net: devmem: Skip when hugetlbfs isn't supported
Date: Tue, 27 Oct 2026 14:15:55 -0700	[thread overview]
Message-ID: <20261027141555.47156425@kernel.org> (raw)
In-Reply-To: <ce8f0d43-0078-41e7-a5d2-cf31c6dc97fb@bootlin.com>

On Mon, 26 Oct 2026 10:38:50 +0100 Maxime Chevallier wrote:
> On 10/23/26 19:52, Jakub Kicinski wrote:
> > On Wed, 21 Oct 2026 11:08:51 +0200 Maxime Chevallier wrote:  
> >> The devmem selftest requires accessing /proc/sys/vm/nr_hugepages,
> >> which is only available when hugetlbfs is supported. This isn't the
> >> case on all CPU architectures, for example it isn't supported on ARM
> >> 32-bits on cores that don't support LPAE.
> >>
> >> On these devices, the devmem kselftest doesn't skip gracefully  
> > 
> > We don't require graceful skipping. If anything IMO hiding the stack
> > traces isn't great.
> > 
> > If the check is extraneous and makes us fail some tests which don't
> > actually require huge pages please make that clear in the commit
> > message. Otherwise the net benefit of the changes is unclear.  
> 
> hugetlbfs isn't required for devmem AFAICS, but the blamed commit
> moved the access to nr_hugepages before the actual "is devmem
> actually supported" test.
> 
> I don't expect the full test suite to gracefully run/skip for devmem
> on these arm32 platforms TBH, it's likely that devmem is only something
> that's been used on platforms that support hugetlbfs anyways, but
> strictly speaking both features are unrelated.

For max clarity I should have simply asked - does it make any test which
previously failed pass on any of your platforms? (incl. some WIP
patches that'd add devmem support) That's basically the criteria 
I think we should use.

  reply	other threads:[~2026-10-27 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  9:08 Maxime Chevallier
2026-10-21  9:47 ` Björn Töpel
2026-10-21 14:55 ` Stanislav Fomichev
2026-10-23 17:52 ` Jakub Kicinski
2026-10-26  9:38   ` Maxime Chevallier
2026-10-27 21:15     ` Jakub Kicinski [this message]
2026-10-28  7:17       ` Maxime Chevallier

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=20261027141555.47156425@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bobbyeshleman@meta.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=skhan@linuxfoundation.org \
    --cc=thomas.petazzoni@bootlin.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

all inboxes | Powered by JetHome®