From: Alexey Dobriyan <adobriyan@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] selftests/x86: add "ffff8" -- kernel memory scanner
Date: Sat, 29 Oct 2022 12:45:19 +0300 [thread overview]
Message-ID: <Y1z2L8aAq7sOWxQT@p183> (raw)
In-Reply-To: <Y1yMlEqtiQwUoy9m@debian.me>
On Sat, Oct 29, 2022 at 09:14:44AM +0700, Bagas Sanjaya wrote:
> On Fri, Oct 28, 2022 at 10:33:49PM +0300, Alexey Dobriyan wrote:
> >
> > I've tested it with kernel patch which installs rogue page and it was found.
> >
> > $ ./a.out -h
> > usage: ./a.out [-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)
> >
> > Intended usages are:
> >
> > $ ./a.out -f # full scan on all cores
> > or
> > $ ./a.out -r -t ... # time limited random scan for QA test
> >
>
> The executable name is a.out, really?
This is copypasta from my internal git.
It will be named ffff8_64 by the build system.
prev parent reply other threads:[~2022-10-29 9: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
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 [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=Y1z2L8aAq7sOWxQT@p183 \
--to=adobriyan@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.