On 09/05/25 3:50 am, David Hildenbrand wrote:
Let's test some basic functionality using /dev/mem. These tests will
implicitly cover some PAT (Page Attribute Handling) handling on x86.
These tests will only run when /dev/mem access to the first two pages
in physical address space is possible a
Hi Mathieu,
On 08/05/25 21:16, Mathieu Poirier wrote:
> On Fri, Apr 25, 2025 at 04:11:12PM +0530, Beleswar Padhi wrote:
>> The mailbox .rx_callback implementations in TI K3 R5, DSP and M4
>> remoteproc drivers handle inbound mailbox messages in the same way.
>> Introduce a common driver 'ti_k3_com
On Fri, May 09, 2025 at 11:32:13AM +0800, Z qiang wrote:
> >
> > On Wed, May 07, 2025 at 07:26:05PM +0800, Zqiang wrote:
> > > In the preparation stage of CPU online, if the corresponding
> > > the rdp's->nocb_cb_kthread does not exist, will be created,
> > > there is a situation where the rdp's rc
: 38d976c32d85ef12dcd2b8a231196f7049548477
patch link:
https://lore.kernel.org/r/20250505-vmlinux-mmap-v3-1-5d53afa060e8%40isovalent.com
patch subject: [PATCH bpf-next v3 1/3] btf: allow mmap of vmlinux btf
config: arc-randconfig-r073-20250508
(https://download.01.org/0day-ci/archive/20250509/202505091116.jhtywjw4-...@intel.com
>
> On Wed, May 07, 2025 at 07:26:05PM +0800, Zqiang wrote:
> > In the preparation stage of CPU online, if the corresponding
> > the rdp's->nocb_cb_kthread does not exist, will be created,
> > there is a situation where the rdp's rcuop kthreads creation fails,
> > and then de-offload this CPU's rdp
On 7/5/25 22:24, Jason Gunthorpe wrote:
On Wed, May 07, 2025 at 09:18:29PM +1000, Alexey Kardashevskiy wrote:
We should not destroy the vdevice for something like that. In a CC
case that would unplug it from the VM which is not right.
vdevice is not directly seen by the guest, is not it? T
Testing of rcutorture's SRCU-P scenario on a large arm64 system resulted
in rcu_torture_writer() forward-progress failures, but these same tests
passed on x86. After some off-list discussion of possible memory-ordering
causes for these failures, Boqun showed that these were in fact due to
reorderi
On Fri, May 2, 2025 at 11:25 PM Peter Zijlstra wrote:
>
> Slight cleanup by using a for() loop instead of while(). This makes it
> clearer what is the iteration and what is the actual work done.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> scripts/mod/modpost.c |8 +++-
> 1 file cha
The rcu_torture_writer() function scans the memory blocks after a stutter
(or forced idle) interval, complaining about any that have not passed
through ten grace periods since the start of the stutter interval.
But one splat suffices, so this commit therefore stops at the first splat.
Signed-off-b
On kernels built with CONFIG_IRQ_WORK=y, when rcu_read_unlock() is
invoked within an interrupts-disabled region of code [1], it will invoke
rcu_read_unlock_special(), which uses an irq-work handler to force the
system to notice when the RCU read-side critical section actually ends.
That end won't h
The design of testing of up/down readers such as srcu_down_read()
and srcu_up_read() assumes that these are tested only by the
rcu_torture_updown() kthread, and never by the rcu_torture_reader()
kthread. Because we all know which road is paved with good intentions,
this commit adds WARN_ON_ONCE()
This commit prints the number of RCU up/down readers and the number
of such readers that migrated from one CPU to another, along
with the rest of the periodic rcu_torture_stats_print() output.
These statistics are currently used only by srcu_down_read{,_fast}()
and srcu_up_read(,_fast)().
Signed-o
Hello!
This series provides miscellaneous rcutorture updates:
1. Suppress torture.sh "Zero time" messages for disabled tests.
2. Print number of RCU up/down readers and migrations.
3. Check for no up/down readers at task level.
4. Start rcu_torture_writer() after rcu_tortur
The torture.sh script prints " --- Zero time for locktorture, disabling"
when the --duration parameter is too short to allow the test to run
even when locktorture has been disabled, for example, via --do-none.
The same is true for scftorture and rcutorture.
This commit therefore suppresses this me
On Thu, May 8, 2025 at 8:14 AM Sami Tolvanen wrote:
>
> Hi,
>
> While looking deeper into the genksyms hacks that have been
> needed during Android's 5.10 and 5.15 GKI lifecycles so far,
> we found a few instances that are not covered by the existing
> gendwarfksyms kABI stability rules. The first
Different architectures capitalize their splats differently. Who knew?
This commit therefore checks for both arm64 "Call trace:" and x86
"Call Trace:".
Reported-by: Joel Fernandes
Closes:
https://lore.kernel.org/all/553c33d8-2b51-4772-8aef-97b0163bc...@nvidia.com/
Signed-off-by: Paul E. McKenn
Back in the day, rcutorture was about the only thing that tested off-stack
CPU masks, but now any arm64 system with more than 256 CPUs tests it
full time. In fact, it is necessary to hack the kernel to prevent such
a system from testing off-stack CPU masks. This means that there is
no longer much
The TREE01.boot nr_cpus kernel boot parameter has been set to 43 for
more than seven years, but it can cause RCU CPU stall warnings on arm64,
most of the time involving the stop-machine subsystem. This should
not be too surprising, given that this causes 43 vCPUs to spin with
interrupts disabled w
Hello!
This series makes a few small updates to make rcutorture run better
on arm64 servers. Remaining issues include TREE07 .config issues
that are addressed by Mark Rutland's porting of PREEMPT_LAZY to arm64
and by upcoming work to handle the fact that arm64 kernels cannot be
built with CONFIG_
: 92a09c47464d040866cf2b4cd052bc60555185fb
patch link:
https://lore.kernel.org/r/20250507141712.4276-4-dawei.li%40linux.dev
patch subject: [PATCH 3/3] rpmsg: ctrl: Introduce RPMSG_CREATE_EPT_FD_IOCTL uAPI
config: i386-randconfig-011-20250508
(https://download.01.org/0day-ci/archive/20250509/202505090716.ib4qqaf2
Pages used by an enclave only get epc_page->poison set in
arch_memory_failure() but they currently stay on sgx_active_page_list until
sgx_encl_release(), with the SGX_EPC_PAGE_RECLAIMER_TRACKED flag untouched.
epc_page->poison is not checked in the reclaimer logic meaning that, if other
conditions
From: Ashish Kalra
During platform init, SNP initialization may fail for several reasons,
such as firmware command failures and incompatible versions. However,
the KVM capability may continue to advertise support for it.
The platform may have SNP enabled but if SNP_INIT fails then SNP is
not sup
Let's test some basic functionality using /dev/mem. These tests will
implicitly cover some PAT (Page Attribute Handling) handling on x86.
These tests will only run when /dev/mem access to the first two pages
in physical address space is possible and allowed; otherwise, the tests
are skipped.
On c
Fan Ni wrote:
> On Sun, Apr 13, 2025 at 05:52:10PM -0500, Ira Weiny wrote:
> > Devices which optionally support Dynamic Capacity (DC) are configured
> > via mailbox commands. CXL 3.2 section 9.13.3 requires the host to issue
> > the Get DC Configuration command in order to properly configure DCDs.
On Wed, May 07, 2025 at 07:26:05PM +0800, Zqiang wrote:
> In the preparation stage of CPU online, if the corresponding
> the rdp's->nocb_cb_kthread does not exist, will be created,
> there is a situation where the rdp's rcuop kthreads creation fails,
> and then de-offload this CPU's rdp, does not a
Hello,
On Thu, May 08, 2025 at 12:03:33PM +0200, Ulf Hansson wrote:
> On Wed, 7 May 2025 at 18:02, Hiago De Franco wrote:
> >
> > From: Hiago De Franco
> >
> > When the remote core is started before Linux boots (e.g., by the
> > bootloader), the driver currently is not able to attach because it
On Wed, May 07, 2025 at 02:14:00PM +0300, Elena Reshetova wrote:
> diff --git a/arch/x86/kernel/cpu/sgx/driver.c
> b/arch/x86/kernel/cpu/sgx/driver.c
> index 7f8d1e11dbee..669e44d61f9f 100644
> --- a/arch/x86/kernel/cpu/sgx/driver.c
> +++ b/arch/x86/kernel/cpu/sgx/driver.c
> @@ -19,6 +19,10 @@
On Sun, Apr 13, 2025 at 05:52:15PM -0500, Ira Weiny wrote:
> Dynamic Capacity CXL regions must allow memory to be added or removed
> dynamically. In addition to the quantity of memory available the
> location of the memory within a DC partition is dynamic based on the
> extents offered by a device
: 92a09c47464d040866cf2b4cd052bc60555185fb
patch link:
https://lore.kernel.org/r/20250507141712.4276-3-dawei.li%40linux.dev
patch subject: [PATCH 2/3] rpmsg: char: Implement eptdev based on anon inode
config: x86_64-randconfig-r052-20250508
(https://download.01.org/0day-ci/archive/20250509/202505090243.edaos4ug
On Sun, Apr 13, 2025 at 05:52:15PM -0500, Ira Weiny wrote:
> Dynamic Capacity CXL regions must allow memory to be added or removed
> dynamically. In addition to the quantity of memory available the
> location of the memory within a DC partition is dynamic based on the
> extents offered by a device
On Mon, Apr 14 2025 at 14:30, Frank Li wrote:
> This patches add new API to pci-epf-core, so any EP driver can use it.
> platform-msi: Add msi_remove_device_irq_domain() in
> platform_device_msi_free_irqs_all()
> irqdomain: Add IRQ_DOMAIN_FLAG_MSI_IMMUTABLE and
> irq_domain_is_msi_imm
On 5/7/25 12:26 PM, Lijuan Gao wrote:
> From: Kyle Deng
>
> The Shared Memory Point to Point (SMP2P) protocol facilitates
> communication of a single 32-bit value between two processors.
> Add these two nodes for remoteproc enablement on QCS615 SoC.
>
> Signed-off-by: Kyle Deng
> Signed-off-by:
Thank you very much for your detailed review, Dave!
Responses inline below.
> On 5/7/25 04:14, Elena Reshetova wrote:
> > In case an SGX vulnerability is discovered and TCB recovery
> > for SGX is triggered, Intel specifies a process that must be
> > followed for a given vulnerability. Steps to
On Fri, Apr 25, 2025 at 04:11:12PM +0530, Beleswar Padhi wrote:
> The mailbox .rx_callback implementations in TI K3 R5, DSP and M4
> remoteproc drivers handle inbound mailbox messages in the same way.
> Introduce a common driver 'ti_k3_common.c' and refactor the
> implementations into a common func
On 5/8/25 07:07, Reshetova, Elena wrote:
...
>> Actually, I think I wrote changelogs for this once upon a time. Could
>> you please go dig those up and use them?
>
> Could you please suggest where can I find them? Was it for the previous
> submission done by Cathy?
Yes. There were also some long
On Mon, May 5, 2025 at 6:39 PM Alexey Gladkov wrote:
>
> For some modules, modalias is generated using the modpost utility and
> the section is added to the module file.
>
> When a module is added inside vmlinux, modpost does not generate
> modalias for such modules and the information is lost.
>
On 5/8/25 08:04, Sean Christopherson wrote:
On Wed, May 07, 2025, Shuah Khan wrote:
The issues Peter is seeing regarding KHDR_INCLUDES in the following
tests can be easily fixed by simply changing the test Makefile. These
aren't framework related.
kvm/Makefile.kvm:-I ../rseq -I.. $(EXTRA_CF
Makes the display work without clk_ignore_unused and pd_ignore_unused.
Signed-off-by: Stanislav Jakubek
---
arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/qcom/msm8226-motorola-falcon.dts
b/arch/arm/boot/dts/qcom
While the currently supported hardware works fine with the default clock
frequencies of 10 on both I2C2 and I2C3, downstream sources list the
frequencies as 10 for I2C2 and 40 for I2C3. Update them as such.
Signed-off-by: Stanislav Jakubek
---
arch/arm/boot/dts/qcom/msm8226-motorola-
On 5/7/25 12:26 PM, Lijuan Gao wrote:
> Add nodes for remoteprocs: ADSP and CDSP for QCS615 SoC to enable proper
> remoteproc functionality.
>
> Signed-off-by: Lijuan Gao
> ---
Reviewed-by: Konrad Dybcio
Konrad
From: Stefano Garzarella
When the other peer calls shutdown(SHUT_RD), there is a chance that
the send() call could occur before the message carrying the close
information arrives over the transport. In such cases, the send()
might still succeed. To avoid this race, let's retry the send() call
a f
On 5/8/25 4:11 PM, Stanislav Jakubek wrote:
> While the currently supported hardware works fine with the default clock
> frequencies of 10 on both I2C2 and I2C3, downstream sources list the
> frequencies as 10 for I2C2 and 40 for I2C3. Update them as such.
>
> Signed-off-by: Stanislav
On 5/7/25 12:26 PM, Lijuan Gao wrote:
> Enable all remoteproc nodes on the qcs615-ride board and point to the
> appropriate firmware files to allow proper functioning of the remote
> processors.
>
> Signed-off-by: Lijuan Gao
> ---
Reviewed-by: Konrad Dybcio
Konrad
On 5/7/25 12:26 PM, Lijuan Gao wrote:
> Add a simple-mfd representing IMEM on QCS615 and define the PIL
> relocation info region as its child. The PIL region in IMEM is used to
> communicate load addresses of remoteproc to post mortem debug tools, so
> that these tools can collect ramdumps.
>
> Si
Running the tests continuously I noticed that sometimes the sigpipe
test would fail due to a race between the control message of the test
and the vsock transport messages.
While I was at it I also improved the test by checking the errno we
expect.
Stefano Garzarella (2):
vsock/test: retry send(
On 5/8/25 4:11 PM, Stanislav Jakubek wrote:
> After some digging in downstream sources, it was found that the TPS65132
> outputs are fixed to +5.4V and -5.4V respectively. This is further confirmed
> on runtime through debugfs, the troubleshooting guide confirms this as well.
> Specify these limits
On 5/8/25 4:11 PM, Stanislav Jakubek wrote:
> Makes the display work without clk_ignore_unused and pd_ignore_unused.
>
> Signed-off-by: Stanislav Jakubek
> ---
Reviewed-by: Konrad Dybcio
Konrad
On 5/8/25 4:11 PM, Stanislav Jakubek wrote:
> After some digging in downstream sources, it was found that the vddio_disp
> regulator's output voltage is 1.8V. This is further confirmed by the
> troubleshooting guide. Specify its output voltage as such.
> While at it, add a comment specifying the IC
From: Stefano Garzarella
In the sigpipe test, we expect send() to fail, but we do not check if
send() fails with the errno we expect (EPIPE).
Add this check and repeat the send() in case of EINTR as we do in other
tests.
Signed-off-by: Stefano Garzarella
---
tools/testing/vsock/vsock_test.c |
After some digging in downstream sources, it was found that the vddio_disp
regulator's output voltage is 1.8V. This is further confirmed by the
troubleshooting guide. Specify its output voltage as such.
While at it, add a comment specifying the IC, which according to the
schematic is the TI TPS2290
After some digging in downstream sources, it was found that the TPS65132
outputs are fixed to +5.4V and -5.4V respectively. This is further confirmed
on runtime through debugfs, the troubleshooting guide confirms this as well.
Specify these limits as such.
Signed-off-by: Stanislav Jakubek
---
ar
This series improves the accuracy of motorola-falcon's DTS.
As a side note, I wanted to ask how to describe the Hall effect sensor's
vdd-supply. The sensor's currently described as part of the gpio-keys node.
According to the schematic it's powered by pm8226_lvs1, but I don't see a way
to describe
On Wed, May 07, 2025, Shuah Khan wrote:
> The issues Peter is seeing regarding KHDR_INCLUDES in the following
> tests can be easily fixed by simply changing the test Makefile. These
> aren't framework related.
>
> kvm/Makefile.kvm:-I ../rseq -I.. $(EXTRA_CFLAGS) $(KHDR_INCLUDES)
...
> You ca
> On May 8, 2025, at 9:42 AM, Willem de Bruijn
> wrote:
>
>
> Jon Kohler wrote:
>>
>>
>>> On May 7, 2025, at 1:23 PM, Willem de Bruijn
>>> wrote:
>>>
>
> Minor: can you fix email to avoid the above?
I think its a corporate email thing, but good reminder, ill clip it out in
future
resp
Jon Kohler wrote:
>
>
> > On May 7, 2025, at 1:23 PM, Willem de Bruijn
> > wrote:
> >
> > !---|
> > CAUTION: External Email
> >
> > |---!
> >
Minor: can you fix e
>
> On Thu, May 8, 2025 at 12:25 AM Frederic Weisbecker
> wrote:
> >
> > Le Wed, May 07, 2025 at 07:26:04PM +0800, Zqiang a écrit :
> > > For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
> > > Disable BH does not change the SOFTIRQ corresponding bits in
> > > preempt_count(), bu
://lore.kernel.org/r/20250507160206.3267692-1-jon%40nutanix.com
patch subject: [PATCH net-next] vhost/net: align variable names with XDP
terminology
config: x86_64-kexec
(https://download.01.org/0day-ci/archive/20250508/202505081920.fooj1z0e-...@intel.com/config)
compiler: clang version 20.1.2 (https
PCI region request functions such as pci_request_region() currently have
the problem of becoming sometimes managed functions, if
pcim_enable_device() instead of pci_enable_device() was called. The PCI
subsystem wants to remove this deprecated behavior from its interfaces.
octeopn_ep enables its de
On Wed, 7 May 2025 at 18:02, Hiago De Franco wrote:
>
> From: Hiago De Franco
>
> When the remote core is started before Linux boots (e.g., by the
> bootloader), the driver currently is not able to attach because it only
> checks for cores running in different partitions. If the core was kicked
>
On 4/22/2025 10:55 PM, David Hildenbrand wrote:
> On 10.04.25 10:41, Christoph Hellwig wrote:
>> On Tue, Apr 08, 2025 at 11:23:57AM +, Shivank Garg wrote:
>>> KVM guest_memfd is implementing its own inodes to store metadata for
>>> backing memory using a custom filesystem. This requires the a
60 matches
Mail list logo
