ses:
https://lore.kernel.org/all/20250610103729.72440-1-aishwarya@arm.com/
Tested-by: Aishwarya TCV
Tested-by : Donet Tom
Reviewed-by: Lorenzo Stoakes
Signed-off-by: Dev Jain
---
v1->v2:
- Add CONFIG_UPROBES (Mark Brown)
- Add CONFIG_PROFILING (Lorenzo)
tools/testing/selftests/mm/config | 3 +++
1
On 11/06/25 6:00 pm, Pedro Falcato wrote:
On Wed, Jun 11, 2025 at 05:40:11PM +0530, Dev Jain wrote:
If CONFIG_UPROBES is not set, a merge subtest fails:
Failure log:
7151 12:46:54.627936 # # # RUN
merge.handle_uprobe_upon_merged_vma ...
7152 12:46:54.639014 # # f /sys
ishwarya
Closes:
https://lore.kernel.org/linux-mm/20250610103729.72440-1-aishwarya@arm.com/
Signed-off-by: Pedro Falcato
---
Reviewed-by: Dev Jain
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended r
On 11/06/25 6:05 pm, Lorenzo Stoakes wrote:
Thanks for this!
On Wed, Jun 11, 2025 at 05:40:11PM +0530, Dev Jain wrote:
If CONFIG_UPROBES is not set, a merge subtest fails:
Failure log:
7151 12:46:54.627936 # # # RUN
merge.handle_uprobe_upon_merged_vma ...
7152 12:46
On 11/06/25 6:09 pm, Mark Brown wrote:
On Wed, Jun 11, 2025 at 05:40:11PM +0530, Dev Jain wrote:
If CONFIG_UPROBES is not set, a merge subtest fails:
...
CONFIG_UPROBES is enabled by CONFIG_UPROBE_EVENTS, which gets enabled by
CONFIG_FTRACE. Therefore add this config to selftests/mm
e kernel build.
Fixes: efe99fabeb11b ("selftests/mm: add test about uprobe pte be orphan during
vma merge")
Reported-by: Aishwarya
Closes:
https://lore.kernel.org/all/20250610103729.72440-1-aishwarya@arm.com/
Signed-off-by: Dev Jain
---
tools/testing/selftests/mm/config | 1 +
1 f
page number to self-adjustable number
according to the real number of free memory.
Fixes: bd67d5c15cc19 ("Test compaction of mlocked memory")
Signed-off-by: Feng Tang
Not sure if fixes tag is needed.
Acked-by: Dev Jain
---
tools/testing/selftests/mm/compaction_test.c | 19 +++
On 15/04/25 12:28 pm, Anshuman Khandual wrote:
On 4/10/25 15:37, Donet Tom wrote:
During cleanup, the value of /proc/sys/vm/nr_hugepages is currently
being set to 0. At the end of the test, if all tests pass, the
original nr_hugepages value is restored. However, if any test fails,
it remain
arm64: add hugetlb mte tests")
Cc: Yang Shi
Reported-by: Naresh Kamboju
Signed-off-by: Catalin Marinas
Reviewed-by: Dev Jain
On 8/27/24 17:16, Dev Jain wrote:
On 8/27/24 17:14, Shuah Khan wrote:
On 8/22/24 06:14, Dev Jain wrote:
Rename sigaltstack to generic signal directory, to allow adding more
signal tests in the future.
Sorry - I think I mentioned I don't like this test renamed. Why are
you sending
A "%s" is missing in ksft_exit_fail_msg(); instead, use the newly
introduced ksft_exit_fail_perror().
Signed-off-by: Dev Jain
---
tools/testing/selftests/arm64/abi/ptrace.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/arm64/abi/p
is
still a subjective choice). Note that, this has no effect on the
execution time of the test since that is controlled by a timeout.
[1] https://lore.kernel.org/all/20240801081657.1386743-1-dev.j...@arm.com/
Signed-off-by: Dev Jain
Suggested-by: David Hildenbrand
Reviewed-by: Ryan Roberts
On 8/28/24 16:31, Mark Brown wrote:
On Tue, Aug 27, 2024 at 01:33:47PM +0100, Will Deacon wrote:
On Tue, Aug 27, 2024 at 10:48:51AM +0530, Dev Jain wrote:
A "%s" is missing in ksft_exit_fail_msg(); instead, use the newly
introduced ksft_exit_fail_perror(). Also, uint64_t corr
On 8/28/24 16:10, Mark Brown wrote:
On Tue, Aug 27, 2024 at 10:48:51AM +0530, Dev Jain wrote:
- ksft_exit_fail_msg("PTRACE_TRACEME", strerror(errno));
+ ksft_exit_fail_perror("PTRACE_TRACEME");
if (raise(SIGSTOP))
- ksft_
On 8/27/24 18:03, Will Deacon wrote:
On Tue, Aug 27, 2024 at 10:48:51AM +0530, Dev Jain wrote:
A "%s" is missing in ksft_exit_fail_msg(); instead, use the newly
introduced ksft_exit_fail_perror(). Also, uint64_t corresponds to
unsigned 64-bit integer, so use %lx instead of %llx.
Wh
On 8/27/24 17:14, Shuah Khan wrote:
On 8/22/24 06:14, Dev Jain wrote:
Rename sigaltstack to generic signal directory, to allow adding more
signal tests in the future.
Sorry - I think I mentioned I don't like this test renamed. Why are
you sending
this rename still included in the
On 8/27/24 17:08, Shuah Khan wrote:
On 8/22/24 05:10, Dev Jain wrote:
On 8/22/24 08:33, Shuah Khan wrote:
On 8/21/24 00:15, Dev Jain wrote:
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Can you elaborate on the benefits if renaming the test?
Also you have
A "%s" is missing in ksft_exit_fail_msg(); instead, use the newly
introduced ksft_exit_fail_perror(). Also, uint64_t corresponds to
unsigned 64-bit integer, so use %lx instead of %llx.
Signed-off-by: Dev Jain
---
The changes in ptrace.c were earlier a part of the follow
On 8/22/24 17:30, Yang Ruibin wrote:
To correctly detect whether mmap is successful, must use if
(map_ptr == MAP_FAILED)to avoid incorrectly handling a valid
mapping.Fix mmap() error paths to check for MAP_FAILED.
Shouldn't you have written "avoid processing the return value
from a failed mm
signal, delivered signal,
and ucontext. The ucontext is mangled with, by adding a signal mask to
it; on return from the handler, the thread must block the corresponding
signal.
In the test description, I have also described signal delivery and blockage,
for ease of understanding what the test does
Rename sigaltstack to generic signal directory, to allow adding more
signal tests in the future.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore
functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
v1:
- https://lore.kernel.org/all/20240607122319.768640-1-dev.j...@arm.com/
Dev Jain (2):
selftests: Rename sigaltstack to generic signal
selftests: Add a test mangling with uc_sigmask
tools/testing/selfte
On 8/22/24 17:39, Dev Jain wrote:
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Sorry, hastily copied the commit message from the previous
iteration :) will send again, kindly ignore this.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools
signal, delivered signal,
and ucontext. The ucontext is mangled with, by adding a signal mask to
it; on return from the handler, the thread must block the corresponding
signal.
In the test description, I have also described signal delivery and blockage,
for ease of understanding what the test does
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 0
tools/testing/selfte
functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
v1:
- https://lore.kernel.org/all/20240607122319.768640-1-dev.j...@arm.com/
Dev Jain (2):
selftests: Rename sigaltstack to generic signal
selftests: Add a test mangling with uc_sigmask
tools/testing/selfte
On 8/22/24 08:33, Shuah Khan wrote:
On 8/21/24 00:15, Dev Jain wrote:
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Can you elaborate on the benefits if renaming the test?
Also you have such a good information in the cover-letter for this
patch - it would be
blockage,
for ease of understanding what the test does.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools/testing/selftests/signal/.gitignore | 1 +
tools/testing/selftests/signal/Makefile | 3 +-
.../selftests/signal/mangle_uc_sigmask.c | 184 ++
3 files
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 2 +-
tools/test
ot be queued
- Remove unneeded ,
- Give a detailed test description in the comments; also describe the
exact meaning of delivered and blocked
- Handle errors for all libc functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
v1:
- https://lore.kernel.org/all/2024
On 8/19/24 12:28, Huang, Ying wrote:
Dev Jain writes:
On 8/13/24 12:52, Dev Jain wrote:
On 8/13/24 10:30, Dev Jain wrote:
On 8/12/24 17:38, Dev Jain wrote:
On 8/12/24 13:01, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:45, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04
On 8/13/24 12:52, Dev Jain wrote:
On 8/13/24 10:30, Dev Jain wrote:
On 8/12/24 17:38, Dev Jain wrote:
On 8/12/24 13:01, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:45, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As
On 8/13/24 10:30, Dev Jain wrote:
On 8/12/24 17:38, Dev Jain wrote:
On 8/12/24 13:01, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:45, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio
On 8/12/24 17:38, Dev Jain wrote:
On 8/12/24 13:01, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:45, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio(), wherein we backoff
if the
folio
On 8/12/24 13:01, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:45, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check
On 8/12/24 11:45, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check during the unmapping phase, upon
the failure of which, the
On 8/12/24 11:50, Huang, Ying wrote:
Dev Jain writes:
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check during the unmapping phase, upon
the failure of which, the
On 8/9/24 22:43, Shuah Khan wrote:
On 8/9/24 04:31, Dev Jain wrote:
Do not fail the test for just a single instance of migration failure,
since migration is a best-effort service.
The cover letter says:
"Given that migration is a best-effort service, it is wrong to fail the
test for j
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check during the unmapping phase, upon
the failure of which, the original state of the PTEs will be restored and
the folio
On 8/12/24 11:04, Huang, Ying wrote:
Hi, Dev,
Dev Jain writes:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check during the unmapping phase, upon
the failure of which, the original state of the PTEs will be restored and
the folio
On 8/11/24 14:38, David Hildenbrand wrote:
On 11.08.24 08:06, Dev Jain wrote:
On 8/11/24 00:22, David Hildenbrand wrote:
On 10.08.24 20:42, Dev Jain wrote:
On 8/9/24 19:17, David Hildenbrand wrote:
On 09.08.24 12:31, Dev Jain wrote:
As already being done in __migrate_folio(), wherein we
On 8/11/24 00:22, David Hildenbrand wrote:
On 10.08.24 20:42, Dev Jain wrote:
On 8/9/24 19:17, David Hildenbrand wrote:
On 09.08.24 12:31, Dev Jain wrote:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check during the unmapping
On 8/9/24 19:17, David Hildenbrand wrote:
On 09.08.24 12:31, Dev Jain wrote:
As already being done in __migrate_folio(), wherein we backoff if the
folio refcount is wrong, make this check during the unmapping phase,
upon
the failure of which, the original state of the PTEs will be restored
Do not fail the test for just a single instance of migration failure,
since migration is a best-effort service.
Signed-off-by: Dev Jain
Suggested-by: David Hildenbrand
Reviewed-by: Ryan Roberts
Tested-by: Ryan Roberts
---
tools/testing/selftests/mm/migration.c | 17 +++--
1 file
will make progress and migration will be retried.
Signed-off-by: Dev Jain
---
mm/migrate.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/mm/migrate.c b/mm/migrate.c
index e7296c0fb5d5..477acf996951 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -1250,6 +1250,15 @@ static int
is still a subjective choice).
[1] https://lore.kernel.org/all/20240801081657.1386743-1-dev.j...@arm.com/
Dev Jain (2):
mm: Retry migration earlier upon refcount mismatch
selftests/mm: Do not fail test for a single migration failure
mm/migrate.c | 9 +
tools
On 7/22/24 20:28, Shuah Khan wrote:
On 7/15/24 05:49, Dev Jain wrote:
On 6/30/24 20:48, Oleg Nesterov wrote:
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
+void handler_usr(int signo, siginfo_t *info, void *uc
ith ifdeffery to prevent compiler warning on other arches
Signed-off-by: Dev Jain
Reviewed-by: Ryan Roberts
---
The patch applies on linux-next.
tools/testing/selftests/mm/va_high_addr_switch.c | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selfte
On 7/17/24 17:27, Ryan Roberts wrote:
On 17/07/2024 12:10, Dev Jain wrote:
Post my improvement of the test:
https://lore.kernel.org/all/20240522070435.773918-3-dev.j...@arm.com/
The test begins to fail on 4k and 16k pages, on non-LPA2 systems. To
reduce noise in the CI systems, let us skip
Post my improvement of the test:
https://lore.kernel.org/all/20240522070435.773918-3-dev.j...@arm.com/
The test begins to fail on 4k and 16k pages, on non-LPA2 systems. To
reduce noise in the CI systems, let us skip the test when higher address
space is not implemented.
Signed-off-by: Dev Jain
On 6/27/24 09:22, Dev Jain wrote:
This patch series is motivated by the following observation:
Raise a signal, jump to signal handler. The ucontext_t structure dumped
by kernel to userspace has a uc_sigmask field having the mask of blocked
signals. If you run a fresh minimalistic program
On 7/13/24 04:47, Remington Brasga wrote:
The string passed to ksft_test_result_skip is missing the `type_name`
Signed-off-by: Remington Brasga
---
clang-tidy reported clang-diagnostic-format-insufficient-args warning
on this line, so I am fixing it.
tools/testing/selftests/arm64/abi/ptrac
On 7/13/24 04:47, Remington Brasga wrote:
The string passed to ksft_test_result_skip is missing the `type_name`
Signed-off-by: Remington Brasga
Reviewed-by: Dev Jain
On 6/30/24 20:48, Oleg Nesterov wrote:
I see nothing wrong, but perhaps this test can be simplified?
Feel free to ignore.
Say,
On 06/27, Dev Jain wrote:
+void handler_usr(int signo, siginfo_t *info, void *uc)
+{
+ int ret;
+
+ /*
+* Break out of infinite recursion caused
blockage,
for ease of understanding what the test does.
Signed-off-by: Dev Jain
---
tools/testing/selftests/signal/.gitignore | 1 +
tools/testing/selftests/signal/Makefile | 3 +-
.../selftests/signal/mangle_uc_sigmask.c | 186 ++
3 files changed, 189 insertions
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 2 +-
tools/test
test description in the comments; also describe the
exact meaning of delivered and blocked
- Handle errors for all libc functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
v1:
- https://lore.kernel.org/all/20240607122319.768640-1-dev.j...@arm.com/
Dev Jain
On 6/26/24 17:24, Oleg Nesterov wrote:
On 06/26, Dev Jain wrote:
+int main(int argc, char *argv[])
+{
+ struct sigaction act, act2;
+ sigset_t *set, *oldset;
...
+ set = malloc(sizeof(sigset_t *));
+ if (!set)
+ ksft_exit_fail_perror("m
blockage,
for ease of understanding what the test does.
Signed-off-by: Dev Jain
---
tools/testing/selftests/signal/.gitignore | 1 +
tools/testing/selftests/signal/Makefile | 3 +-
.../selftests/signal/mangle_uc_sigmask.c | 194 ++
3 files changed, 197 insertions
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
Reviewed-by: Mark Brown
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 2 +-
tools/test
g of delivered and blocked
- Handle errors for all libc functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
v1:
- https://lore.kernel.org/all/20240607122319.768640-1-dev.j...@arm.com/
Dev Jain (2):
selftests: Rename sigaltstack to generic signal
selftests: Ad
.
Signed-off-by: Dev Jain
---
v2->v3:
- Add abi Makefile and .gitignore
- Remove config file
v1->v2:
- Add config file
tools/testing/selftests/Makefile | 1 +
tools/testing/selftests/arm/Makefile | 56 +++
tools/testing/selftests/arm/
For a 64-bit parent debugging a 32-bit child, add tests for reading the
TLS registers, and mangling with the mode bits in CPSR.
Signed-off-by: Dev Jain
---
tools/testing/selftests/arm/abi/ptrace_64.c | 91 +++
.../selftests/arm/abi/trivial_32bit_program.c | 14 +++
2 files
For a 32-bit parent debugging a 32-bit child, add tests for reading the
TLS registers, and mangling with the mode bits in CPSR.
Signed-off-by: Dev Jain
---
tools/testing/selftests/arm/abi/ptrace.c | 82
tools/testing/selftests/arm/abi/ptrace.h | 57
2
Split some of the common code to be used by selftests/arm, into ptrace.h.
Signed-off-by: Dev Jain
---
tools/testing/selftests/arm64/abi/ptrace.c | 121 ++
tools/testing/selftests/arm64/abi/ptrace.h | 135 +
2 files changed, 145 insertions(+), 111 deletions
ne.
Fixes: ecaf4d3f734f ("kselftest/arm64: Add test coverage for NT_ARM_TLS")
Fixes: cb5aa6379438 ("kselftest/arm64: Add a smoke test for ptracing hardware
break/watch points")
Signed-off-by: Dev Jain
---
tools/testing/selftests/arm64/abi/ptrace.c | 6 +++---
1 file changed
illegal attempt and the testcases are expected to terminate via SEGV.
Signed-off-by: Dev Jain
---
.../testcases/mangle_cpsr_invalid_aif_bits.c | 33 +++
.../mangle_cpsr_invalid_compat_toggle.c | 29
2 files changed, 62 insertions(+)
create mode 100644
Use ifdeffery to guard code chunks meant specifically for arm64, in
preparation for putting signal tests in selftests/arm.
Signed-off-by: Dev Jain
---
.../selftests/arm/signal/test_signals.c | 2 +
.../selftests/arm/signal/test_signals.h | 2 +
.../selftests/arm/signal
This patch introduces an ELF parsing test. A basic sanity check is
required to ensure that we are actually testing a 32-bit build.
Signed-off-by: Dev Jain
---
v2->v3:
- Introduce two more testcases
tools/testing/selftests/arm/elf/parse_elf.c | 77 +
1 file changed,
/proc/self/maps.
Signed-off-by: Dev Jain
---
v2->v3:
- Split into multiple testcases
tools/testing/selftests/arm/mm/compat_va.c | 89 ++
1 file changed, 89 insertions(+)
create mode 100644 tools/testing/selftests/arm/mm/compat_va.c
diff --git a/tools/testing/selftests/
d warnings in selftests/arm64 (can be applied independent of this
series)
v1->v2:
- Formatting changes
- Add .gitignore files and config file
v1:
- https://lore.kernel.org/all/20240405084410.256788-1-dev.j...@arm.com/
Dev Jain (9):
selftests/arm: Add mm test
selftests/arm: Add elf test
On 6/12/24 18:46, Mark Brown wrote:
On Wed, Jun 12, 2024 at 10:14:01AM +0530, Dev Jain wrote:
On 6/11/24 16:55, Mark Brown wrote:
On Tue, Jun 11, 2024 at 01:26:50PM +0530, Dev Jain wrote:
+ * A signal is said to be delivered, when the program takes action on the
+ * signal: such action may
On 6/12/24 16:14, Muhammad Usama Anjum wrote:
diff --git a/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
b/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
index 4f5881d4ef66d..695c45635d257 100644
--- a/tools/testing/selftests/kvm/x86_64/hyperv_cpuid.c
+++ b/tools/testing/selftests/kvm
On 6/11/24 16:55, Mark Brown wrote:
On Tue, Jun 11, 2024 at 01:26:50PM +0530, Dev Jain wrote:
+ * A signal is said to be delivered, when the program takes action on the
+ * signal: such action may involve termination of the process, ignoring the
+ * signal, terminating with core dump
On 6/11/24 16:24, Mark Brown wrote:
On Tue, Jun 11, 2024 at 01:26:49PM +0530, Dev Jain wrote:
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
---
If people review patches and give a tag for them you should carry the
tag forward to avoid
a signal to be delivered or blocked, for ease of clarity.
Signed-off-by: Dev Jain
---
tools/testing/selftests/signal/.gitignore | 1 +
tools/testing/selftests/signal/Makefile | 3 +-
.../selftests/signal/mangle_uc_sigmask.c | 194 ++
3 files changed, 197
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 2 +-
tools/testing/selftests/{sigaltstack =>
ive a detailed test description in the comments; also describe the
exact meaning of delivered and blocked
- Handle errors for all libc functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
Dev Jain (2):
selftests: Rename sigaltstack to generic signal
s
Sorry, please ignore this email thread; I am sending another one.
On 6/11/24 13:13, Dev Jain wrote:
This patch series is motivated by the following observation:
Raise a signal, jump to signal handler. The ucontext_t structure dumped
by kernel to userspace has a uc_sigmask field having the mask
a signal to be delivered or blocked, for ease of clarity.
Signed-off-by: Dev Jain
---
tools/testing/selftests/signal/.gitignore | 1 +
tools/testing/selftests/signal/Makefile | 3 +-
.../selftests/signal/mangle_uc_sigmask.c | 194 ++
3 files changed, 197
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 2 +-
tools/testing/selftests/{sigaltstack =>
; also describe the
exact meaning of delivered and blocked
- Handle errors for all libc functions/syscalls
- Mention tests in Makefile and .gitignore in alphabetical order
Dev Jain (2):
selftests: Rename sigaltstack to generic signal
selftests: Add a test mangling with uc_sigmask
tools/te
On 6/7/24 19:12, Mark Brown wrote:
On Fri, Jun 07, 2024 at 06:53:27PM +0530, Dev Jain wrote:
On 6/7/24 18:42, Mark Brown wrote:
On Fri, Jun 07, 2024 at 05:53:19PM +0530, Dev Jain wrote:
+ * Test describing a clear distinction between signal states - delivered and
+ * blocked, and their
On 6/7/24 18:42, Mark Brown wrote:
On Fri, Jun 07, 2024 at 05:53:19PM +0530, Dev Jain wrote:
This test asserts the relation between blocked signal, delivered signal,
and ucontext. The ucontext is mangled with, by adding a signal mask to
it; on return from the handler, the thread must block
This test asserts the relation between blocked signal, delivered signal,
and ucontext. The ucontext is mangled with, by adding a signal mask to
it; on return from the handler, the thread must block the corresponding
signal.
Signed-off-by: Dev Jain
---
tools/testing/selftests/signal/.gitignore
Rename sigaltstack to signal, and rename the existing test to
sigaltstack.c.
Signed-off-by: Dev Jain
---
tools/testing/selftests/Makefile| 2 +-
tools/testing/selftests/{sigaltstack => signal}/.gitignore | 2 +-
tools/testing/selftests/{sigaltstack =>
signals blocked using sigaction()
remain blocked only till the execution of the handler, and not in the
context present before jumping to the handler (but nothing can be
confirmed from the man-pages), the series introduces a test for
mangling with uc_sigmask. I will send a separate series to fix the
On 6/5/24 17:30, Mark Brown wrote:
On Wed, Jun 05, 2024 at 05:24:48PM +0530, Dev Jain wrote:
Currently, we are writing the same value as we read, into the TLS
register; hence, we cannot confirm updation of the register, making the
testcase "verify_tpidr_one" redundant. Fix this; w
Currently, we are writing the same value as we read, into the TLS
register; hence, we cannot confirm updation of the register, making the
testcase "verify_tpidr_one" redundant. Fix this; while at it, do a style
change.
Signed-off-by: Dev Jain
---
tools/testing/selftests/arm64/abi/pt
When invoking the binary with "--run-hugetlb" flag, the testcases
involving the base page are anyways going to be run. Therefore, remove
duplication by invoking the binary only once.
Signed-off-by: Dev Jain
---
tools/testing/selftests/mm/va_high_addr_switch.sh | 4
1 file
populating the array as a stack variable, and filling
in the page size and hugepage size at runtime.
Suggested-by: Andrew Morton
Signed-off-by: Dev Jain
---
.../selftests/mm/va_high_addr_switch.c| 454 +-
1 file changed, 232 insertions(+), 222 deletions(-)
diff --git a/tools
granules on higher addresses; we restructure the test to
support the same. In addition, we avoid invocation of the binary twice,
in the shell script, to reduce test noise.
Dev Jain (2):
selftests/mm: va_high_addr_switch: Reduce test noise
selftests/mm: va_high_addr_switch: Dynamically
On 5/20/24 05:18, Andrew Morton wrote:
On Thu, 16 May 2024 09:26:33 +0530 Dev Jain wrote:
Post FEAT_LPA2, Aarch64 extends the 4KB and 16KB translation granule to
large virtual addresses. Currently, the test is being skipped for said
granule sizes, because the page sizes have been statically
he test
succeeding always. Q.E.D
Changes in v2:
- Handle unsigned long number of hugepages
v1:
- https://lore.kernel.org/all/20240515093633.54814-3-dev.j...@arm.com/
NOTE: This patch depends on the previous one.
Fixes: bd67d5c15cc1 ("Test compaction of mlocked memory")
Cc: sta...@vger.k
Currently, the test tries to set nr_hugepages to zero, but that is not
actually done because the file offset is not reset after read(). Fix that
using lseek().
Fixes: bd67d5c15cc1 ("Test compaction of mlocked memory")
Cc: sta...@vger.kernel.org
Signed-off-by: Dev Jain
---
too
: bd67d5c15cc1 ("Test compaction of mlocked memory")
Cc: sta...@vger.kernel.org
Signed-off-by: Dev Jain
---
tools/testing/selftests/mm/compaction_test.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/mm/compaction_test.c
b/too
- Combine the first patch (previously standalone) with this series
Link to v1:
https://lore.kernel.org/all/20240513082842.4117782-1-dev.j...@arm.com/
https://lore.kernel.org/all/20240515093633.54814-1-dev.j...@arm.com/
Dev Jain (3):
selftests/mm: compaction_test: Fix bogus test success on Aarch64
On 5/20/24 05:33, Andrew Morton wrote:
On Wed, 15 May 2024 15:06:33 +0530 Dev Jain wrote:
Reset nr_hugepages to zero before the start of the test.
If a non-zero number of hugepages is already set before the start of the
test, the following problems arise:
- The probability of the test
On 5/20/24 05:30, Andrew Morton wrote:
On Wed, 15 May 2024 15:06:32 +0530 Dev Jain wrote:
nr_hugepages is not set to zero because the file offset has not been reset
after read(). Fix that using lseek().
Please fully describe the runtime effects of this bug.
This is not a "bug&qu
testcases. Instead, don't skip the test, and encourage the user
to manually change the macros.
Signed-off-by: Dev Jain
---
.../testing/selftests/mm/va_high_addr_switch.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftes
1 - 100 of 130 matches
Mail list logo
