On Fri, Apr 18, 2025 at 12:00 AM Thomas Gleixner wrote:
> On Fri, Apr 18 2025 at 08:37, Thomas Gleixner wrote:
> > On Thu, Apr 17 2025 at 17:46, John Stultz wrote:
> >> Instead it seems like we should just do:
> >> tk->coarse_nsec = tk->tkr_mono.xtime_nsec >> tk->tkr_mono.shift;
> >
> > You end
From: Thomas Gleixner
Lei Chen raised an issue with CLOCK_MONOTONIC_COARSE seeing time
inconsistencies. Lei tracked down that this was being caused by the
adjustment
tk->tkr_mono.xtime_nsec -= offset;
which is made to compensate for the unaccumulated cycles in offset when the
multiplicator
10:39:22AM +0530, Sahil Siddiq wrote:
> > > > [...]
> > > > I was working on getting this patches ready for upstreaming and noticed
> > > > one
> > > > thing:
> > > >
> > > >
> > > > ---
On Fri, Apr 18, 2025 at 03:13:46PM +0200, Luca Weiss wrote:
> Add the required nodes for sound playback via a connected external
> display (DisplayPort over USB-C).
>
> In user space just the following route needs to be set (e.g. using
> ALSA UCM):
>
> amixer -c0 cset name='DISPLAY_PORT_RX Audi
On Fri, Apr 18, 2025 at 03:13:45PM +0200, Luca Weiss wrote:
> Add a compatible for the QCM6490-based Fairphone 5 which can use this
> machine driver.
>
> As a note, QCM6490 RB3 board is using audioreach architecture while
> Fairphone 5 uses pre-audioreach.
>
> Signed-off-by: Luca Weiss
> ---
>
On Fri, Apr 18, 2025 at 03:13:44PM +0200, Luca Weiss wrote:
> Add support for DisplayPort Jack events, so that user space can
> configure the audio routing correctly.
>
> Signed-off-by: Luca Weiss
> ---
> sound/soc/qcom/sm8250.c | 18 --
> 1 file changed, 12 insertions(+), 6 dele
On Fri, Apr 18, 2025 at 03:13:43PM +0200, Luca Weiss wrote:
> Sound machine drivers for Qualcomm SoCs can be reused across multiple
> SoCs. But user space ALSA UCM files depend on the card driver name which
> should be set per board/SoC.
>
> Allow such customization by using driver match data as s
On Fri, Apr 18, 2025 at 03:27:22PM +0200, Luca Weiss wrote:
> Hi Krzysztof, hi Dmitry,
>
> Any feedback on the below proposed patch?
>
> I can also send out a v3 with this patch included soon if that makes it
> easier to review.
>
> Regards
> Luca
>
> On Tue Apr 1, 2025 at 11:32 AM CEST, Luca W
On Fri, Apr 18, 2025 at 10:29:19PM -, Joel Fernandes wrote:
> Hello, Paul,
>
> On Fri, 18 Apr 2025 22:26:17 GMT, "Paul E. McKenney" wrote:
> > On Fri, Apr 18, 2025 at 08:32:46PM +0200, Miguel Ojeda wrote:
> > > On Fri, Apr 18, 2025 at 8:04 PM Paul E. McKenney wrot
> > e:
> > > >
> > > > Suppo
Hello, Paul,
On Fri, 18 Apr 2025 22:26:17 GMT, "Paul E. McKenney" wrote:
> On Fri, Apr 18, 2025 at 08:32:46PM +0200, Miguel Ojeda wrote:
> > On Fri, Apr 18, 2025 at 8:04 PM Paul E. McKenney wrot
> e:
> > >
> > > Suppose we fired up a guest OS and captured the console output. Is ther
> e
> > > a
Hello, Paul,
On Fri, 18 Apr 2025 22:26:17 GMT, "Paul E. McKenney" wrote:
> On Fri, Apr 18, 2025 at 08:32:46PM +0200, Miguel Ojeda wrote:
> > On Fri, Apr 18, 2025 at 8:04 PM Paul E. McKenney wrot
> e:
> > >
> > > Suppose we fired up a guest OS and captured the console output. Is ther
> e
> > > a
On Fri, Apr 18, 2025 at 11:20:29PM +0200, Thomas Weißschuh wrote:
> Hi Paul,
>
> On 2025-04-18 10:32:27-0700, Paul E. McKenney wrote:
> > On Wed, Apr 16, 2025 at 08:40:15PM +0200, Thomas Weißschuh wrote:
> > > Fix some issues uncovered by UBSAN and enable UBSAN for nolibc-test to
> > > avoid regre
Hi Paul,
On 2025-04-18 10:32:27-0700, Paul E. McKenney wrote:
> On Wed, Apr 16, 2025 at 08:40:15PM +0200, Thomas Weißschuh wrote:
> > Fix some issues uncovered by UBSAN and enable UBSAN for nolibc-test to
> > avoid regressions.
> >
> > Signed-off-by: Thomas Weißschuh
>
> Thank you, Thomas! Are
On Fri, Apr 18, 2025 at 08:32:46PM +0200, Miguel Ojeda wrote:
> On Fri, Apr 18, 2025 at 8:04 PM Paul E. McKenney wrote:
> >
> > Suppose we fired up a guest OS and captured the console output. Is there
> > a way to make that guest OS shut down automatically at the end of the
> > test and to extrac
WM8998 codec driver"
depends on MFD_WM8998 && MFD_ARIZONA
config SND_SOC_WM9081
---
base-commit: 7e74f756f5f643148ca5537bf2fee6767e4b0ed9
change-id: 20250418-wm8998-defae73b3320
Best regards,
--
André Apitzsch
The pull request you sent on Fri, 18 Apr 2025 11:36:35 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-kunit-fixes-6.15-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7f424c6690df7a5e807548371b9546d51546fc54
Tha
The pull request you sent on Fri, 18 Apr 2025 11:23:27 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-fixes-6.15-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/338d40ceef38d9a36b48164e22768b40d6f89701
Thank you
On 4/18/2025 12:09 PM, Joel Fernandes wrote:
> From: "Paul E. McKenney"
>
> This commit creates counters in the rcu_torture_one_read_state_updown
> structure that check for a call to ->up_read() that lacks a matching
> call to ->down_read().
>
> While in the area, add end-of-run cleanup code
On Fri, Apr 18, 2025 at 12:56 PM Lorenzo Stoakes
wrote:
>
> On Fri, Apr 18, 2025 at 12:31:29PM -0700, Suren Baghdasaryan wrote:
> > On Fri, Apr 18, 2025 at 11:30 AM Lorenzo Stoakes
> > wrote:
> > >
> > > On Fri, Apr 18, 2025 at 10:49:54AM -0700, Suren Baghdasaryan wrote:
> > > > Test that /proc/p
On Fri, Apr 18, 2025 at 12:31:29PM -0700, Suren Baghdasaryan wrote:
> On Fri, Apr 18, 2025 at 11:30 AM Lorenzo Stoakes
> wrote:
> >
> > On Fri, Apr 18, 2025 at 10:49:54AM -0700, Suren Baghdasaryan wrote:
> > > Test that /proc/pid/maps does not report unexpected holes in the address
> > > space whe
On Fri, Apr 18, 2025 at 11:30 AM Lorenzo Stoakes
wrote:
>
> On Fri, Apr 18, 2025 at 10:49:54AM -0700, Suren Baghdasaryan wrote:
> > Test that /proc/pid/maps does not report unexpected holes in the address
> > space when we concurrently remap a part of a vma into the middle of
> > another vma. This
On Thu, Apr 17, 2025 at 11:37 PM Thomas Gleixner wrote:
> On Thu, Apr 17 2025 at 17:46, John Stultz wrote:
> > On Sat, Apr 5, 2025 at 2:40 PM Thomas Gleixner wrote:
> >> +static inline void tk_update_coarse_nsecs(struct timekeeper *tk, u64
> >> offset)
> >> +{
> >> + offset *= tk->tkr_mono
On Fri, Apr 18, 2025 at 8:04 PM Paul E. McKenney wrote:
>
> Suppose we fired up a guest OS and captured the console output. Is there
> a way to make that guest OS shut down automatically at the end of the
> test and to extract the test results?
Ah, sorry, I thought you were already doing somethi
On Fri, Apr 18, 2025 at 10:49:54AM -0700, Suren Baghdasaryan wrote:
> Test that /proc/pid/maps does not report unexpected holes in the address
> space when we concurrently remap a part of a vma into the middle of
> another vma. This remapping results in the destination vma being split
> into three
On Fri, Apr 18, 2025 at 07:31:53PM +0200, Miguel Ojeda wrote:
> On Fri, Apr 18, 2025 at 6:10 PM Joel Fernandes wrote:
> >
> > a rust_doctests_kernel kunit run. Note that kunit wants a clean source
> > tree, so this runs "make mrproper", which might come as a surprise to
> > some users. Should th
On Fri, Apr 18, 2025 at 01:50:47PM -0300, Herton R. Krzesinski wrote:
> Right now test_kmod has hardcoded dependencies on btrfs/xfs. That
> is not optimal since you end up needing to select/build them, but it
> is not really required since other fs could be selected for the testing.
> Also, we can'
For lockless /proc/pid/maps reading we have to ensure all the fields
used when generating the output are RCU-safe. The only pointer fields
in vm_area_struct which are used to generate that file's output are
vm_file and anon_name. vm_file is RCU-safe but anon_name is not. Make
anon_name RCU-safe as
With maple_tree supporting vma tree traversal under RCU and vma and
its important members being RCU-safe, /proc/pid/maps can be read under
RCU and without the need to read-lock mmap_lock. However vma content
can change from under us, therefore we make a copy of the vma and we
pin pointer fields use
Utilize speculative vma lookup to find and snapshot a vma without
taking mmap_lock during PROCMAP_QUERY ioctl execution. Concurrent
address space modifications are detected and the lookup is retried.
While we take the mmap_lock for reading during such contention, we
do that momentarily only to reco
Add verbose more to the proc tests to print debugging information.
Usage: proc-pid-vm --verbose
Signed-off-by: Suren Baghdasaryan
---
tools/testing/selftests/proc/proc-pid-vm.c | 154 +++--
1 file changed, 141 insertions(+), 13 deletions(-)
diff --git a/tools/testing/selftests/p
Extend /proc/pid/maps tearing test to verify PROCMAP_QUERY ioctl operation
correctness while the vma is being concurrently modified.
Signed-off-by: Suren Baghdasaryan
---
tools/testing/selftests/proc/proc-pid-vm.c | 60 ++
1 file changed, 60 insertions(+)
diff --git a/tools/
Test that /proc/pid/maps does not report unexpected holes in the address
space when we concurrently remap a part of a vma into the middle of
another vma. This remapping results in the destination vma being split
into three parts and the part in the middle being patched back from,
all done concurren
Test that /proc/pid/maps does not report unexpected holes in the address
space when a vma at the edge of the page is being concurrently remapped.
This remapping results in the vma shrinking and expanding from under the
reader. We should always see either shrunk or expanded (original) version
of th
The content of /proc/pid/maps is generated page-by-page with mmap_lock
read lock (or other synchronization mechanism) being dropped in between
these pages. This means that the reader can occasionally retrieve
inconsistent information if the data used for file generation is being
concurrently change
After a long delay I'm posting next iteration of lockless /proc/pid/maps
reading patchset. Differences from v2 [1]:
- Add a set of tests concurrently modifying address space and checking for
correct reading results;
- Use new mmap_lock_speculate_xxx APIs for concurrent change detection and
retries;
Hi Linus,
Please pull the following kunit fixes update for Linux 6.15-rc3.
Fixes arch sh kunit qemu_configs script sh.py to honor kunit cmdline.
diff is attached.
thanks,
-- Shuah
The following changes since commit 8ffd015db85fe
On Wed, Apr 16, 2025 at 08:40:15PM +0200, Thomas Weißschuh wrote:
> Fix some issues uncovered by UBSAN and enable UBSAN for nolibc-test to
> avoid regressions.
>
> Signed-off-by: Thomas Weißschuh
Thank you, Thomas! Are these intended to go into the current v6.15
release, or are you instead thin
On Fri, Apr 18, 2025 at 6:10 PM Joel Fernandes wrote:
>
> a rust_doctests_kernel kunit run. Note that kunit wants a clean source
> tree, so this runs "make mrproper", which might come as a surprise to
> some users. Should there be a --mrproper parameter to torture.sh to make
> the user explicitl
Hi Linus,
Please pull the following kselftest fixes update for Linux 6.15-rc3.
Fixes dynevent_limitations.tc test failure on dash by detecting and
handling bash and dash differences in evaluating \\.
diff is attached.
thanks,
-- Shuah
--
On 4/11/25 2:00 PM, Thomas Weißschuh wrote:
> __sync_bool_compare_and_swap() is deprecated and requires libatomic on
> GCC. Compiler toolchains don't necessarily have libatomic available, so
> avoid this requirement by using atomics that don't need libatomic.
>
> Signed-off-by: Thomas Weißschuh
R
Currently, the driver overrides the rproc ops when booting in IPC-only
mode. Remove these overrides and register the ops unconditionally. This
requires to have IPC-only mode checks in the .prepare and .unprepare ops
and returning early. The other rproc ops are invoked when booting either
in IPC-onl
Test that the SO_INCOMING_NAPI_ID of a network file descriptor is
non-zero. This ensures that either the core networking stack or, in some
cases like netdevsim, the driver correctly sets the NAPI ID.
Signed-off-by: Joe Damato
---
.../testing/selftests/drivers/net/.gitignore | 1 +
tools/testin
On Thu, 17 Apr 2025 11:01:54 -0700 Dan Williams
wrote:
> Darrick J. Wong wrote:
> > On Thu, Apr 10, 2025 at 12:12:33PM -0700, Alison Schofield wrote:
> > > On Thu, Apr 10, 2025 at 11:10:20AM +0200, David Hildenbrand wrote:
> > > > Alison reports an issue with fsdax when large extends end up usin
On Sat, Apr 5, 2025 at 2:40 PM Thomas Gleixner wrote:
>
> Lei Chen raised an issue with CLOCK_MONOTONIC_COARSE seeing time
> inconsistencies. Lei tracked down that this was being caused by the
> adjustment
>
> tk->tkr_mono.xtime_nsec -= offset;
>
> which is made to compensate for the unaccumul
The k3_dsp_rproc_release() function erroneously deasserts the local
reset even for devices which do not support it. Even though it results
in a no-operation, Update the logic to explicitly deassert the local
reset for devices that support it and only the global reset for those
that do not.
Signed-
On 4/11/25 2:00 PM, Thomas Weißschuh wrote:
> The pointers to the wrappers are stored in function pointers,
> preventing them from actually being inlined.
> Remove the inline qualifier, aligning these wrappers with the other
> functions defined through macros.
>
> Signed-off-by: Thomas Weißschuh
On 4/11/25 2:00 PM, Thomas Weißschuh wrote:
> With -Wmissing-prototypes the compiler will warn about non-static
> functions which don't have a prototype defined.
> As they are not used from a different compilation unit they don't need to
> be defined globally.
>
> Avoid the issue by marking the fu
On 4/11/25 2:00 PM, Thomas Weißschuh wrote:
> For tests without fixtures the variant argument is unused.
> This is intentional, prevent to compiler from complaining.
>
> Example warning:
>
> harness-selftest.c: In function 'wrapper_standalone_pass':
> ../kselftest_harness.h:181:52: error:
On 4/11/25 2:00 PM, Thomas Weißschuh wrote:
> Add a selftest for the kselftest harness itself so any changes can be
> validated.
>
> Signed-off-by: Thomas Weißschuh
Reviewed-by: Muhammad Usama Anjum
> ---
> MAINTAINERS| 1 +
> tools/testing/selftests/M
Sound machine drivers for Qualcomm SoCs can be reused across multiple
SoCs. But user space ALSA UCM files depend on the card driver name which
should be set per board/SoC.
Allow such customization by using driver match data as sound card driver
name.
Also while we're already touching these lines,
Right now test_kmod has hardcoded dependencies on btrfs/xfs. That
is not optimal since you end up needing to select/build them, but it
is not really required since other fs could be selected for the testing.
Also, we can't change the default/driver module used for testing on
initialization.
Thus m
On Thu, Apr 17, 2025 at 9:14 PM Luis Chamberlain wrote:
>
> On Thu, Apr 17, 2025 at 09:08:34PM -0300, Herton R. Krzesinski wrote:
> > Right now test_kmod has hardcoded dependencies on btrfs/xfs. That
> > is not optimal since you end up needing to select/build them, but it
> > is not really require
Factor ksft C helpers to a header so they can be used by other C-based
tests.
Signed-off-by: Joe Damato
---
tools/testing/selftests/drivers/net/ksft.h| 56 +++
.../selftests/drivers/net/xdp_helper.c| 49 +---
2 files changed, 58 insertions(+), 47 deletions
On 17/04/2025 12:48, Paolo Abeni wrote:
On 4/15/25 1:17 PM, Antonio Quartulli wrote:
Notable changes since v25:
* removed netdev notifier (was only used for our own devices)
* added .dellink implementation to address what was previously
done in notifier
* removed .ndo_open and moved netif_car
On Thu, 17 Apr 2025 01:32:42 + Joe Damato wrote:
> Test that the SO_INCOMING_NAPI_ID of a network file descriptor is
> non-zero. This ensures that either the core networking stack or, in some
> cases like netdevsim, the driver correctly sets the NAPI ID.
>
> Signed-off-by: Joe Damato
> ---
>
Greetings:
Welcome to v2.
This series fixes netdevsim to correctly set the NAPI ID on the skb.
This is helpful for writing tests around features that use
SO_INCOMING_NAPI_ID.
In addition to the netdevsim fix in patch 1, patches 2-4 do some self
test refactoring and add a test for NAPI IDs. The t
Add link update test for cgroup_storage.
'./test_progs -a cgroup_storage_update'
test_cgroup_storage_update:PASS:create cgroup 0 nsec
setup_network:PASS:ip netns add cgroup_storage_ns 0 nsec
setup_network:PASS:open netns 0 nsec
setup_network:PASS:ip link set lo up 0 nsec
test_cgroup_storage_update
On 4/18/2025 12:09 PM, Joel Fernandes wrote:
> Hi,
>
> Please find the upcoming miscellaneous RCU changes. The changes can also
FYI: Sorry, s/miscellaneous/torture-related/ here.
Also please ignore patches with "XX/12" in their subject, that was an error on
my part.
The rest of the series stand
The previous patch improved the rcu_seq_done_exact() function by adding
a meaningful constant for the guardband.
Ensure that this is working for the future by a quick check during
rcu_gp_init().
Reviewed-by: Paul E. McKenney
Signed-off-by: Joel Fernandes
---
kernel/rcu/tree.c | 6 ++
1 fil
Hi,
Please find the upcoming sequence Counter related RCU changes. The changes can
also
be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git
seq.2025.04.18a
Thanks.
Frederic Weisbecker (1):
rcu: Comment on the extraneous delta test on rcu_seq_done_exact()
Joel
poll_state_synchronize_srcu() uses rcu_seq_done() unlike
poll_state_synchronize_rcu() which uses rcu_seq_done_exact().
The rcu_seq_done_exact() makes more sense for polling API, as with
this API, there is a higher chance that there is a significant delay
between the get_state..() and poll_state..
From: Frederic Weisbecker
The numbers used in rcu_seq_done_exact() lack some explanation behind
their magic. Especially after the commit:
85aad7cc4178 ("rcu: Fix get_state_synchronize_rcu_full() GP-start
detection")
which reported a subtle issue where a new GP sequence snapshot was taken
o
The rcu_seq_done_exact() function checks if a grace period has completed by
comparing sequence numbers. It includes a guard band to handle sequence number
wraparound, which was previously expressed using the magic number calculation
'3 * RCU_SEQ_STATE_MASK + 1'.
This magic number is not immediatel
From: Frederic Weisbecker
This reverts commit f7345ccc62a4b880cf76458db5f320725f28e400.
swake_up_one_online() has been removed because hrtimers can now assign
a proper online target to hrtimers queued from offline CPUs. Therefore
remove the related hackery.
Link: https://lore.kernel.org/all/202
From: I Hsin Cheng
Currently the implementation of "Guard" methods are basically wrappers
around rcu's function within kernel. Building the kernel with llvm
18.1.8 on x86_64 machine will generate the following symbols:
$ nm vmlinux | grep ' _R'.*Guard | rustfilt
817b6c90 T ::new
From: Frederic Weisbecker
It's now ok to perform a wake-up from an offline CPU because the
resulting armed scheduler bandwidth hrtimers are now correctly targeted
by hrtimer infrastructure.
Remove the obsolete hackerry.
Link: https://lore.kernel.org/all/20241231170712.149394-3-frede...@kernel.o
From: Yongliang Gao
When counting the number of hardirqs in the x86 architecture,
it is essential to add arch_irq_stat_cpu to ensure accuracy.
For example, a CPU loop within the rcu_read_lock function.
Before:
[ 70.910184] rcu: INFO: rcu_preempt self-detected stall on CPU
[ 70.910436] rcu:
Hi,
Please find the upcoming miscellaneous RCU changes. The changes can also
be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git
misc.2025.04.18a
Thanks.
Frederic Weisbecker (2):
rcu: Remove swake_up_one_online() bandaid
Revert "rcu/nocb: Fix rcuog wake-up fr
Update MAINTAINERS file to reflect changes to Joel's email address for
upstream work.
Reviewed-by: Paul E. McKenney
Signed-off-by: Joel Fernandes
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 96b827049501..8eb7e057b8f9
From: "Paul E. McKenney"
This commit adds a --do-rcu-rust parameter to torture.sh, which invokes
a rust_doctests_kernel kunit run. Note that kunit wants a clean source
tree, so this runs "make mrproper", which might come as a surprise to
some users. Should there be a --mrproper parameter to tor
From: "Paul E. McKenney"
This commit creates counters in the rcu_torture_one_read_state_updown
structure that check for a call to ->up_read() that lacks a matching
call to ->down_read().
While in the area, add end-of-run cleanup code that prevents calls to
rcu_torture_updown_hrt() from happening
From: "Paul E. McKenney"
Right now, torture.sh runs normal runs unconditionally, which can be slow
and thus annoying when you only want to test --kcsan or --kasan runs.
This commit therefore adds a --do-normal argument so that "--kcsan
--do-no-kasan --do-no-normal" runs only KCSAN runs. Note tha
From: "Paul E. McKenney"
The rcu_torture_reader() and rcu_torture_fwd_prog_cr() functions
run CPU-bound for extended periods of time (tens or even
hundreds of milliseconds), so they invoke tick_dep_set_task() and
tick_dep_clear_task() to ensure that the scheduling-clock tick helps
move grace peri
From: "Paul E. McKenney"
Uses of srcu_read_lock_lite() and srcu_read_unlock_lite() are better
served by the new srcu_read_lock_fast() and srcu_read_unlock_fast() APIs.
As in srcu_read_lock_lite() and srcu_read_unlock_lite() would never have
happened had I thought a bit harder a few months ago. T
From: "Paul E. McKenney"
The torture.sh --do-rt command-line parameter is intended to mimic -rt
kernels. Now that CONFIG_PREEMPT_RT is upstream, this commit makes this
mimicking more precise.
Note that testing of RCU priority boosting is disabled in favor
of forward-progress testing of RCU call
From: "Paul E. McKenney"
The down/up SRCU reader testing uses an hrtimer handler to exit the SRCU
read-side critical section. This might be delayed, and if delayed for
too long, it can prevent the rcutorture run from completing. This commit
therefore complains if the hrtimer handler is delayed
From: "Paul E. McKenney"
The rcu_torture_one_read() function is designed for RCU readers that are
confined to a task, such that a single thread of control extends from the
beginning of a given RCU read-side critical section to its end. This does
not suffice for things like srcu_down_read() and s
From: "Paul E. McKenney"
This commit adds a new rcutorture.n_up_down kernel boot parameter
that specifies the number of outstanding SRCU up/down readers, which
begin in kthread context and end in an hrtimer handler. There is a new
kthread ("rcu_torture_updown") that scans an per-reader array loo
From: "Paul E. McKenney"
This is strictly a code-movement commit, pulling that part of
the rcu_torture_updown() function's loop body that processes
one rcu_torture_one_read_state_updown structure into a new
rcu_torture_updown_one() function. The checks for the end of the
torture test and the cur
From: "Paul E. McKenney"
The srcu_lockdep.sh currently blindly trusts the rcutorture SRCU-P
scenario to build its kernel with lockdep enabled. Of course, this
dependency might not be obvious to someone rebalancing SRCU scenarios.
This commit therefore adds code to srcu_lockdep.sh that verifies t
From: "Paul E. McKenney"
Mixing different flavors of RCU readers is forbidden, for example, you
should not use srcu_read_lock() and srcu_read_lock_nmisafe() on the same
srcu_struct structure. There are checks for this, but these checks are
not tested on a regular basis. This commit therefore ad
Currently, the ->gpwrap is not tested (at all per my testing) due to the
requirement of a large delta between a CPU's rdp->gp_seq and its node's
rnp->gpseq.
This results in no testing of ->gpwrap being set. This patch by default
adds 5 minutes of testing with ->gpwrap forced by lowering the delta
On ARM64, when running with --configs '36*SRCU-P', I noticed that only 1
instance
instead of 36 for starting.
Fix it by checking for Image files, instead of bzImage which ARM does
not seem to have. With this I see all 36 instances running at the same
time in the batch.
Tested-by: Paul E. McKenne
From: "Paul E. McKenney"
This commit adds a --do-rcu-rust parameter to torture.sh, which invokes
a rust_doctests_kernel kunit run. Note that kunit wants a clean source
tree, so this runs "make mrproper", which might come as a surprise to
some users. Should there be a --mrproper parameter to tor
From: "Paul E. McKenney"
Uses of srcu_read_lock_lite() and srcu_read_unlock_lite() are better
served by the new srcu_read_lock_fast() and srcu_read_unlock_fast() APIs.
As in srcu_read_lock_lite() and srcu_read_unlock_lite() would never have
happened had I thought a bit harder a few months ago. T
From: "Paul E. McKenney"
Right now, torture.sh runs normal runs unconditionally, which can be slow
and thus annoying when you only want to test --kcsan or --kasan runs.
This commit therefore adds a --do-normal argument so that "--kcsan
--do-no-kasan --do-no-normal" runs only KCSAN runs. Note tha
From: "Paul E. McKenney"
This commit creates counters in the rcu_torture_one_read_state_updown
structure that check for a call to ->up_read() that lacks a matching
call to ->down_read().
While in the area, add end-of-run cleanup code that prevents calls to
rcu_torture_updown_hrt() from happening
From: "Paul E. McKenney"
The rcu_torture_reader() and rcu_torture_fwd_prog_cr() functions
run CPU-bound for extended periods of time (tens or even
hundreds of milliseconds), so they invoke tick_dep_set_task() and
tick_dep_clear_task() to ensure that the scheduling-clock tick helps
move grace peri
From: "Paul E. McKenney"
The down/up SRCU reader testing uses an hrtimer handler to exit the SRCU
read-side critical section. This might be delayed, and if delayed for
too long, it can prevent the rcutorture run from completing. This commit
therefore complains if the hrtimer handler is delayed
From: "Paul E. McKenney"
This commit adds a new rcutorture.n_up_down kernel boot parameter
that specifies the number of outstanding SRCU up/down readers, which
begin in kthread context and end in an hrtimer handler. There is a new
kthread ("rcu_torture_updown") that scans an per-reader array loo
From: "Paul E. McKenney"
This is strictly a code-movement commit, pulling that part of
the rcu_torture_updown() function's loop body that processes
one rcu_torture_one_read_state_updown structure into a new
rcu_torture_updown_one() function. The checks for the end of the
torture test and the cur
From: "Paul E. McKenney"
The rcu_torture_one_read() function is designed for RCU readers that are
confined to a task, such that a single thread of control extends from the
beginning of a given RCU read-side critical section to its end. This does
not suffice for things like srcu_down_read() and s
From: "Paul E. McKenney"
The torture.sh --do-rt command-line parameter is intended to mimic -rt
kernels. Now that CONFIG_PREEMPT_RT is upstream, this commit makes this
mimicking more precise.
Note that testing of RCU priority boosting is disabled in favor
of forward-progress testing of RCU call
From: "Paul E. McKenney"
Mixing different flavors of RCU readers is forbidden, for example, you
should not use srcu_read_lock() and srcu_read_lock_nmisafe() on the same
srcu_struct structure. There are checks for this, but these checks are
not tested on a regular basis. This commit therefore ad
From: "Paul E. McKenney"
The srcu_lockdep.sh currently blindly trusts the rcutorture SRCU-P
scenario to build its kernel with lockdep enabled. Of course, this
dependency might not be obvious to someone rebalancing SRCU scenarios.
This commit therefore adds code to srcu_lockdep.sh that verifies t
Hi,
Please find the upcoming miscellaneous RCU changes. The changes can also
be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/jfern/linux.git
torture.2025.04.18a
Thanks.
Joel Fernandes (2):
rcutorture: Perform more frequent testing of ->gpwrap
rcutorture: Fix issue with r
On Tue, Apr 15, 2025, Elena Reshetova wrote:
> +/* This lock is held to prevent new EPC pages from being created
> + * during the execution of ENCLS[EUPDATESVN].
> + */
> +static DEFINE_SPINLOCK(sgx_epc_eupdatesvn_lock);
> +
> static atomic_long_t sgx_nr_used_pages = ATOMIC_LONG_INIT(0);
> static
On Thu, Apr 17, 2025, Kai Huang wrote:
> I think the sgx_updatesvn() should just return true when EUPDATESVN returns 0
> or
> SGX_NO_UPDATE, and return false for all other error codes. And it should
> ENCLS_WARN() for all other error codes, except SGX_INSUFFICIENT_ENTROPY
> because
> it can stil
Add a compatible for the QCM6490-based Fairphone 5 which can use this
machine driver.
As a note, QCM6490 RB3 board is using audioreach architecture while
Fairphone 5 uses pre-audioreach.
Signed-off-by: Luca Weiss
---
sound/soc/qcom/sm8250.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/so
Hi Krzysztof, hi Dmitry,
Any feedback on the below proposed patch?
I can also send out a v3 with this patch included soon if that makes it
easier to review.
Regards
Luca
On Tue Apr 1, 2025 at 11:32 AM CEST, Luca Weiss wrote:
> Hi Dmitry,
>
> On Wed Mar 12, 2025 at 8:06 PM CET, Dmitry Baryshkov
1 - 100 of 113 matches
Mail list logo
