The VHOST_[GS]ET_FEATURES_ARRAY ioctl already took 0x83 and it would
result in a build error when the vhost uapi header is used for perf tool
build like below.
In file included from trace/beauty/ioctl.c:93:
tools/perf/trace/beauty/generated/ioctl/vhost_virtio_ioctl_array.c: In
function ‘ioctl
On Mon, Aug 18, 2025 at 3:59 PM Radim Krčmář wrote:
>
> 2025-08-14T21:25:42+05:30, Anup Patel :
> > This series adds ONE_REG interface for SBI FWFT extension implemented
> > by KVM RISC-V.
>
> I think it would be better to ONE_REG the CSRs (medeleg/menvcfg), or at
> least expose their CSR fields (
On Mon, Aug 18, 2025 at 10:53:43PM +0200, Bernd Edlinger wrote:
> This introduces signal->exec_bprm, which is used to
> fix the case when at least one of the sibling threads
> is traced, and therefore the trace process may dead-lock
> in ptrace_attach, but de_thread will need to wait for the
> trac
On Wed, Jul 23, 2025 at 6:35 AM Vlastimil Babka wrote:
>
> Specifying a non-zero value for a new struct kmem_cache_args field
> sheaf_capacity will setup a caching layer of percpu arrays called
> sheaves of given capacity for the created cache.
>
> Allocations from the cache will allocate via the
Removed an extra space in split_huge_page_test that was introduced
by commit 4b76e221794b ("mm/selftests: fix split_huge_page_test
failure on systems with 64KB page size").
Signed-off-by: Aboorva Devarajan
---
tools/testing/selftests/mm/split_huge_page_test.c | 2 +-
1 file changed, 1 insertion(
Some functions is recursive for the kprobe_multi and impact the benchmark
results. So just skip them.
Signed-off-by: Menglong Dong
---
tools/testing/selftests/bpf/trace_helpers.c | 16
1 file changed, 16 insertions(+)
diff --git a/tools/testing/selftests/bpf/trace_helpers.c
b/
We need to get all the kernel function that can be traced sometimes, so we
move the get_syms() and get_addrs() in kprobe_multi_test.c to
trace_helpers.c and rename it to bpf_get_ksyms() and bpf_get_addrs().
Signed-off-by: Menglong Dong
---
.../bpf/prog_tests/kprobe_multi_test.c| 220 +---
On Mon, Aug 18, 2025 at 04:07:21PM +0200, Thomas Weißschuh wrote:
> On 2025-08-17 11:39:05+0200, Willy Tarreau wrote:
> > On Sun, Aug 17, 2025 at 10:30:52AM +0200, Thomas Weißschuh wrote:
> > > On 2025-07-21 04:56:27+0200, Willy Tarreau wrote:
> > > > On Sat, Jul 19, 2025 at 05:38:28PM +0200, Thoma
For now, the benchmark for kprobe-multi is single, which means there is
only 1 function is hooked during testing. Add the testing
"kprobe-multi-all", which will hook all the kernel functions during
the benchmark. And the "kretprobe-multi-all" is added too.
Signed-off-by: Menglong Dong
---
tools/
Add the benchmark testcase "kprobe-multi-all", which will hook all the
kernel functions during the testing.
This series is separated out from [1].
Link:
https://lore.kernel.org/bpf/20250817024607.296117-1-dong...@chinatelecom.cn/ [1]
Menglong Dong (3):
selftests/bpf: move get_ksyms and get_add
On Tue, 19 Aug 2025 10:48:37 +0800 Jason Wang wrote:
> On Mon, Aug 18, 2025 at 11:39 PM Jakub Kicinski wrote:
> >
> > On Mon, 18 Aug 2025 09:15:22 +0800 Junnan Wu wrote:
> > > > > Yes, you are right. The commit of this fix tag is the first commit I
> > > > > found which add function `virtnet_poll_
socket.c: In function ‘run_tests’:
socket.c:59:25: warning: ignoring return value of ‘strerror_r’ \
declared with attribute ‘warn_unused_result’ [-Wunused-result]
59 | strerror_r(-s->expect, err_string1, ERR_STRING_SZ);
| ^~
socket.c:60:25: warning:
On Tue, Aug 19, 2025 at 4:23 AM Namhyung Kim wrote:
>
> Hello,
>
> I was sync'ing perf tools copy of kernel sources to apply recent
> changes. But there's a build error when it converts vhost ioctl
> commands due to a conflicting slot like below.
>
> In file included from trace/beauty/ioctl.c:9
On Mon, Aug 18, 2025 at 11:39 PM Jakub Kicinski wrote:
>
> On Mon, 18 Aug 2025 09:15:22 +0800 Junnan Wu wrote:
> > > > Yes, you are right. The commit of this fix tag is the first commit I
> > > > found which add function `virtnet_poll_cleantx`. Actually, we are not
> > > > sure whether this issue
From: Cryolitia PukNgae
To free memory and close fd after use
Suggested-by: Jun Zhan
Signed-off-by: Cryolitia PukNgae
---
tools/testing/selftests/net/tls.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/tools/testing/selftests/net/tls.c
b/tools/testing/selftests/net/tls.c
index
d8
Thanks for the review! I'll send the patch v2 with the adjustments shortly.
On Mon, Aug 18, 2025 at 5:35 PM Jakub Kicinski wrote:
>
> On Thu, 14 Aug 2025 23:06:31 -0700 Alex Tran wrote:
> > + char *err_message1;
> > + char *err_message2;
>
> nit, how about:
>
> const char *msg1, *
Alexey,
> The blogic_pci_tbl structure is used by the MODULE_DEVICE_TABLE macro.
> There is no longer a need to protect it with the MODULE condition,
> since this no longer causes the compiler to warn about an unused
> variable.
>
> To avoid warnings when -Wunused-const-variable option is used,
On Sat, 2025-08-16 at 14:43 +, Wei Yang wrote:
Hi Wei,
> On Sat, Aug 16, 2025 at 09:31:11AM +0530, Aboorva Devarajan wrote:
> > In ksm_functional_tests, test_child_ksm() returned negative values to
> > indicate errors. However, when passed to exit(), these were interpreted
> > as large unsig
On 2025/8/19 上午8:30, Andrew Jones wrote:
On Mon, Aug 11, 2025 at 06:49:07PM +0800, Bibo Mao wrote:
Hi Dong,
Thanks for you patch.
On 2025/8/11 下午4:24, Dong Yang wrote:
Remove the common KVM test cases already added to TEST_GEN_PROGS_COMMON
as following:
demand_paging_test
On Thu, 14 Aug 2025 23:06:31 -0700 Alex Tran wrote:
> + char *err_message1;
> + char *err_message2;
nit, how about:
const char *msg1, *msg2;
? And then please wrap the lines at 80 chars.
> int i, err;
>
> err = 0;
> @@ -56,13 +58,13 @@ static int run_tests(void)
>
On Mon, Aug 11, 2025 at 06:49:07PM +0800, Bibo Mao wrote:
> Hi Dong,
>
> Thanks for you patch.
>
> On 2025/8/11 下午4:24, Dong Yang wrote:
> > Remove the common KVM test cases already added to TEST_GEN_PROGS_COMMON
> > as following:
> >
> > demand_paging_test
> > dirty_log_test
> > g
On Thu, Aug 07, 2025 at 10:59:27PM +0800, dayss1...@gmail.com wrote:
> From: Dong Yang
>
> Add supported KVM test cases and fix the compilation dependencies.
> ---
> Changes in v2:
> - Delete some repeat KVM test cases on riscv
> - Add missing headers to fix the build for new RISC-V KVM selftests
On Thu, Aug 07, 2025 at 10:59:28PM +0800, dayss1...@gmail.com wrote:
> From: Quan Zhou
>
> Some common KVM test cases are supported on riscv now as following:
>
> access_tracking_perf_test
> dirty_log_perf_test
> memslot_modification_stress_test
> memslot_perf_test
> mmu_stre
On 7/30/25 5:11 AM, Neeraj Kumar wrote:
> LSA 2.1 format introduces region label, which can also reside
> into LSA along with only namespace label as per v1.1 and v1.2
>
> As both namespace and region labels are of same size of 256 bytes.
> Thus renamed "struct nd_namespace_label" to "struct nd
On Thu, Aug 07, 2025 at 10:59:30PM +0800, dayss1...@gmail.com wrote:
> From: Dong Yang
>
> Add missing headers to fix the build for new RISC-V KVM selftests.
>
> Signed-off-by: Quan Zhou
> Signed-off-by: Dong Yang
> ---
> tools/testing/selftests/kvm/include/riscv/processor.h | 2 ++
> 1 file
Remote processors may announce multiple devices (e.g., I2C, GPIO) over
an RPMSG channel. These devices may require corresponding device tree
nodes, especially when acting as providers, to supply phandles for their
consumers.
Define an RPMSG node to work as a container for a group of RPMSG channels
This introduces signal->exec_bprm, which is used to
fix the case when at least one of the sibling threads
is traced, and therefore the trace process may dead-lock
in ptrace_attach, but de_thread will need to wait for the
tracer to continue execution.
The problem happens when a tracer tries to ptra
On Thu, Aug 07, 2025 at 10:59:29PM +0800, dayss1...@gmail.com wrote:
> From: Quan Zhou
>
> To avoid redefinition issues with RISCV_FENCE,
> directly reference the existing macro in `rseq-riscv.h`.
>
> Signed-off-by: Quan Zhou
> Signed-off-by: Dong Yang
> ---
> tools/testing/selftests/rseq/rs
Register the RPMsg channel driver and populate remote devices defined
under the "rpmsg" subnode upon receiving their notification messages.
The following illustrates the expected DTS layout structure:
cm33: remoteproc-cm33 {
compatible = "fsl,imx8ulp-cm33";
Add the RPMSG bus node along with its GPIO subnodes to the device
tree.
Enable remote device communication and GPIO control via RPMSG on
the i.MX platform.
Signed-off-by: Shenwei Wang
---
arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 27 ++
1 file changed, 27 insertions(+)
d
On i.MX SoCs, the system may include two processors:
- An MCU running an RTOS
- An MPU running Linux
These processors communicate via the RPMSG protocol.
The driver implements the standard GPIO interface, allowing
the Linux side to control GPIO controllers which reside in
the remot
Support the remote devices on the remote processor via the RPMSG bus on
i.MX platform.
The expected DTS layout structure is following:
cm33: remoteproc-cm33 {
compatible = "fsl,imx8ulp-cm33";
rpmsg {
rpmsg-io-channel {
On Mon, Aug 18, 2025 at 01:23:10PM -0700, Namhyung Kim wrote:
> Hello,
>
> I was sync'ing perf tools copy of kernel sources to apply recent
> changes. But there's a build error when it converts vhost ioctl
> commands due to a conflicting slot like below.
I haven't looked at this specific case in
Hello,
I was sync'ing perf tools copy of kernel sources to apply recent
changes. But there's a build error when it converts vhost ioctl
commands due to a conflicting slot like below.
In file included from trace/beauty/ioctl.c:93:
tools/perf/trace/beauty/generated/ioctl/vhost_virtio_ioctl_arr
Tell git to ignore the generated binary for the test.
Signed-off-by: Mark Brown
---
tools/testing/selftests/filelock/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/filelock/.gitignore
b/tools/testing/selftests/filelock/.gitignore
new file mode 100644
inde
This series makes the output from the ofdlocks test a bit easier for
tooling to work with, and also ignores the generated file while we're
here.
Signed-off-by: Mark Brown
---
Mark Brown (3):
kselftest/filelock: Use ksft_perror()
kselftest/filelock: Report each test in oftlocks separat
The filelock test checks four different things but only reports an overall
status, convert to use ksft_test_result() for these individual tests. Each
test depends on the previous ones so we still bail out if any of them fail
but we get a bit more information from UIs parsing the results.
Signed-of
The ofdlocks test reports some errors via perror() which does not produce
KTAP output, convert to ksft_perror() which does.
Signed-off-by: Mark Brown
---
tools/testing/selftests/filelock/ofdlocks.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/fi
Instead of just checking the existence of PMD folios before and after folio
split tests, use check_folio_orders() to check after-split folio orders.
The split ranges in split_thp_in_pagecache_to_order_at() are changed to
[addr, addr + pagesize) for every pmd_pagesize. It prevents folios within
the
The helper gathers a folio order statistics of folios within a virtual
address range and checks it against a given order list. It aims to provide
a more precise folio order check instead of just checking the existence of
PMD folios.
The helper will be used the upcoming commit.
Signed-off-by: Zi Y
and rename it to is_backed_by_folio().
is_backed_by_folio() checks if the given vaddr is backed a folio with
a given order. It does so by:
1. getting the pfn of the vaddr;
2. checking kpageflags of the pfn;
if order is greater than 0:
3. checking kpageflags of the head pfn;
4. checking kpageflags
All functions are only used within the file.
Signed-off-by: Zi Yan
Reviewed-by: Wei Yang
Reviewed-by: wang lian
Acked-by: David Hildenbrand
---
.../selftests/mm/split_huge_page_test.c | 22 +--
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/tools/testing
They are useful information for debugging split huge page tests.
Signed-off-by: Zi Yan
Reviewed-by: Wei Yang
Reviewed-by: Donet Tom
Reviewed-by: wang lian
Reviewed-by: Baolin Wang
Reviewed-by: Barry Song
Acked-by: David Hildenbrand
---
mm/huge_memory.c | 8
1 file changed, 4 inser
This patchset uses kpageflags to get after-split folio orders for a better
split_huge_page_test result check[1]. The added
gather_after_split_folio_orders() scans through a VPN range and collects
the numbers of folios at different orders. check_after_split_folio_orders()
compares the result of gath
Commit 6693731487a8 ("vsock/virtio: Allocate nonlinear SKBs for handling
large transmit buffers") converted the virtio vsock transmit path to
utilise nonlinear SKBs when handling large buffers. As part of this
change, virtio_transport_fill_skb() was updated to call
skb_copy_datagram_from_iter() ins
In a similar manner to copy_from_iter()/copy_from_iter_full(), introduce
skb_copy_datagram_from_iter_full() which reverts the iterator to its
initial state when returning an error.
A subsequent fix for a vsock regression will make use of this new
function.
Cc: Paolo Abeni
Cc: Christian Brauner
Hi all,
Here are a couple of patches fixing the vsock error-handling regression
found by syzbot [1] that I introduced during the recent merge window.
Cheers,
Will
[1] https://lore.kernel.org/all/689a3d92.050a0220.7f033.00ff@google.com/
Cc: Alexander Viro
Cc: Christian Brauner
Cc: "David
On 18-08-2025 5:37 p.m., Rob Herring wrote:
On Sun, Aug 10, 2025 at 05:37:52PM +0200, Luca Weiss wrote:
Add the msm8953 CCI device string compatible.
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/D
Hi Rob,
On 18-08-2025 5:51 p.m., Rob Herring wrote:
On Sun, Aug 10, 2025 at 05:37:54PM +0200, Luca Weiss wrote:
Add the compatible for an 64Kb EEPROM from Belling.
It is generally not required to add a compatible here assuming
"atmel,24c64" is enough to identify the specific device (i.e. read
On 8/17/25 6:43 AM, 赵佳炜 wrote:
Hi, Yonghong. I've already filed an issue[1] in GCC community.
Accroding to the discussion, it's not a gcc bug but may be a systemtap bug.
I don't know how to report this bug to systemtap, but I found that the
libbpf/usdt have the same problem. I've filed
When we added coverage for ID_AA64MMFR3_EL1 we didn't add it to the list
of registers we read in the guest, do so.
Fixes: 0b593ef12afc ("KVM: arm64: selftests: Catch up set_id_regs with the
kernel")
Signed-off-by: Mark Brown
---
tools/testing/selftests/kvm/arm64/set_id_regs.c | 1 +
1 file chan
Since .vmlinux.export.c is used to add generated by modpost modaliases
for builtin modules the .vmlinux.export.o is no longer optional and
should always be created. The generation of this file is not dependent
on CONFIG_MODULES.
Signed-off-by: Alexey Gladkov
---
scripts/Makefile.vmlinux | 9 ++--
At this point, if a symbol is compiled as part of the kernel,
information about which module the symbol belongs to is lost.
To save this it is possible to add the module name to the alias name.
It's not very pretty, but it's possible for now.
Cc: Miguel Ojeda
Cc: Andreas Hindborg
Cc: Danilo Kru
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.
As a result kmod (which uses modules.builtin.modinfo in userspace)
The blogic_pci_tbl structure is used by the MODULE_DEVICE_TABLE macro.
There is no longer a need to protect it with the MODULE condition, since
this no longer causes the compiler to warn about an unused variable.
To avoid warnings when -Wunused-const-variable option is used, mark it
as __maybe_unu
From: Masahiro Yamada
Currently, we assume all the data for modules.builtin.modinfo are
available in vmlinux.o.
This makes it impossible for modpost, which is invoked after vmlinux.o,
to add additional module info.
This commit moves the modules.builtin.modinfo rule after modpost.
Signed-off-by
From: Masahiro Yamada
Keep the .modinfo section during linking, but strip it from the final
vmlinux.
Adjust scripts/mksysmap to exclude modinfo symbols from kallsyms.
This change will allow the next commit to extract the .modinfo section
from the vmlinux.unstripped intermediate.
Signed-off-by:
In the upcoming changes, the ELF_DETAILS macro will be extended with
the ".modinfo" section, which will cause an error:
>> s390x-linux-ld: .tmp_vmlinux1: warning: allocated section `.modinfo' not in
>> segment
>> s390x-linux-ld: .tmp_vmlinux2: warning: allocated section `.modinfo' not in
>> segm
From: Masahiro Yamada
Generate the intermediate vmlinux.unstripped regardless of
CONFIG_ARCH_VMLINUX_NEEDS_RELOCS.
If CONFIG_ARCH_VMLINUX_NEEDS_RELOCS is unset, vmlinux.unstripped and
vmlinux are identiacal.
This simplifies the build rule, and allows to strip more sections
by adding them to rem
The modules.builtin.modinfo file is used by userspace (kmod to be specific) to
get information about builtin modules. Among other information about the module,
information about module aliases is stored. This is very important to determine
that a particular modalias will be handled by a module that
On 8/10/25 6:27 PM, Waiman Long wrote:
The "Memory out of range" subtest of futex_numa_mpol assumes that memory
access outside of the mmap'ed area is invalid. That may not be the case
depending on the actual memory layout of the test application. When
that subtest was run on an x86-64 system with
On Sun, Aug 10, 2025 at 05:37:54PM +0200, Luca Weiss wrote:
> Add the compatible for an 64Kb EEPROM from Belling.
It is generally not required to add a compatible here assuming
"atmel,24c64" is enough to identify the specific device (i.e. read the
device's ID registers). If it is not sufficient,
On Mon, 18 Aug 2025 09:15:22 +0800 Junnan Wu wrote:
> > > Yes, you are right. The commit of this fix tag is the first commit I
> > > found which add function `virtnet_poll_cleantx`. Actually, we are not
> > > sure whether this issue appears after this commit.
> > >
> > > In our side, this issue is
On Sun, Aug 10, 2025 at 05:37:52PM +0200, Luca Weiss wrote:
> Add the msm8953 CCI device string compatible.
>
> Signed-off-by: Luca Weiss
> ---
> Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/
Hi Bibo,
Thanks for your review and for catching this mistake.
On Mon, Aug 11, 2025 at 06:49:07PM +0800, Bibo Mao wrote:
> Hi Dong,
>
> Thanks for you patch.
>
> On 2025/8/11 下午4:24, Dong Yang wrote:
> > Remove the common KVM test cases already added to TEST_GEN_PROGS_COMMON
> > as following:
On 18 Aug 2025, at 4:33, David Hildenbrand wrote:
> On 15.08.25 04:39, Zi Yan wrote:
>> and rename it to is_backed_by_folio().
>>
>> is_backed_by_folio() checks if the given vaddr is backed a folio with
>> a given order. It does so by:
>> 1. getting the pfn of the vaddr;
>> 2. checking kpageflags
On Sat, Aug 16, 2025 at 06:34:29AM -0400, Michael S. Tsirkin wrote:
> On Fri, Aug 15, 2025 at 04:48:00PM +0100, Will Deacon wrote:
> > On Fri, Aug 15, 2025 at 01:00:59PM +0100, Will Deacon wrote:
> > > On Fri, Aug 15, 2025 at 06:44:47AM -0400, Michael S. Tsirkin wrote:
> > > > On Fri, Aug 15, 2025
On 2025-08-17 11:39:05+0200, Willy Tarreau wrote:
> On Sun, Aug 17, 2025 at 10:30:52AM +0200, Thomas Weißschuh wrote:
> > On 2025-07-21 04:56:27+0200, Willy Tarreau wrote:
> > > On Sat, Jul 19, 2025 at 05:38:28PM +0200, Thomas Weißschuh wrote:
(...)
> > > I think I'd be fine with this, but then w
On Thu, 3 Jul 2025 at 08:48, lirongqing wrote:
>
> From: Li RongQing
>
> The original commit be2ff42c5d6e ("fuse: Use hash table to link
> processing request") converted fuse_pqueue->processing to a hash table,
> but virtio_fs_enqueue_req() was not updated to use it correctly.
> So use fuse_pqueu
On Mon, Aug 18, 2025 at 11:09:44AM +0200, Eugenio Perez Martin wrote:
> On Thu, Aug 14, 2025 at 12:42 PM Michael S. Tsirkin wrote:
> >
> > On Thu, Aug 14, 2025 at 11:36:22AM +0800, Jason Wang wrote:
> > > > > diff --git a/include/linux/virtio.h b/include/linux/virtio.h
> > > > > index addbc209275a
Signed-off-by: Sidharth Seela
diff --git a/tools/testing/selftests/syscall_user_dispatch/sud_test.c
b/tools/testing/selftests/syscall_user_dispatch/sud_test.c
index 2eb2c06303f2..6b846f5c1fa6 100644
--- a/tools/testing/selftests/syscall_user_dispatch/sud_test.c
+++ b/tools/testing/selftests/sysca
The result of integer comparison already evaluates to bool. No need for
explicit conversion.
Signed-off-by: Xichao Zhao
---
v2: Correct the errors in version v1 and modified the commit message
and subject.
v3: Change !(max_num == min_num) to (max_num != min_num).
---
drivers/virtio/virtio_v
2025-08-14T21:25:42+05:30, Anup Patel :
> This series adds ONE_REG interface for SBI FWFT extension implemented
> by KVM RISC-V.
I think it would be better to ONE_REG the CSRs (medeleg/menvcfg), or at
least expose their CSR fields (each sensible medeleg bit, PMM, ...)
through kvm_riscv_config, tha
> On Mon, Aug 18, 2025 at 12:01 PM Xichao Zhao wrote:
>> The result of integer comparison already evaluates to bool. No need for
>> explicit conversion.
>>
>> Signed-off-by: Xichao Zhao
>> ---
>> drivers/virtio/virtio_vdpa.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff
On Mon, Aug 18, 2025 at 12:01 PM Xichao Zhao wrote:
>
> The result of integer comparison already evaluates to bool. No need for
> explicit conversion.
>
> Signed-off-by: Xichao Zhao
> ---
> drivers/virtio/virtio_vdpa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/driv
On Wed, Jul 23, 2025 at 03:34:34PM +0200, Vlastimil Babka wrote:
> Specifying a non-zero value for a new struct kmem_cache_args field
> sheaf_capacity will setup a caching layer of percpu arrays called
> sheaves of given capacity for the created cache.
>
> Allocations from the cache will allocate
The result of integer comparison already evaluates to bool. No need for
explicit conversion.
Signed-off-by: Xichao Zhao
---
drivers/virtio/virtio_vdpa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/virtio/virtio_vdpa.c b/drivers/virtio/virtio_vdpa.c
index 657b07a60
On 15.08.25 02:18, Soham Metha wrote:
found/fixed the following typo
- avaialable -> available
in `tools/testing/selftests/kvm/s390/cpumodel_subfuncs_test.c`
Signed-off-by: Soham Metha
---
Reviewed-by: David Hildenbrand
--
Cheers
David / dhildenb
> Hi all,
>
> Apologies for the oversight; this patch contains issues. I will send a
> v2 version of the patch to correct them.
>
> Best regards,
>
> Xichao Zhao
>
>> The may_reduce_num is used only once and has a redundant conversion to bool.
>> Therefore, remove it.
>>
>> Signed-off-by: Xichao Z
Thank you! Anthony.
Yep, I checked the comments in arch/mm/x86/fault.c file which says as your
advices in previous email.
I changed my code in kernel 5.5 as below:
if (unlikely(is_shared_vma) && ((fault & VM_FAULT_RETRY) &&
(flags & FAULT_FLAG_ALLOW_RETRY) || fault_signal_pend
The may_reduce_num is used only once and has a redundant conversion to bool.
Therefore, remove it.
Signed-off-by: Xichao Zhao
---
drivers/virtio/virtio_vdpa.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/virtio/virtio_vdpa.c b/drivers/virtio/virtio_vdpa.c
index
On Thu, Aug 14, 2025 at 12:42 PM Michael S. Tsirkin wrote:
>
> On Thu, Aug 14, 2025 at 11:36:22AM +0800, Jason Wang wrote:
> > > > diff --git a/include/linux/virtio.h b/include/linux/virtio.h
> > > > index addbc209275a..37029df94aaf 100644
> > > > --- a/include/linux/virtio.h
> > > > +++ b/include
On Thu, Aug 14, 2025 at 3:08 PM Alexey Gladkov wrote:
> The typo when using the MODULE_DEVICE_TABLE macro was not noticeable
> because the macro was defined only if the module was built as a separate
> module.
>
> Cc: Xianwei Zhao
> Cc: Linus Walleij
> Cc: Neil Armstrong
> Cc: Kevin Hilman
>
Finalize the series by advertising VDUSE API v1 support to userspace.
Now that all required infrastructure for v1 (ASIDs, VQ groups,
update_iotlb_v2) is in place, VDUSE devices can opt in to the new
features.
Signed-off-by: Eugenio Pérez
---
drivers/vdpa/vdpa_user/vduse_dev.c | 4 ++--
1 file c
Add support for assigning Address Space Identifiers (ASIDs) to each VQ
group. This enables mapping each group into a distinct memory space.
Now that the driver can change ASID in the middle of operation, the
domain that each vq address point is also protected by domain_lock.
Signed-off-by: Eugen
This is a first step so we can make more than one different address
spaces. No change on the colde flow intended.
Signed-off-by: Eugenio Pérez
---
drivers/vdpa/vdpa_user/vduse_dev.c | 115 +++--
1 file changed, 59 insertions(+), 56 deletions(-)
diff --git a/drivers/vdpa
This allows the kernel to detect whether the userspace VDUSE device
supports the VQ group and ASID features. VDUSE devices that don't set
the V1 API will not receive the new messages, and vdpa device will be
created with only one vq group and asid.
The next patches implement the new feature incre
Return the internal struct that represents the vq group as virtqueue map
token, instead of the device. This allows the map functions to access
the information per group.
At this moment all the virtqueues share the same vq group, that only
can point to ASID 0. This change prepares the infrastruct
Proposal to make it type safe, never casting to void, but allow the
backend to use whatever struct it needs.
Next patches will move the token from a domain to a custom struct.
Signed-off-by: Eugenio Pérez
---
drivers/vdpa/vdpa_user/iova_domain.h | 1 +
drivers/vdpa/vdpa_user/vduse_dev.c | 60
When used by vhost-vDPA bus driver for VM, the control virtqueue
should be shadowed via userspace VMM (QEMU) instead of being assigned
directly to Guest. This is because QEMU needs to know the device state
in order to start and stop device correctly (e.g for Live Migration).
This requies to isolat
This allows sepparate the different virtqueues in groups that shares the
same address space. Asking the VDUSE device for the groups of the vq at
the beginning as they're needed for the DMA API.
Allocating 3 vq groups as net is the device that need the most groups:
* Dataplane (guest passthrough)
On 15.08.25 04:39, Zi Yan wrote:
and rename it to is_backed_by_folio().
is_backed_by_folio() checks if the given vaddr is backed a folio with
a given order. It does so by:
1. getting the pfn of the vaddr;
2. checking kpageflags of the pfn;
if order is greater than 0:
3. checking kpageflags of t
On 31/07/2025 18:01, Muhammad Usama Anjum wrote:
> [...]
>
> diff --git a/tools/testing/selftests/mm/Makefile
> b/tools/testing/selftests/mm/Makefile
> index 23d4bf6215465..d75f1effcb791 100644
> --- a/tools/testing/selftests/mm/Makefile
> +++ b/tools/testing/selftests/mm/Makefile
> @@ -20,7 +20,6
+Dave Hansen
On 31/07/2025 18:01, Muhammad Usama Anjum wrote:
> The while loop doesn't execute and following warning gets generated:
>
> protection_keys.c:561:15: warning: code will never be executed
> [-Wunreachable-code]
> int rpkey = alloc_random_pkey();
>
> Let's enable the whi
On 31/07/2025 18:01, Muhammad Usama Anjum wrote:
> [...]
>
> diff --git a/tools/testing/selftests/mm/pkey_sighandler_tests.c
> b/tools/testing/selftests/mm/pkey_sighandler_tests.c
> index b5e076a564c95..302fef54049c8 100644
> --- a/tools/testing/selftests/mm/pkey_sighandler_tests.c
> +++ b/tools/t
Hello,
syzbot found the following issue on:
HEAD commit:8742b2d8935f Merge tag 'pull-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=109d2af058
kernel config: https://syzkaller.appspot.com/x/.config?x=412ee2f8b704a5e6
das
On 17.08.25 08:52, Ujwal Kundur wrote:
Refactor macros and non-composite global variable definitions into a
struct that is defined at the start of a test and is passed around
instead of relying on global vars.
Signed-off-by: Ujwal Kundur
Acked-by: Peter Xu
---
Previous versions and discussion
On 15.08.25 04:39, Zi Yan wrote:
All functions are only used within the file.
Signed-off-by: Zi Yan
---
Acked-by: David Hildenbrand
--
Cheers
David / dhildenb
When using GCC on x86-64 to compile an usdt prog with -O1 or higher
optimization, the compiler will generate SIB addressing mode for global
array and PC-relative addressing mode for global variable,
e.g. "1@-96(%rbp,%rax,8)" and "-1@4+t1(%rip)".
The current USDT implementation in libbpf cannot par
usdt_o1 is intended to exercise the SIB (Scale-Index-Base) argument
handling in libbpf's USDT path. With GCC 13 this reliably produced a
SIB-form argument (e.g. 8@(%rdx,%rax,8)), but with newer GCC (e.g. 15)
the compiler frequently optimizes the probe argument into a plain
register (e.g. 8@%rax) or
1 - 100 of 113 matches
Mail list logo
