On Mon, May 19, 2025 at 03:06:48PM +0800, Xuewei Niu wrote:
The virtio_vsock_sock has a new field called bytes_unread as the return
value of the SIOCINQ ioctl.
Though the rx_bytes exists, we introduce a bytes_unread field to the
virtio_vsock_sock struct. The reason is that it will not be updated
On Mon, May 12, 2025 at 02:23:12PM +0200, Michal Luczaj wrote:
On 5/7/25 10:26, Stefano Garzarella wrote:
On Wed, 7 May 2025 at 00:47, Michal Luczaj wrote:
On 5/6/25 11:46, Stefano Garzarella wrote:
On Tue, 6 May 2025 at 11:43, Stefano Garzarella wrote:
On Thu, May 01, 2025 at 10:05:24AM
On Tue, 20 May 2025 at 10:54, Stefano Garzarella wrote:
>
> On Mon, May 12, 2025 at 02:23:12PM +0200, Michal Luczaj wrote:
> >On 5/7/25 10:26, Stefano Garzarella wrote:
> >> On Wed, 7 May 2025 at 00:47, Michal Luczaj wrote:
> >>>
> >>> On 5/6/25 11:46, Stefano Garzarella wrote:
> On Tue, 6 M
On 17/05/2025 14:23, Beleswar Prasad Padhi wrote:
On 5/16/2025 9:15 PM, Mathieu Poirier wrote:
On Tue, May 13, 2025 at 11:14:38AM +0530, Beleswar Padhi wrote:
The rproc_detach() function invokes __rproc_detach() before
rproc_unprepare_device(). The __rproc_detach() function sets the
rproc->
* Reshetova, Elena wrote:
> > > Yes, meaning is different, see above.
> >
> > So that's rather convoluted:
> >
> > atomic64_inc_not_zero(): returns 1 on successful increase, 0 on
> > failure
> > sgx_inc_usage_count(): returns 0 on successful increase, 1 on
> > failure
> >
On Mon May 19, 2025 at 1:50 PM UTC, Ujwal Kundur wrote:
> Thanks for the review and testing!
>
>>> -static void retry_copy_page(int ufd, struct uffdio_copy *uffdio_copy,
>>> - unsigned long offset)
>>> +static void retry_copy_page(uffd_global_test_opts_t *gopts, struct
>>>
On Mon, May 19, 2025 at 03:06:49PM +0800, Xuewei Niu wrote:
This patch adds two tests for ioctl SIOCINQ for SOCK_STREAM and
SOCK_SEQPACKET. The client waits for the server to send data, and checks if
the return value of the SIOCINQ is the size of the data. Then, consumes the
data and checks if th
On Tue, 2025-05-20 at 06:36 +, Reshetova, Elena wrote:
> > >
> > > > Why not just fail sgx_open() (e.g., return -EBUSY, or -EAGAIN) in that
> > > > case?
> > > > Userspace can then retry?
> > >
> > > The idea on the patch was that such a scenario where we run out of entropy
> > > should not
On 5/19/25 11:35 AM, Johan Hovold wrote:
> On Sat, May 17, 2025 at 07:27:49PM +0200, Konrad Dybcio wrote:
>> SC8280XP features a SLPI, much like its distant relative, SM8350.
>
> Please get into the habit of spelling out *and* explaining internal
> Qualcomm acronyms like "SLPI" so that your cover
On Fri, May 16, 2025 at 06:59:37PM -0700, Sumanth Gavini wrote:
> Fix misspelling reported by codespell
>
> Signed-off-by: Sumanth Gavini
Thanks,
With this change this file appears to be codespell-clean.
Reviewed-by: Simon Horman
On 20/05/2025 17:29, Konrad Dybcio wrote:
On 5/19/25 11:35 AM, Johan Hovold wrote:
On Sat, May 17, 2025 at 07:27:49PM +0200, Konrad Dybcio wrote:
Konrad Dybcio (4):
dt-bindings: remoteproc: qcom,sm8350-pas: Add SC8280XP
arm64: dts: qcom: sc8280xp: Fix node order
arm64:
On Mon, May 19, 2025 at 02:41:06PM +0100, Mark Rutland wrote:
> I've pushed a arm64/stacktrace-updates branch [1] with fixups for those
> as two separate commits atop this one. If that looks good to you I
> suggest we post that as a series and ask Will and Catalin to take that
> as-is.
Yes, please
On 2025-05-20 09:06:57 [+0100], Colin Ian King wrote:
> There is a spelling mistake in a fail error message. Fix it.
>
> Signed-off-by: Colin Ian King
Reviewed-by: Sebastian Andrzej Siewior
Sebastian
I'd like to cut down the memory usage of parsing vmlinux BTF in ebpf-go.
With some upcoming changes the library is sitting at 5MiB for a parse.
Most of that memory is simply copying the BTF blob into user space.
By allowing vmlinux BTF to be mmapped read-only into user space I can
cut memory usage
User space needs access to kernel BTF for many modern features of BPF.
Right now each process needs to read the BTF blob either in pieces or
as a whole. Allow mmaping the sysfs file so that processes can directly
access the memory allocated for it in the kernel.
remap_pfn_range is used instead of
Teach libbpf to use mmap when parsing vmlinux BTF from /sys. We don't
apply this to fall-back paths on the regular file system because there
is no way to ensure that modifications underlying the MAP_PRIVATE
mapping are not visible to the process.
Acked-by: Andrii Nakryiko
Tested-by: Alan Maguire
Add a basic test for the ability to mmap /sys/kernel/btf/vmlinux.
Ensure that the data is valid BTF and that it is padded with zero.
Tested-by: Alan Maguire
Signed-off-by: Lorenz Bauer
---
tools/testing/selftests/bpf/prog_tests/btf_sysfs.c | 81 ++
1 file changed, 81 inserti
On Tue, May 20, 2025 at 12:58:18PM +0200, Paolo Abeni wrote:
> On 5/20/25 10:24 AM, Stefano Garzarella wrote:
>
> https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style
>
> @Bobby: AFAICS this now has all the ingredients to fit NIPA integration
> am I correct? the last com
On Tue, May 20, 2025 at 01:09:25PM +0200, Stefano Garzarella wrote:
> On Tue, May 20, 2025 at 12:58:18PM +0200, Paolo Abeni wrote:
> > On 5/20/25 10:24 AM, Stefano Garzarella wrote:
> >
> > Still it could be worthy to re-introduce (behind a command line option)
> > the ability to build the kernel
On 2025-05-19 2:58 a.m., Namhyung Kim wrote:
> Hello,
>
> On Mon, Mar 24, 2025 at 05:30:44PM +, Mingwei Zhang wrote:
>> From: Kan Liang
>>
>> Current perf doesn't explicitly schedule out all exclude_guest events
>> while the guest is running. There is no problem with the current
>> emulate
On Tue, May 20, 2025 at 03:28:45PM +0100, Will Deacon wrote:
> On Mon, May 19, 2025 at 02:41:06PM +0100, Mark Rutland wrote:
> > I've pushed a arm64/stacktrace-updates branch [1] with fixups for those
> > as two separate commits atop this one. If that looks good to you I
> > suggest we post that as
On Tue, 20 May 2025 at 11:01, Stefano Garzarella wrote:
>
> On Tue, 20 May 2025 at 10:54, Stefano Garzarella wrote:
> >
> > On Mon, May 12, 2025 at 02:23:12PM +0200, Michal Luczaj wrote:
> > >On 5/7/25 10:26, Stefano Garzarella wrote:
> > >> On Wed, 7 May 2025 at 00:47, Michal Luczaj wrote:
> >
On Tue, May 20, 2025 at 12:09:02PM -0400, Liang, Kan wrote:
>
>
> On 2025-05-19 2:58 a.m., Namhyung Kim wrote:
> > Hello,
> >
> > On Mon, Mar 24, 2025 at 05:30:44PM +, Mingwei Zhang wrote:
> >> From: Kan Liang
> >>
> >> Current perf doesn't explicitly schedule out all exclude_guest events
>
On Tue, May 20, 2025 at 08:23:02PM +0100, Bryan O'Donoghue wrote:
> On 20/05/2025 19:39, Vincent Knecht via B4 Relay wrote:
> > From: Vincent Knecht
>
> > + compatible = "qcom,msm8939-camss";
> > + reg = <0x01b0ac00 0x200>,
> <0x01b0ac00 0x0 0x200 0x0>
No.
On Tue, May 20, 2025 at 06:25:04AM +, Reshetova, Elena wrote:
> > Maybe just use raw atomic_inc() and atomic_dec() at the sites?
> >
> > IMHO, it makes only sense to wrap, when it makes sense to wrap.
>
> You mean for this patch or overall? For overall we discussed in v4
> why we would like t
On 5/20/25 12:57, Jarkko Sakkinen wrote:
> unlikely() is both (minor) optimization and documents that it is not expected
> branch so it obviously makes sense here.
I'm not a big fan of unlikely() being thrown in without specific
reasons. I don't think we need an annotation to tell us that the path
On Tue, May 20, 2025 at 06:31:46AM +, Reshetova, Elena wrote:
BTW, please keep the line which tells who responded.
> > +/**
> > > + * sgx_updatesvn() - Attempt to call ENCLS[EUPDATESVN]
> > > + * If EPC is empty, this instruction attempts to update CPUSVN to the
> > > + * currently loaded mi
On 20/05/2025 19:39, Vincent Knecht via B4 Relay wrote:
From: Vincent Knecht
Add the camera subsystem and CCI used to interface with cameras on the
Snapdragon 615.
Signed-off-by: Vincent Knecht
---
arch/arm64/boot/dts/qcom/msm8939-pm8916.dtsi | 4 +
arch/arm64/boot/dts/qcom/msm8939.dtsi
On 5/20/25 8:39 PM, Vincent Knecht via B4 Relay wrote:
> From: Vincent Knecht
>
> Add the camera subsystem and CCI used to interface with cameras on the
> Snapdragon 615.
>
> Signed-off-by: Vincent Knecht
> ---
[...]
> + interrupts = ,
> +
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Fri, 16 May 2025 16:22:05 -0700 you wrote:
> Cover three recent cases:
> 1. missing ops locking for the lowers during netdev_sync_lower_features
> 2. missing locking for dev_set_promiscuity (plus netdev_ops_assert_
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Fri, 16 May 2025 18:59:37 -0700 you wrote:
> Fix misspelling reported by codespell
>
> Signed-off-by: Sumanth Gavini
> ---
> tools/testing/selftests/nci/nci_dev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 dele
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Fri, 16 May 2025 20:25:33 -0700 you wrote:
> Fix "withouth" to "without"
> Fix "instaces" to "instances"
>
> Signed-off-by: Sumanth Gavini
> ---
> tools/testing/selftests/net/srv6_end_flavors_test.sh | 4 ++--
>
> On Mon, May 19, 2025 at 03:06:46PM +0800, Xuewei Niu wrote:
> >This patchset introduces SIOCINQ ioctl support for vsock, indicating the
> >number of unread bytes.
>
> Thanks for this work, but please use net-next tree since this is a new
> feature:
> https://www.kernel.org/doc/html/latest/proc
> On Mon, May 19, 2025 at 03:06:49PM +0800, Xuewei Niu wrote:
> >This patch adds two tests for ioctl SIOCINQ for SOCK_STREAM and
> >SOCK_SEQPACKET. The client waits for the server to send data, and checks if
> >the return value of the SIOCINQ is the size of the data. Then, consumes the
> >data and
> On Mon, May 19, 2025 at 03:06:48PM +0800, Xuewei Niu wrote:
> >The virtio_vsock_sock has a new field called bytes_unread as the return
> >value of the SIOCINQ ioctl.
> >
> >Though the rx_bytes exists, we introduce a bytes_unread field to the
> >virtio_vsock_sock struct. The reason is that it will
On 5/19/25 3:04 AM, Matthieu Baerts wrote:
+SEC("cgroup/getsockopt")
+int iters_subflow(struct bpf_sockopt *ctx)
+{
+ struct mptcp_subflow_context *subflow;
+ struct bpf_sock *sk = ctx->sk;
+ struct sock *ssk = NULL;
+ struct mptcp_sock *msk;
+ int local_ids = 0;
+
+ if (ctx->le
Lingering should be transport-independent in the long run. In preparation
for supporting other transports, as well as the linger on shutdown(), move
code to core.
Generalize by querying vsock_transport::unsent_bytes(), guard against the
callback being unimplemented. Do not pass sk_lingertime expli
Change vsock's lingerning to wait on close() until all data is sent, i.e.
until workers picked all the packets for processing.
Changes in v5:
- Move unsent_bytes fetching logic to utils.c
- Add a helper for enabling SO_LINGER
- Accommodate for close() taking a long time for reasons unrelated to
Currently vsock's lingering effectively boils down to waiting (or timing
out) until packets are consumed or dropped by the peer; be it by receiving
the data, closing or shutting down the connection.
To align with the semantics described in the SO_LINGER section of man
socket(7) and to mimic AF_INE
Distill the virtio_vsock_sock::bytes_unsent checking loop (ioctl SIOCOUTQ)
and move it to utils. Tweak the comment.
Signed-off-by: Michal Luczaj
---
tools/testing/vsock/util.c | 25 +
tools/testing/vsock/util.h | 1 +
tools/testing/vsock/vsock_test.c | 23 +++
Add a helper function that sets SO_LINGER. Adapt the caller.
Signed-off-by: Michal Luczaj
---
tools/testing/vsock/util.c | 13 +
tools/testing/vsock/util.h | 4
tools/testing/vsock/vsock_test.c | 10 +-
3 files changed, 18 insertions(+), 9 deletions(-)
diff
There was an issue with SO_LINGER: instead of blocking until all queued
messages for the socket have been successfully sent (or the linger timeout
has been reached), close() would block until packets were handled by the
peer.
Add a test to alert on close() lingering when it should not.
Signed-off
On Thu, May 15, 2025 at 08:51:45AM +0100, Alan Maguire wrote:
> > I'd like to cut down the memory usage of parsing vmlinux BTF in ebpf-go.
> > With some upcoming changes the library is sitting at 5MiB for a parse.
> > Most of that memory is simply copying the BTF blob into user space.
> > By allowi
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
tags/rproc-v6.15-fixes
for you to fetch changes up to 4ca45
The pull request you sent on Tue, 20 May 2025 21:41:51 -0500:
> https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git
> tags/rproc-v6.15-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4a95bc121ccdaee04c4d72f84dbfa6b880a514b6
Thank you!
--
Deet-
Hi Ulf,
On Tue, May 20, 2025 at 02:21:49PM +0200, Ulf Hansson wrote:
>On Mon, 19 May 2025 at 19:24, Hiago De Franco wrote:
>>
>> Hi Ulf,
>>
>> On Mon, May 19, 2025 at 04:33:30PM +0200, Ulf Hansson wrote:
>> > On Fri, 9 May 2025 at 21:13, Hiago De Franco wrote:
>> > >
>> > > On Fri, May 09, 2025
On Wed, May 21, 2025 at 12:13:06PM +0800, Peng Fan wrote:
>Hi Ulf,
>
>On Tue, May 20, 2025 at 02:21:49PM +0200, Ulf Hansson wrote:
>>On Mon, 19 May 2025 at 19:24, Hiago De Franco wrote:
>>>
>>> Hi Ulf,
>>>
>>> On Mon, May 19, 2025 at 04:33:30PM +0200, Ulf Hansson wrote:
>>> > On Fri, 9 May 2025 at
On Mon, May 19, 2025 at 02:15:11PM -0300, Hiago De Franco wrote:
>From: Hiago De Franco
Let's wait for V2 discussion a bit, then I will give a look if we reach
an agreement on using firmware power API here.
Thanks,
Peng
There is a spelling mistake in a fail error message. Fix it.
Signed-off-by: Colin Ian King
---
tools/testing/selftests/futex/functional/futex_numa_mpol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/futex/functional/futex_numa_mpol.c
b/tools/testin
On 5/20/25 10:24 AM, Stefano Garzarella wrote:
> On Thu, May 15, 2025 at 03:00:48PM -0700, Bobby Eshleman wrote:
>> This commit introduces a new vmtest.sh runner for vsock.
>>
>> It uses virtme-ng/qemu to run tests in a VM. The tests validate G2H,
>> H2G, and loopback. The testing tools from tools/
On Mon, May 19, 2025 at 03:06:46PM +0800, Xuewei Niu wrote:
This patchset introduces SIOCINQ ioctl support for vsock, indicating the
number of unread bytes.
Thanks for this work, but please use net-next tree since this is a new
feature:
https://www.kernel.org/doc/html/latest/process/maintaine
On Tue, May 20, 2025 at 12:58:18PM +0200, Paolo Abeni wrote:
On 5/20/25 10:24 AM, Stefano Garzarella wrote:
On Thu, May 15, 2025 at 03:00:48PM -0700, Bobby Eshleman wrote:
This commit introduces a new vmtest.sh runner for vsock.
It uses virtme-ng/qemu to run tests in a VM. The tests validate G
On 5/16/25 12:00 AM, Bobby Eshleman wrote:
> +tap_prefix() {
> + sed -e "s/^/${TAP_PREFIX}/"
> +}
I think there is no need to the tap prefix to the output you intend to
'comment out', the kselftest infra should already add the tap prefix
mark to each line generated by the test,
> +
> +tap_out
On Thu, May 15, 2025 at 03:00:48PM -0700, Bobby Eshleman wrote:
This commit introduces a new vmtest.sh runner for vsock.
It uses virtme-ng/qemu to run tests in a VM. The tests validate G2H,
H2G, and loopback. The testing tools from tools/testing/vsock/ are
reused. Currently, only vsock_test is u
On 2025-05-16 19:06:31+, Rae Moar wrote:
> -Alternatively, you could conditionally ``#include`` the test file at the end
> of
> -your .c file. For example:
> + /* In the KUnit test file "my_file_test.c" */
> +
> + #include
> + #include
> + ...
> + MODULE_IMPORT_NS(EXPO
On 2025-05-16 20:16:15+, Rae Moar wrote:
> test_group = {
> "name": test.name,
> "sub_groups": sub_groups,
> "test_cases": test_cases,
> + "misc": counts_json
Should have a trailing comma for future extensibility.
In case history is
On Mon, 19 May 2025 at 19:24, Hiago De Franco wrote:
>
> Hi Ulf,
>
> On Mon, May 19, 2025 at 04:33:30PM +0200, Ulf Hansson wrote:
> > On Fri, 9 May 2025 at 21:13, Hiago De Franco wrote:
> > >
> > > On Fri, May 09, 2025 at 12:37:02PM +0200, Ulf Hansson wrote:
> > > > On Thu, 8 May 2025 at 22:28, H
On 5/20/25 00:06, Beleswar Prasad Padhi wrote:
Hi Mathieu,
On 19/05/25 20:07, Mathieu Poirier wrote:
On Sat, May 17, 2025 at 06:53:29PM +0530, Beleswar Prasad Padhi wrote:
On 5/16/2025 9:15 PM, Mathieu Poirier wrote:
On Tue, May 13, 2025 at 11:14:38AM +0530, Beleswar Padhi wrote:
The rproc_d
From: Vincent Knecht
Add bindings for qcom,msm8939-camss in order to support the camera
subsystem for MSM8939.
Signed-off-by: Vincent Knecht
---
.../bindings/media/qcom,msm8939-camss.yaml | 269 +
1 file changed, 269 insertions(+)
diff --git a/Documentation/devicet
From: Vincent Knecht
The camera subsystem for the MSM8939 is the same as MSM8916 except with
3 CSID instead of 2, and some higher clock rates.
As a quirk, this SoC needs writing values to 2 VFE VBIF registers
(see downstream msm8939-camera.dtsi vbif-{regs,settings} properties).
This fixes black
From: Vincent Knecht
Some devices need writing values to VFE VBIF registers.
Add helper functions to do this.
Signed-off-by: Vincent Knecht
---
drivers/media/platform/qcom/camss/Makefile | 1 +
drivers/media/platform/qcom/camss/camss-vfe-vbif.c | 30 ++
drivers/med
From: Vincent Knecht
Add the camera subsystem and CCI used to interface with cameras on the
Snapdragon 615.
Signed-off-by: Vincent Knecht
---
arch/arm64/boot/dts/qcom/msm8939-pm8916.dtsi | 4 +
arch/arm64/boot/dts/qcom/msm8939.dtsi| 152 +++
2 files changed, 1
This series adds CAMSS support for MSM8939.
It's mostly identical to MSM8916, except for some clocks
and an additional CSI.
To fix black stripes across sensor output, and garbage in
CSID TPG output, 2 VFE VBIF register settings are needed.
So the 1st patch adds helper functions to do just that.
P
Add the test counts to the JSON output from kunit.py. For example:
...
"git_branch": "kselftest",
"misc":
{
"tests": 2,
"passed": 1.
"failed": 1,
"crashed": 0,
"skipped": 0,
"errors": 0,
}
...
To output the JSON using the following command:
./tools/testing/kunit/kunit.py r
On Tue, May 20, 2025 at 08:39:07PM +0200, Vincent Knecht via B4 Relay wrote:
> From: Vincent Knecht
>
> The camera subsystem for the MSM8939 is the same as MSM8916 except with
> 3 CSID instead of 2, and some higher clock rates.
>
> As a quirk, this SoC needs writing values to 2 VFE VBIF register
On Tue, May 20, 2025 at 10:30:30PM +0300, Vladimir Zapolskiy wrote:
> Hello Vincent.
>
> On 5/20/25 21:39, Vincent Knecht via B4 Relay wrote:
> > From: Vincent Knecht
> >
> > Add the camera subsystem and CCI used to interface with cameras on the
> > Snapdragon 615.
> >
> > Signed-off-by: Vincen
The documentation on testing static functions using the KUnit macros
VISIBLE_IF_KUNIT and EXPORT_SYMBOL_IF_KUNIT is lacking clarity and
missing key steps in the example. This has caused bugs and confusion
among developers.
Improve wording of description and add missing steps to the example.
This e
On Fri, 16 May 2025 18:17:22 -0700, Sumanth Gavini wrote:
> Fix misspelling reported by codespell
>
>
Applied to for-next/seccomp, thanks!
[1/1] selftests: seccomp: Fix "performace" to "performance"
https://git.kernel.org/kees/c/a9b33aae79ce
Take care,
--
Kees Cook
On 20/05/2025 20:53, Dmitry Baryshkov wrote:
<0x01b0ac00 0x0 0x200 0x0>
No.
Ah you're right I see we are only doing this for new SoCs.
---
bod
On Fri, 2025-05-16 at 13:13 +0800, Li Zhijian wrote:
> kmemleak reported a memleak after the ndctl_test
> unreferenced object 0x88800e6cf2c0 (size 32):
> comm "modprobe", pid 969, jiffies 4294698691
> hex dump (first 32 bytes):
> 03 00 00 00 a0 0a 00 00 00 b0 b4 00 00 c9 ff ff
On Fri, 2025-05-16 at 13:13 +0800, Li Zhijian wrote:
> Call free_arenas() to release the arena instances in btt->arena_list
> in the error paths.
>
> Signed-off-by: Li Zhijian
> ---
> drivers/nvdimm/btt.c | 12
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
Reviewed-by: Vishal
This patch adds a new robust_list() syscall. The current syscall
can't be expanded to cover the following use case, so a new one is
needed. This new syscall allows users to set multiple robust lists per
process and to have either 32bit or 64bit pointers in the list.
* Use case
FEX-Emu[1] is an ap
Create a test for the robust list mechanism. Test the following uAPI
operations:
- Creating a robust mutex where the lock waiter is wake by the kernel
when the lock owner died
- Setting a robust list to the current task
- Getting a robust list from the current task
- Getting a robust list from a
There are two functions for handling robust lists during the task
exit: exit_robust_list() and compat_exit_robust_list(). The first one
handles either 64bit or 32bit lists, depending if it's a 64bit or 32bit
kernel. The compat_exit_robust_list() only exists in 64bit kernels that
supports 32bit sysc
Create ASSERT_{EQ, NE, TRUE, FALSE} macros to make test creation easier.
Signed-off-by: André Almeida
---
tools/testing/selftests/futex/include/logging.h | 38 +
1 file changed, 38 insertions(+)
diff --git a/tools/testing/selftests/futex/include/logging.h
b/tools/testin
sendmsg() with a single iov becomes ITER_UBUF, sendmsg() with multiple
iovs becomes ITER_IOVEC. iter_iov_len does not return correct
value for UBUF, so teach to treat UBUF differently.
Cc: Al Viro
Cc: Pavel Begunkov
Cc: Mina Almasry
Fixes: bd61848900bf ("net: devmem: Implement TX path")
Signed-
Add new -z argument to specify max IOV size. By default, use
single large IOV.
Signed-off-by: Stanislav Fomichev
---
.../selftests/drivers/net/hw/ncdevmem.c | 49 +++
1 file changed, 29 insertions(+), 20 deletions(-)
diff --git a/tools/testing/selftests/drivers/net/hw/ncde
Use prime 3 for length to make offset slowly drift away.
Signed-off-by: Stanislav Fomichev
---
.../testing/selftests/drivers/net/hw/devmem.py | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/drivers/net/hw/devmem.py
b/tools/testing/s
Wire up the new set_robust_list2 syscall in all available architectures.
Signed-off-by: André Almeida
---
arch/alpha/kernel/syscalls/syscall.tbl | 1 +
arch/arm/tools/syscall.tbl | 1 +
arch/m68k/kernel/syscalls/syscall.tbl | 1 +
arch/microblaze/kernel/syscalls/sysca
Remove the limit of ROBUST_LIST_LIMIT elements that a robust list can
have, for the ones created with the new interface. This is done by
overwritten the list as it's proceeded in a way that we avoid circular
lists.
For the old interface, we keep the limited behavior to avoid changing
the API.
Sig
Create a new robust_list() syscall. The current syscall can't be
expanded to cover the following use case, so a new one is needed. This
new syscall allows users to set multiple robust lists per process and to
have either 32bit or 64bit pointers in the list.
* Interface
This is the proposed interf
Expand the current robust list test for the new set_robust_list2
syscall. Create an option to make it possible to run the same tests
using the new syscall, and also add two new relevant test: test long
lists (bigger than ROBUST_LIST_LIMIT) and for unaligned addresses.
Signed-off-by: André Almeida
On Tue, May 20, 2025 at 04:51:42PM +0100, Conor Dooley wrote:
> On Mon, May 19, 2025 at 07:22:21PM -0700, Drew Fustini wrote:
> > On Mon, May 19, 2025 at 07:14:40PM -0700, Drew Fustini wrote:
> > > Convert the PMEM device tree binding from text to YAML. This will allow
> > > device trees with pmem-
orrect base, please add 'base-commit' tag
(or use b4 which does this automatically)
New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for
20250520-camss-8x39-vbif-v1-0-a12cd6006...@mailoo.org:
arch/arm64/boot/dts/qcom/msm8939-wingtech-wt82918.dtb: cci@1b
A long-term goal is supporting frozen PageOffline pages, and later
PageOffline pages that don't have a refcount at all. Some more work for
that is needed -- in particular around non-folio page migration and
memory ballooning drivers -- but let's start by handling PageOffline pages
that can be skipp
This is a requirement for making PageOffline pages not have a refcount
in the long future ("frozen"), and for reworking non-folio page migration
in the near future.
I have patches mostly ready to go to handle the latter. For turning all
PageOffline() pages frozen, the non-folio page migration and
On Tue, May 20, 2025 at 01:24:43PM +0200, Paolo Abeni wrote:
> On 5/16/25 12:00 AM, Bobby Eshleman wrote:
> > +tap_prefix() {
> > + sed -e "s/^/${TAP_PREFIX}/"
> > +}
>
> I think there is no need to the tap prefix to the output you intend to
> 'comment out', the kselftest infra should already ad
On Mon, May 19, 2025 at 07:22:21PM -0700, Drew Fustini wrote:
> On Mon, May 19, 2025 at 07:14:40PM -0700, Drew Fustini wrote:
> > Convert the PMEM device tree binding from text to YAML. This will allow
> > device trees with pmem-region nodes to pass dtbs_check.
> >
> > Signed-off-by: Drew Fustini
On Tue, May 13, 2025 at 11:14:34AM +0530, Beleswar Padhi wrote:
> This series refactors a lot of functions & callbacks from
> ti_k3_dsp_remoteproc.c, ti_k3_r5_remoteproc.c and ti_k3_m4_remoteproc.c
> drivers. This is a consolidated and final series as part of the
> refactoring of K3 remoteproc driv
On 20/05/2025 19:39, Vincent Knecht via B4 Relay wrote:
+static const struct camss_subdev_resources csiphy_res_8x39[] = {
+ /* CSIPHY0 */
+ {
+ .regulators = {},
Regulators should be declared with the PHY not the CSID.
---
bod
On 20/05/2025 19:39, Vincent Knecht via B4 Relay wrote:
From: Vincent Knecht
Add bindings for qcom,msm8939-camss in order to support the camera
subsystem for MSM8939.
Signed-off-by: Vincent Knecht
---
.../bindings/media/qcom,msm8939-camss.yaml | 269 +
1 file ch
Hello Vincent.
On 5/20/25 21:39, Vincent Knecht via B4 Relay wrote:
From: Vincent Knecht
Add the camera subsystem and CCI used to interface with cameras on the
Snapdragon 615.
Signed-off-by: Vincent Knecht
---
arch/arm64/boot/dts/qcom/msm8939-pm8916.dtsi | 4 +
arch/arm64/boot/dts/qcom/
On 2025-05-20 1:51 p.m., Namhyung Kim wrote:
@@ -1089,6 +1094,7 @@ struct bpf_perf_event_data_kern {
*/
struct perf_cgroup_info {
struct perf_time_ctxtime;
+ struct perf_time_ctxtimeguest;
int active;
>>>
The pidfd_test suite currently defines six test functions,
four of which return an int, while the remaining
two return void. This is inconsistent.
To address this, convert the two void-returning test
functions to return int, bringing them in line with
the rest. For now, the functions always return
Fix typos in comments in pidfd_info_test.c
Signed-off-by: Ivan Pravdin
---
tools/testing/selftests/pidfd/pidfd_info_test.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/pidfd/pidfd_info_test.c
b/tools/testing/selftests/pidfd/pidfd_info_test.c
95 matches
Mail list logo
