Newer 32-bit architectures e.g. riscv32 are using 64-bit time_t
from get go, they have not wired __NR_clock_adjtime at all
valid-adjtimex testcase fails to compile on such architectures.
if this condition is found then use 64-bit adjtime syscall
Signed-off-by: Khem Raj
Cc: John Stultz
Cc: Shuah
We recently notice that the step_after_suspend_test would
fail on our plenty devices. The test believesit failed to
enter suspend state with
$ sudo ./step_after_suspend_test
TAP version 13
Bail out! Failed to enter Suspend state
However, in the kernel message, I indeed see the system get
suspend
On 9/17/24 8:44 AM, Christoph Schlameuss wrote:
Fix pointer function arguments whitespaces.
Signed-off-by: Christoph Schlameuss
Generally we don't use the fixup prefix in upstream development AFAIK.
selftests: kvm: s390: Fix whitespace confusion in ucontrol test
Checkpatch thinks that we'r
On 9/17/24 8:44 AM, Christoph Schlameuss wrote:
Add a test case manipulating s390 storage keys from within the ucontrol
VM.
Signed-off-by: Christoph Schlameuss
With the nit fixed:
Reviewed-by: Janosch Frank
+ /* SSKE */
+ sync_regs->gprs[1] = skeyvalue;
+ run->kvm_dirty_r
The test proves that a function that is being kprobed and uses a
post_handler cannot be livepatched.
Only one ftrace_ops with FTRACE_OPS_FL_IPMODIFY set may be registered
to any given function at a time.
Signed-off-by: Michael Vetter
---
V2:
Save and restore kprobe state.
tools/testing/selftes
On 9/17/24 8:44 AM, Christoph Schlameuss wrote:
Add a test case verifying basic running and interaction of ucontrol VMs.
Fill the segment and page tables for allocated memory and map memory on
first access.
* uc_map_unmap
Store and load data to mapped and unmapped memory and use pic segment
