From: Alexey Dobriyan <adobriyan@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH v2] selftests/x86: add "ffff8" -- kernel memory scanner
Date: Tue, 1 Nov 2022 09:45:39 +0300 [thread overview]
Message-ID: <Y2DAk9zKYG9hT/Ov@p183> (raw)
In-Reply-To: <429982ba-e06f-e76b-061c-39db67558aa5@intel.com>
On Mon, Oct 31, 2022 at 02:37:43PM -0700, Dave Hansen wrote:
> On 10/29/22 10:25, Alexey Dobriyan wrote:
> >
> > $ ./ffff8_64 -h
> > usage: ./ffff8_64 [-f] [-r] [-n N] [-s S]
> > -f: sequential scan
> > -r: random scan (default)
> > -n: use N threads (default: $(nproc))
> > -s: lowest address shift (default: 47)
> > -t: time to run (default: 256 seconds)
>
> Does this mean that if someone is just running all kernel selftests,
> they need to wait for 256 seconds for this to finish?
Yes. But low time will cover negligible amount of address space.
Is there some kind of policy to not do this? LTP surely has similar
tests for races.
next prev parent reply other threads:[~2022-11-01 6:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 19:33 [PATCH] selftests/x86: add "ffff8" -- kernel memory scanner Alexey Dobriyan
2022-10-28 22:14 ` H. Peter Anvin
2022-10-29 9:55 ` Alexey Dobriyan
2022-10-29 17:25 ` [PATCH v2] " Alexey Dobriyan
2022-10-31 21:37 ` Dave Hansen
2022-11-01 6:45 ` Alexey Dobriyan [this message]
2022-11-01 7:04 ` Dave Hansen
2022-11-23 13:29 ` [PATCH v3] " Alexey Dobriyan
2022-10-29 2:14 ` [PATCH] " Bagas Sanjaya
2022-10-29 9:45 ` Alexey Dobriyan
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=Y2DAk9zKYG9hT/Ov@p183 \
--to=adobriyan@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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