Re: [RFC PATCH v5 00/10] KVM: selftests: some improvement and a new test for kvm page table

On 2021/3/23 23:58, Sean Christopherson wrote: On Tue, Mar 23, 2021, Yanan Wang wrote: Hi, This v5 series can mainly include two parts. Based on kvm queue branch: https://git.kernel.org/pub/scm/virt/kvm/kvm.git/log/?h=queue Given the number of Reviewed-by tags, I'm pretty sure you can drop t

Re: [PATCH] perf test: Change to use bash for daemon test

Hi Leo, On Sat, Mar 20, 2021 at 7:46 PM Leo Yan wrote: > > When executed the daemon test on Arm64 and x86 with Debian (Buster) > distro, both skip the test case with the log: > > # ./perf test -v 76 > 76: daemon operations

[PATCH v9 8/8] kselftests: Add test to check for rlimit changes in different user namespaces

pid, -child[i], WEXITSTATUS(wstatus[i])); + else if (WIFSIGNALED(wstatus[i])) + warnx("(pid=%d): pid %d killed by signal %d", + pid, -child[i], WTERMSIG(wstatus[i])); + + if (WIFSIGNALED(wstatus[i]) && WTERMSIG(wstatus[i]) == SIGUSR1) + continue; + + warnx("(pid=%d): Test failed", pid); + exit(EXIT_FAILURE); + } + + warnx("(pid=%d): Test passed", pid); + exit(EXIT_SUCCESS); +} -- 2.29.3

Re: [PATCH] perf test: Fix perf test 42

