From: Andrew Morton <akpm@linux-foundation.org>
To: Shuah Khan <shuah.kh@samsung.com>
Cc: gregkh@linuxfoundation.org, keescook@chromium.org,
michael@ellerman.id.au, benh@kernel.crashing.org,
fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 linux-next] tools: selftests - create a separate hotplug target for full range test
Date: Tue, 8 Jul 2014 15:31:12 -0700 [thread overview]
Message-ID: <20140708153112.494e5f769f9ae9184fad66cd@linux-foundation.org> (raw)
In-Reply-To: <1404316298-8870-1-git-send-email-shuah.kh@samsung.com>
On Wed, 2 Jul 2014 09:51:38 -0600 Shuah Khan <shuah.kh@samsung.com> wrote:
> On some systems, hot-plug tests could hang forever waiting for cpu and
> memory to be ready to be offlined. A special hot-plug target is created
> to run full range of hot-plug tests. In default mode, hot-plug tests run
> in safe mode with a limited scope. In limited mode, cpu-hotplug test is
> run on a single cpu as opposed to all hotplug capable cpus, and memory
> hotplug test is run on 2% of hotplug capable memory instead of 10%. In
> addition to the above change, cpu-hotplug is chnged to change processor
> affinity to cpu 0 so it doesn't impact itself while the test runs.
>
> ...
>
> --- a/tools/testing/selftests/README.txt
> +++ b/tools/testing/selftests/README.txt
> @@ -4,8 +4,15 @@ The kernel contains a set of "self tests" under the tools/testing/selftests/
> directory. These are intended to be small unit tests to exercise individual
> code paths in the kernel.
>
> -Running the selftests
> -=====================
> +On some systems, hot-plug tests could hang forever waiting for cpu and
> +memory to be ready to be offlined. A special hot-plug target is created
> +to run full range of hot-plug tests. In default mode, hot-plug tests run
> +in safe mode with a limited scope. In limited mode, cpu-hotplug test is
> +run on a single cpu as opposed to all hotplug capable cpus, and memory
> +hotplug test is run on 2% of hotplug capable memory instead of 10%.
> +
> +Running the selftests (hotplug tests are run in limited mode)
> +=============================================================
>
> To build the tests:
>
> @@ -18,14 +25,26 @@ To run the tests:
>
> - note that some tests will require root privileges.
>
> -
> -To run only tests targetted for a single subsystem:
> +To run only tests targeted for a single subsystem: (including
> +hotplug targets in limited mode)
>
> $ make -C tools/testing/selftests TARGETS=cpu-hotplug run_tests
>
> See the top-level tools/testing/selftests/Makefile for the list of all possible
> targets.
>
> +Running the full range hotplug selftests
> +========================================
> +
> +To build the tests:
> +
> + $ make -C tools/testing/selftests hotplug
Well. `make -C tools/testing/selftests' will build the hotplug tests,
won't it? We may as well *compile* everything by default..
>
> ...
>
prev parent reply other threads:[~2014-07-08 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 15:51 Shuah Khan
2014-07-08 22:31 ` Andrew Morton [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=20140708153112.494e5f769f9ae9184fad66cd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=shuah.kh@samsung.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®