Em Mon, Mar 22, 2021 at 01:53:39PM +0100, Thomas Richter escreveu: > For some time now the perf test 42: BPF filter returns an error > on bpf relocation subtest, at least on x86 and s390. This is caused by > > commit d859900c4c56 ("bpf, libbpf: support global data/bss/rodata sect

Re: [RFC PATCH v5 00/10] KVM: selftests: some improvement and a new test for kvm page table

On Tue, Mar 23, 2021, Yanan Wang wrote: > Hi, > This v5 series can mainly include two parts. > Based on kvm queue branch: > https://git.kernel.org/pub/scm/virt/kvm/kvm.git/log/?h=queue Given the number of Reviewed-by tags, I'm pretty sure you can drop the "RFC" :-)

[RFC PATCH v5 10/10] KVM: selftests: Add a test for kvm page table code

This test serves as a performance tester and a bug reproducer for kvm page table code (GPA->HPA mappings), so it gives guidance for people trying to make some improvement for kvm. The function guest_code() can cover the conditions where a single vcpu or multiple vcpus access guest pages wit

[RFC PATCH v5 00/10] KVM: selftests: some improvement and a new test for kvm page table

e the accurate backing src granularity for kinds of alignment or guest memory accessing of vcpus. In the second part, a new test is added: This test is added to serve as a performance tester and a bug reproducer for kvm page table code (GPA->HPA mappings), it gives guidance for the people trying to m

Re: [PATCH] media: test-drivers: Remove duplicate include of string.h

Hi Wan, thanks for the patch! Unfortunately, however, a similar patch has already been accepted [1] [1] https://patchwork.linuxtv.org/project/linux-media/patch/20210306113255.217387-1-zhang.yun...@zte.com.cn/ -- thanks -- Daniel

[PATCH] media: test-drivers: Remove duplicate include of string.h

linux/string.h has been included at line 21, so remove the duplicate one at line 22. Signed-off-by: Wan Jiabing --- drivers/media/test-drivers/vidtv/vidtv_psi.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/media/test-drivers/vidtv/vidtv_psi.c b/drivers/media/test-drivers/vidtv

[PATCH 3/4] selftest/arm64/ptrace: add a test for orig_x0

The test creates two processes where one traces another one. The tracee executes a system call, the tracer traps it, changes orig_x0, triggers a signal and checks that the syscall is restarted with the setted argument. Test output: $ ./ptrace_restart_syscall_test 1..3 ok 1 orig_x0: 0x3 ok 2

[PATCH 4/4] selftest/arm64/ptrace: add a test for orig_x7

In system calls, x7 is used to indicate whether a tracee has been stopped on syscall-enter or syscall-exit and the origin value of x7 is saved in orig_x7. Test output: $ ./ptrace_syscall_test 1..4 ok 1 x7: 0 ok 2 x7: 1 ok 3 x7: 686920776f726c64 ok 4 The child exited with code 0. # Totals

[PATCH] perf test: Fix perf test 42

For some time now the perf test 42: BPF filter returns an error on bpf relocation subtest, at least on x86 and s390. This is caused by commit d859900c4c56 ("bpf, libbpf: support global data/bss/rodata sections") which introduces support for global variables in eBPF programs. At least

Re: [RFC PATCH v4 9/9] KVM: selftests: Add a test for kvm page table code

On 2021/3/12 22:20, Andrew Jones wrote: On Tue, Mar 02, 2021 at 08:57:51PM +0800, Yanan Wang wrote: This test serves as a performance tester and a bug reproducer for kvm page table code (GPA->HPA mappings), so it gives guidance for people trying to make some improvement for kvm. The funct

[PATCH V4 10/10] x86/pks: Add PKS test code

From: Ira Weiny The core PKS functionality provides an interface for kernel users to reserve keys to their domains set up the page tables with those keys and control access to those domains when needed. Define test code which exercises the core functionality of PKS via a debugfs entry. Basic

Re: [PATCH] proc: test subset=pid

On Sat, Mar 20, 2021 at 06:48:55PM +0300, Alexey Dobriyan wrote: > Test that /proc instance mounted with > > mount -t proc -o subset=pid > > contains only ".", "..", "self", "thread-self" and pid directories. > > Note: >

[PATCH] proc: test subset=pid

Test that /proc instance mounted with mount -t proc -o subset=pid contains only ".", "..", "self", "thread-self" and pid directories. Note: Currently "subset=pid" doesn't return "." and ".." via readdir. This mu

[rcu:rcu/test] BUILD SUCCESS 25577a0bbbd347ae3459f56a44ad4704f0fce723

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/test branch HEAD: 25577a0bbbd347ae3459f56a44ad4704f0fce723 Merge remote-tracking branch 'linus/master' into dev.2021.03.18a elapsed time: 726m configs tested: 103 configs skipped: 2 The followi

[PATCH] perf test: Change to use bash for daemon test

When executed the daemon test on Arm64 and x86 with Debian (Buster) distro, both skip the test case with the log: # ./perf test -v 76 76: daemon operations : --- start --- test child forked, pid 11687 test daemon list trap: SIGINT: bad

Re: [PATCH v1, RFC] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

On 16.03.21 18:56, Thorsten Leemhuis wrote: > On 15.03.21 21:20, Jonathan Corbet wrote: >> Thorsten Leemhuis writes: > >> Anything that could be done to >> make it more concise going forward would be more than welcome. > Yeah, will think about it, especially WRT to the other patch you looked > at

[PATCH v3 2/5] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

eport bugs, even if they can't test vanilla mainline kernel. Signed-off-by: Thorsten Leemhuis CC: Randy Dunlap --- With this I try to get rid of the last remaining parts that have a 'this needs discussion' box that's in the text. I hope I've found a middle ground that ever

Re: [PATCH-tip 0/5] locking/locktorture: Fix locktorture ww_mutex test problems

On 3/19/21 7:16 AM, Ingo Molnar wrote: * Waiman Long wrote: This is a follow-up patch series for the previous patchset on fixing locktorture ww_mutex test problem [1]. The first 3 patches of that series were merged into tip. It turns out that the last one of the three wasn't quite righ

[tip: locking/core] locking/locktorture: Fix false positive circular locking splat in ww_mutex test

Committer: Ingo Molnar CommitterDate: Fri, 19 Mar 2021 12:13:09 +01:00 locking/locktorture: Fix false positive circular locking splat in ww_mutex test In order to avoid false positive circular locking lockdep splat when runnng the ww_mutex torture test, we need to make sure that the ww_mutexes have

[tip: locking/core] locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex test

Committer: Ingo Molnar CommitterDate: Fri, 19 Mar 2021 12:13:10 +01:00 locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex test The ww_acquire_ctx structure for ww_mutex needs to persist for a complete lock/unlock cycle. In the ww_mutex test in locktorture, however, both

[PATCH 5.10 01/13] crypto: aesni - Use TEST %reg,%reg instead of CMP $0,%reg

From: Uros Bizjak [ Upstream commit 032d049ea0f45b45c21f3f02b542aa18bc6b6428 ] CMP $0,%reg can't set overflow flag, so we can use shorter TEST %reg,%reg instruction when only zero and sign flags are checked (E,L,LE,G,GE conditions). Signed-off-by: Uros Bizjak Cc: Herbert Xu Cc: Bor

[PATCH 5.4 15/18] crypto: aesni - Use TEST %reg,%reg instead of CMP $0,%reg

From: Uros Bizjak commit 032d049ea0f45b45c21f3f02b542aa18bc6b6428 upstream. CMP $0,%reg can't set overflow flag, so we can use shorter TEST %reg,%reg instruction when only zero and sign flags are checked (E,L,LE,G,GE conditions). Signed-off-by: Uros Bizjak Cc: Herbert Xu Cc: Borislav P

Re: [PATCH-tip 0/5] locking/locktorture: Fix locktorture ww_mutex test problems

* Waiman Long wrote: > This is a follow-up patch series for the previous patchset on fixing > locktorture ww_mutex test problem [1]. The first 3 patches of that > series were merged into tip. It turns out that the last one of the > three wasn't quite right. So this patch serie

Re: [PATCH-tip 0/5] locking/locktorture: Fix locktorture ww_mutex test problems

* Waiman Long wrote: > This is a follow-up patch series for the previous patchset on fixing > locktorture ww_mutex test problem [1]. The first 3 patches of that > series were merged into tip. It turns out that the last one of the > three wasn't quite right. So this patch serie

Re: [PATCH v2 2/2] selftests/kvm: add set_boot_cpu_id test

ic. > > > > > > + > > > + vm = create_vm(); > > > + > > > + if (is_bsp_vcpu1) > > > + vm_ioctl(vm, KVM_SET_BOOT_CPU_ID, (void *) VCPU_ID1); > > > > Does this ioctl need to be called before creating the vcpus? The > >

Re: [PATCH v2 2/2] selftests/kvm: add set_boot_cpu_id test

On 18/03/2021 17:20, Andrew Jones wrote: On Thu, Mar 18, 2021 at 04:16:24PM +0100, Emanuele Giuseppe Esposito wrote: Test for the KVM_SET_BOOT_CPU_ID ioctl. Check that it correctly allows to change the BSP vcpu. v1 -> v2: - remove unnecessary printf - move stage for loop inside run_v

[PATCH v3 2/2] perf test: Add CVS summary test

perf/tests/shell/stat+cvs_summary.sh b/tools/perf/tests/shell/stat+cvs_summary.sh new file mode 100755 index ..dd14f2ce7f6b --- /dev/null +++ b/tools/perf/tests/shell/stat+cvs_summary.sh @@ -0,0 +1,31 @@ +#!/bin/sh +# perf stat cvs summary test +# SPDX-License-Identifier: GPL-2.0

Re: [PATCH 5/5] selftests/seccomp: Add test for atomic addfd+send

On Thu, Mar 18, 2021 at 6:17 AM Sargun Dhillon wrote: > > This just adds a test to verify that when using the new introduced flag > to ADDFD, a valid fd is added and returned as the syscall result. > > Signed-off-by: Rodrigo Campos > Signed-off-by: Sargun Dhillon I think i

[PATCH-tip 0/5] locking/locktorture: Fix locktorture ww_mutex test problems

This is a follow-up patch series for the previous patchset on fixing locktorture ww_mutex test problem [1]. The first 3 patches of that series were merged into tip. It turns out that the last one of the three wasn't quite right. So this patch series revert the last patch. The rests of the

[PATCH-tip 5/5] locking/locktorture: locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex test

The ww_acquire_ctx structure for ww_mutex needs to persist for a complete lock/unlock cycle. In the ww_mutex test in locktorture, however, both ww_acquire_init() and ww_acquire_fini() are called within the lock function only. This causes a lockdep splat of "WARNING: Nested lock was not taken&

[PATCH-tip 2/5] locking/locktorture: Fix false positive circular locking splat in ww_mutex test

In order to avoid false positive circular locking lockdep splat when runnng the ww_mutex torture test, we need to make sure that the ww_mutexes have the same lock class as the acquire_ctx. This means the ww_mutexes must have the same lockdep key as the acquire_ctx. Unfortunately the current

Re: [PATCH v2 2/2] selftests/kvm: add set_boot_cpu_id test

On Thu, Mar 18, 2021 at 04:16:24PM +0100, Emanuele Giuseppe Esposito wrote: > Test for the KVM_SET_BOOT_CPU_ID ioctl. > Check that it correctly allows to change the BSP vcpu. > > v1 -> v2: > - remove unnecessary printf > - move stage for loop inside run_vcpu > -

[PATCH v2 2/2] selftests/kvm: add set_boot_cpu_id test

Test for the KVM_SET_BOOT_CPU_ID ioctl. Check that it correctly allows to change the BSP vcpu. v1 -> v2: - remove unnecessary printf - move stage for loop inside run_vcpu - test EBUSY when calling KVM_SET_BOOT_CPU_ID after vcpu creation and execution - introduce _vm_ioctl Signed-off

Re: [PATCH v2 1/3] perf test: Remove unused argument

Em Thu, Mar 18, 2021 at 02:01:49PM +0100, Jiri Olsa escreveu: > On Tue, Mar 16, 2021 at 05:55:03PM -0700, Ian Rogers wrote: > > Remove unused argument from daemon_exit. > > > > Signed-off-by: Ian Rogers > > for the patchset > > Acked-by: Jiri Olsa Thanks, added to the csets I had applied alre

Re: [PATCH v2 1/3] perf test: Remove unused argument

aemon_exit ${config} > > # check that sessions are gone > if [ -d "/proc/${pid_size}" ]; then > @@ -374,7 +373,7 @@ EOF > perf daemon signal --config ${config} > > # stop daemon > - daemon_exit ${base} ${config} > + daemon_exit $

Re: [PATCH v2 3/3] perf-test: add a test for perf-stat --bpf-counters option

> On Mar 17, 2021, at 11:07 PM, Namhyung Kim wrote: > > On Wed, Mar 17, 2021 at 6:18 AM Song Liu wrote: >> >> Add a test to compare the output of perf-stat with and without option >> --bpf-counters. If the difference is more than 10%, the test is considered >

Re: [PATCH v2 3/3] perf-test: add a test for perf-stat --bpf-counters option

On Wed, Mar 17, 2021 at 6:18 AM Song Liu wrote: > > Add a test to compare the output of perf-stat with and without option > --bpf-counters. If the difference is more than 10%, the test is considered > as failed. > > For stable results between two runs (w/ and w/o --bpf-c

[PATCH 3/5] selftests/seccomp: Add test for wait killable notifier

This adds a test for the positive case of the wait killable notifier, in testing that when the feature is activated the process acts as expected -- in not terminating on a non-fatal signal, and instead queueing it up. There is already a test case for normal handlers and preemption. Signed-off-by

[PATCH 5/5] selftests/seccomp: Add test for atomic addfd+send

This just adds a test to verify that when using the new introduced flag to ADDFD, a valid fd is added and returned as the syscall result. Signed-off-by: Rodrigo Campos Signed-off-by: Sargun Dhillon --- tools/testing/selftests/seccomp/seccomp_bpf.c | 38 +++ 1 file changed, 38

Re: [PATCH 4/4] locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex test

On 3/17/21 1:16 AM, Davidlohr Bueso wrote: On Tue, 16 Mar 2021, Waiman Long wrote: The ww_acquire_ctx structure for ww_mutex needs to persist for a complete lock/unlock cycle. In the ww_mutex test in locktorture, however, both ww_acquire_init() and ww_acquire_fini() are called within the lock

Re: [PATCH] selftests/kvm: add test for KVM_GET_MSR_FEATURE_INDEX_LIST

has nsmrs == 1, you are overwriting an u32 of the > > stack after struct kvm_msr_list.  You need to use your own struct > > similar to what is done with "buffer.header" and "buffer.entry". > > > > >   r = ioctl(kvm_fd, KVM_GET_MSRS, &buffer.heade

Re: [PATCH] selftests/kvm: add test for KVM_GET_MSR_FEATURE_INDEX_LIST

uot;KVM_GET_MSRS IOCTL failed,\n"   "  rc: %i errno: %i", r, errno); More in general, this is not a test, but rather a library function used to read a single MSR. If you would like to add a test for KVM_GET_MSR_FEATURE_INDEX_LIST that would be very welcome.  That would

[PATCH v1 5/5] selftests/vm: add test for MADV_POPULATE_(READ|WRITE)

Let's add a simple test for MADV_POPULATE_READ and MADV_POPULATE_WRITE, verifying some error handling, that population works, and that softdirty tracking works as expected. For now, limit the test to private anonymous memory. Cc: Andrew Morton Cc: Arnd Bergmann Cc: Michal Hocko Cc:

Re: [PATCH] selftests/kvm: add set_boot_cpu_id test

run_vm_bsp(VCPU_ID0); + run_vm_bsp(VCPU_ID1); + run_vm_bsp(VCPU_ID0); Looks good! Just another small change: since this third test is not adding much, you could instead invoke KVM_SET_BOOT_CPU_ID(VCPU_ID1) *after* the creation of the vCPUs instead of before. This should fail with -EBUSY, and vcpu 0 will remain the BSP. Paolo

Re: [PATCH] selftests/kvm: add test for KVM_GET_MSR_FEATURE_INDEX_LIST

SRS IOCTL failed,\n" " rc: %i errno: %i", r, errno); More in general, this is not a test, but rather a library function used to read a single MSR. If you would like to add a test for KVM_GET_MSR_FEATURE_INDEX_LIST that would be very welcome. That would be a

[PATCH] selftests/kvm: add test for KVM_GET_MSR_FEATURE_INDEX_LIST

Extend the kvm_get_feature_msr function to cover also KVM_GET_MSR_FEATURE_INDEX_LIST. Signed-off-by: Emanuele Giuseppe Esposito --- tools/testing/selftests/kvm/lib/x86_64/processor.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/tools/testing/selftests/kvm/lib/x86_64/processor.c b/

[PATCH] selftests/kvm: add set_boot_cpu_id test

Test for the KVM_SET_BOOT_CPU_ID ioctl. Check that it correctly allows to change the BSP vcpu. Signed-off-by: Emanuele Giuseppe Esposito --- tools/testing/selftests/kvm/.gitignore| 1 + tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/x86_64/set_boot_cpu_id.c

Re: [PATCH 4/4] locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex test

On Tue, 16 Mar 2021, Waiman Long wrote: The ww_acquire_ctx structure for ww_mutex needs to persist for a complete lock/unlock cycle. In the ww_mutex test in locktorture, however, both ww_acquire_init() and ww_acquire_fini() are called within the lock function only. This causes a lockdep splat

[PATCH v6 16/21] selftests/resctrl: Modularize resctrl test suite main() function

Resctrl test suite main() function does the following things 1. Parses command line arguments passed by user 2. Some setup checks 3. Logic that calls into each unit test 4. Print result and clean up after running each unit test Introduce wrapper functions for steps 3 and 4 to modularize the main

[PATCH v6 17/21] selftests/resctrl: Skip the test if requested resctrl feature is not supported

There could be two reasons why a resctrl feature might not be enabled on the platform 1. H/W might not support the feature 2. Even if the H/W supports it, the user might have disabled the feature through kernel command line arguments Hence, any resctrl unit test (like cmt, cat, mbm and mba

[PATCH v6 07/21] selftests/resctrl: Rename CQM test as CMT test

CMT (Cache Monitoring Technology) [1] is a H/W feature that reports cache occupancy of a process. resctrl selftest suite has a unit test to test CMT for LLC but the test is named as CQM (Cache Quality Monitoring). Furthermore, the unit test source file is named as cqm_test.c and several functions

[PATCH v6 08/21] selftests/resctrl: Call kselftest APIs to log test results

Call kselftest APIs instead of using printf() to log test results for cleaner code and better future extension. Suggested-by: Shuah Khan Tested-by: Babu Moger Signed-off-by: Fenghua Yu --- Change Log: v6: - Capitalize the first letter in printed msg (Babu). v5: - Add this patch (Shuah

[PATCH v2 1/3] perf test: Remove unused argument

rf.data for signals and 1 for perf record finished count=`ls ${base}/session-test/ | grep perf.data | wc -l` @@ -420,7 +419,7 @@ EOF fi # stop daemon - daemon_exit ${base} ${config} + daemon_exit ${config} rm -rf ${base} rm -f ${config} @@ -457,

[PATCH v2 2/3] perf test: Cleanup daemon if test is interrupted.

daemon --config ${config} -x: | head -1` - local pid=`echo "${line}" | awk 'BEGIN { FS = ":" } ; { print $1 }'` - - # stop daemon - perf daemon stop --config ${config} - - # ... and wait for the pid to go away - tail --pid=${pid} -f /dev/null -} - test_list() { echo "test daemon list" -- 2.31.0.rc2.261.g7f71774620-goog

[PATCH v2 3/3] perf test: Add 30s timeout for wait for daemon start.

Retry the ping loop upto 600 times, or approximately 30 seconds, to make sure the test does hang at start up. Signed-off-by: Ian Rogers --- tools/perf/tests/shell/daemon.sh | 7 +++ 1 file changed, 7 insertions(+) diff --git a/tools/perf/tests/shell/daemon.sh b/tools/perf/tests/shell

[PATCH v2 3/3] perf-test: add a test for perf-stat --bpf-counters option

Add a test to compare the output of perf-stat with and without option --bpf-counters. If the difference is more than 10%, the test is considered as failed. For stable results between two runs (w/ and w/o --bpf-counters), the test program should: 1) be long enough for better signal-noise-ratio; 2

[PATCH v12 05/10] ecdsa: Register NIST P384 and extend test suite

From: Saulo Alessandre Register NIST P384 as an akcipher and extend the testmgr with NIST P384-specific test vectors. Summary of changes: * crypto/ecdsa.c - add ecdsa_nist_p384_init_tfm - register and unregister P384 tfm * crypto/testmgr.c - add test vector for P384 on vector of tests

Re: [PATCH v1, RFC] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

lated sections to make them compatible and a bit clearer. >> At the same time make them less daunting: we want users to report bugs, >> even if they can't test vanilla mainline kernel. >> >> Signed-off-by: Thorsten Leemhuis >> CC: Randy Dunlap >> >> ---

[PATCH 4/4] locking/locktorture: Fix incorrect use of ww_acquire_ctx in ww_mutex test

The ww_acquire_ctx structure for ww_mutex needs to persist for a complete lock/unlock cycle. In the ww_mutex test in locktorture, however, both ww_acquire_init() and ww_acquire_fini() are called within the lock function only. This causes a lockdep splat of "WARNING: Nested lock was not taken&

[PATCH 0/4] locking/ww_mutex: Fix locktorture ww_mutex test problems

It was found that lockdep splat was produced whenever the ww_mutex locktorture test was run on a kernel with lockdep enabled. It turns out that there are bugs both in the ww_mutex and the locktorture code. This patch series fix these bugs so that the ww_mutex locktorture test is able to run

TEST EMAIL - PLEASE IGNORE

On 15/3/2021 5:44 pm, Rahul Tanwar wrote: > From: Arnd Bergmann > To: Pavel Machek, > Amireddy Mallikarjuna reddy > > Cc: Arnd Bergmann, Dan Murphy, > linux-l...@vger.kernel.org,linux-kernel@vger.kernel.org > Subject:[PATCH] leds: lgm: fix gpiolib dependency >

[PATCH v7 6/6] selftest/x86/signal: Include test cases for validating sigaltstack

The test measures the kernel's signal delivery with different (enough vs. insufficient) stack sizes. Signed-off-by: Chang S. Bae Reviewed-by: Len Brown Cc: x...@kernel.org Cc: linux-kselft...@vger.kernel.org Cc: linux-kernel@vger.kernel.org --- Changes from v3: * Revised test messages

Re: [PATCH v1, RFC] docs: reporting-issues.rst: tone down 'test vanilla mainline' a little

the same time make them less daunting: we want users to report bugs, > even if they can't test vanilla mainline kernel. > > Signed-off-by: Thorsten Leemhuis > CC: Randy Dunlap > > --- > With this I try to get rid of the last remaining parts that have a > 'this need

Re: [PATCH v6 08/10] perf: arm64: Add test for userspace counter access on heterogeneous systems

On Wed, Mar 10, 2021 at 05:08:35PM -0700, Rob Herring wrote: > Userspace counter access only works on heterogeneous systems with some > restrictions. The userspace process must be pinned to a homogeneous > subset of CPUs and must open the corresponding PMU for those CPUs. This > commit

[PATCH 4.19 030/120] net: stmmac: fix watchdog timeout during suspend/resume stress test

From: Greg Kroah-Hartman From: Joakim Zhang commit c511819d138de38e1637eedb645c207e09680d0f upstream. stmmac_xmit() call stmmac_tx_timer_arm() at the end to modify tx timer to do the transmission cleanup work. Imagine such a situation, stmmac enters suspend immediately after tx timer modified,

[PATCH 5.10 159/290] kasan: fix memory corruption in kasan_bitops_tags test

From: Greg Kroah-Hartman From: Andrey Konovalov [ Upstream commit e66e1799a76621003e5b04c9c057826a2152e103 ] Since the hardware tag-based KASAN mode might not have a redzone that comes after an allocated object (when kasan.mode=prod is enabled), the kasan_bitops_tags() test ends up corrupting

[PATCH 5.11 156/306] kasan: fix memory corruption in kasan_bitops_tags test

From: Greg Kroah-Hartman From: Andrey Konovalov [ Upstream commit e66e1799a76621003e5b04c9c057826a2152e103 ] Since the hardware tag-based KASAN mode might not have a redzone that comes after an allocated object (when kasan.mode=prod is enabled), the kasan_bitops_tags() test ends up corrupting

[PATCH 5.11 081/306] net: stmmac: fix watchdog timeout during suspend/resume stress test

From: Greg Kroah-Hartman From: Joakim Zhang commit c511819d138de38e1637eedb645c207e09680d0f upstream. stmmac_xmit() call stmmac_tx_timer_arm() at the end to modify tx timer to do the transmission cleanup work. Imagine such a situation, stmmac enters suspend immediately after tx timer modified,

[PATCH 5.10 067/290] net: stmmac: fix watchdog timeout during suspend/resume stress test

From: Greg Kroah-Hartman From: Joakim Zhang commit c511819d138de38e1637eedb645c207e09680d0f upstream. stmmac_xmit() call stmmac_tx_timer_arm() at the end to modify tx timer to do the transmission cleanup work. Imagine such a situation, stmmac enters suspend immediately after tx timer modified,

[PATCH 5.4 040/168] net: stmmac: fix watchdog timeout during suspend/resume stress test

From: Greg Kroah-Hartman From: Joakim Zhang commit c511819d138de38e1637eedb645c207e09680d0f upstream. stmmac_xmit() call stmmac_tx_timer_arm() at the end to modify tx timer to do the transmission cleanup work. Imagine such a situation, stmmac enters suspend immediately after tx timer modified,

[PATCH v5 11/11] selftests: gpio: add test cases for gpio-sim

From: Bartosz Golaszewski Add a set of tests for the new gpio-sim module. This is a pure shell test-suite and uses the helper programs available in the gpio selftests directory. These test-cases only test the functionalities exposed by the gpio-sim driver, not those handled by core gpiolib code

[linux-stable-rc CI] Test report for 4.14.226-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.14.y Arch: x86 Version: 4.14.226-rc1 Commit: 21dddc147970ed44c54e95c59aa4c9d95683733d Compiler: gcc version 7.3.0 (GCC) All t

[linux-stable-rc CI] Test report for 5.4.106-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.4.y Arch: x86 Version: 5.4.106-rc1 Commit: 2bcbae06b8fb9030973ee996e1b8ed43f3bfd4ab Compiler: gcc version 7.3.0 (GCC) All tes

[linux-stable-rc CI] Test report for 5.10.24-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.10.y Arch: arm64 Version: 5.10.24-rc1 Commit: 7496dbd02b27316275e097a4e52cebcd2ca5a5c0 Compiler: gcc version 7.3.0 (GCC) Fail

[linux-stable-rc CI] Test report for 5.10.24-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.10.y Arch: x86 Version: 5.10.24-rc1 Commit: 7496dbd02b27316275e097a4e52cebcd2ca5a5c0 Compiler: gcc version 7.3.0 (GCC) All te

[linux-stable-rc CI] Test report for 4.19.181-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Arch: arm64 Version: 4.19.181-rc1 Commit: a233c6b3f6de88ca62da8fde45f330b104827851 Compiler: gcc version 7.3.0 (GCC) All

[linux-stable-rc CI] Test report for 5.4.106-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.4.y Arch: arm64 Version: 5.4.106-rc1 Commit: 2bcbae06b8fb9030973ee996e1b8ed43f3bfd4ab Compiler: gcc version 7.3.0 (GCC) All t

[linux-stable-rc CI] Test report for 4.19.181-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Arch: x86 Version: 4.19.181-rc1 Commit: a233c6b3f6de88ca62da8fde45f330b104827851 Compiler: gcc version 7.3.0 (GCC) All t

[linux-stable-rc CI] Test report for 4.19.181-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Arch: arm64 Version: 4.19.181-rc1 Commit: 21889d805d10fd6fc2202417881b6e909a47121e Compiler: gcc version 7.3.0 (GCC) Fai

[linux-stable-rc CI] Test report for 5.4.106-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.4.y Arch: x86 Version: 5.4.106-rc1 Commit: e8e77f614b2e2ba579aa4ff7c507026bd86dac64 Compiler: gcc version 7.3.0 (GCC) All tes

[linux-stable-rc CI] Test report for 5.10.24-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.10.y Arch: arm64 Version: 5.10.24-rc1 Commit: e725551e82d7dce92673b0bef6430fc8e903fb72 Compiler: gcc version 7.3.0 (GCC) Fail

[linux-stable-rc CI] Test report for 5.10.24-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.10.y Arch: x86 Version: 5.10.24-rc1 Commit: e725551e82d7dce92673b0bef6430fc8e903fb72 Compiler: gcc version 7.3.0 (GCC) Failed

[linux-stable-rc CI] Test report for 5.4.106-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.4.y Arch: arm64 Version: 5.4.106-rc1 Commit: e8e77f614b2e2ba579aa4ff7c507026bd86dac64 Compiler: gcc version 7.3.0 (GCC) All t

[linux-stable-rc CI] Test report for 4.19.181-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Arch: x86 Version: 4.19.181-rc1 Commit: c292b9ded226bc1afca7093e3714798129cdce3b Compiler: gcc version 7.3.0 (GCC) All t

Re: [PATCH v5 08/21] selftests/resctrl: Call kselftest APIs to log test results

Hi, Babu, On Fri, Mar 12, 2021 at 01:12:35PM -0600, Babu Moger wrote: > > - printf("# dmesg: %s", line); > > + ksft_print_msg("dmesg: %s", line); > > if (strstr(line, "resctrl:")) > > - printf("# dmesg: %s", line); > > +

[linux-stable-rc CI] Test report for 4.19.181-rc1 /arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Arch: arm64 Version: 4.19.181-rc1 Commit: c292b9ded226bc1afca7093e3714798129cdce3b Compiler: gcc version 7.3.0 (GCC) All

[linux-stable-rc CI] Test report for 4.19.181-rc1 /x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.19.y Arch: x86 Version: 4.19.181-rc1 Commit: cf7e1fa20d45200b0dad0a561975f501373581bd Compiler: gcc version 7.3.0 (GCC) Faile

RE: [PATCH v5 08/21] selftests/resctrl: Call kselftest APIs to log test results

esctrl: Call kselftest APIs to log test > results > > Call kselftest APIs instead of using printf() to log test results > for cleaner code and better future extension. > > Suggested-by: Shuah Khan > Signed-off-by: Fenghua Yu > --- > Change Log: > v5: > -

RE: [PATCH v5 07/21] selftests/resctrl: Rename CQM test as CMT test

> -Original Message- > From: Fenghua Yu > Sent: Sunday, March 7, 2021 8:55 AM > To: Shuah Khan ; Tony Luck ; > Reinette Chatre ; Moger, Babu > > Cc: linux-kselftest ; linux-kernel ker...@vger.kernel.org>; Fenghua Yu > Subject: [PATCH v5 07/21] selftests/

[PATCH 23/23] ASoC: tscs454: remove useless test on PLL disable

+* identical zero vzalues, there is no need to test +* the PLL index +*/ + val = FV_PLL1CLKEN_DISABLE; ret = snd_soc_component_update_bits(component, R_PLLCTL, msk, val); if (ret < 0) { -- 2.25.1

Re: [RFC PATCH v4 9/9] KVM: selftests: Add a test for kvm page table code

On Tue, Mar 02, 2021 at 08:57:51PM +0800, Yanan Wang wrote: > This test serves as a performance tester and a bug reproducer for > kvm page table code (GPA->HPA mappings), so it gives guidance for > people trying to make some improvement for kvm. > > The function guest_co

[linux-stable-rc CI] Test report for linux-5.4.y/arm64

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-5.4.y Arch: arm64 Version: 5.4.106-rc1+ Commit: ddc6c64e1db1aa383fe8e2317dc04e46994cc1a7 Compiler: gcc version 7.3.0 (GCC) All

[linux-stable-rc CI] Test report for linux-4.14.y/x86

Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git Branch: linux-4.14.y Arch: x86 Version: 4.14.226-rc1+ Commit: ac6e3f484ce66973debf20d6f035ba453f804c1a Compiler: gcc version 7.3.0 (GCC) All

[PATCH v4 11/11] selftests: gpio: add test cases for gpio-sim

From: Bartosz Golaszewski Add a set of tests for the new gpio-sim module. This is a pure shell test-suite and uses the helper programs available in the gpio selftests directory. These test-cases only test the functionalities exposed by the gpio-sim driver, not those handled by core gpiolib code

Re: [RFC PATCH v4 0/9] KVM: selftests: some improvement and a new test for kvm page table

ty of different backing src types(anonumous/thp/hugetlb) is added, so that we can use the accurate backing src granularity for kinds of alignment or guest memory accessing of vcpus. In the second part, a new test is added: This test is added to serve as a performance tester and a bug reproducer fo

Re: [PATCH 2/3] perf test: Cleanup daemon if test is interrupted.

On Thu, Mar 11, 2021 at 08:18:27AM -0800, Ian Rogers wrote: > On Thu, Mar 11, 2021 at 2:38 AM Jiri Olsa wrote: > > > > On Wed, Mar 10, 2021 at 12:41:17PM -0800, Ian Rogers wrote: > > > Reorder daemon_start and daemon_exit as the trap handler is added in > > > daemon_start referencing daemon_exit.

Re: [PATCH 2/3] perf test: Cleanup daemon if test is interrupted.

eferences? Ian > thanks, > jirka > > > + > > # wait for the session to ping > > local state="FAIL" > > while [ "${state}" != "OK" ]; do > > @@ -113,20 +133,6 @@ daemon_start() > > done > > } > >

<    2   3   4   5   6   7   8   9   10   11   >