Add ucall test support for LoongArch, ucall method on LoongArch uses
undefined mmio area. It will cause causes vcpu exits to hypervisor so
that hypervisor can communicate with vcpu.
Signed-off-by: Bibo Mao
---
.../selftests/kvm/include/loongarch/ucall.h | 20 ++
.../selftests/kvm/lib/l
This patchset adds KVM selftests for LoongArch system, currently only
some common test cases are supported and pass to run. These testcase
are listed as following:
coalesced_io_test
demand_paging_test
dirty_log_perf_test
dirty_log_test
guest_print_test
hardware_disable_test
Some common KVM testcases are supported on LoongArch now as following:
coalesced_io_test
demand_paging_test
dirty_log_perf_test
dirty_log_test
guest_print_test
hardware_disable_test
kvm_binary_stats_test
kvm_create_max_vcpus
kvm_page_table_test
memslot_modification_stress_test
On Wed, 9 Apr 2025 at 22:40, Gon Solo wrote:
>
> Am Wed, Apr 09, 2025 at 08:04:19PM + schrieb Ricardo Ribalda:
> > Changes in v2:
> > - Make repo a local variable
> > - Link to v1:
> > https://lore.kernel.org/r/20250225-spx-v1-1-e935b27eb...@chromium.org
>
> This is not necessary as it was Py
On 2025-04-10 03:10:37, patchwork-bot+netdev...@kernel.org wrote:
> Hello:
>
> This series was applied to bpf/bpf-next.git (master)
> by Alexei Starovoitov :
>
> On Mon, 7 Apr 2025 22:21:19 +0800 you wrote:
> > I was writing a benchmark based on sockmap + TCP and discovered several
> > issues:
>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov :
On Mon, 7 Apr 2025 22:21:19 +0800 you wrote:
> I was writing a benchmark based on sockmap + TCP and discovered several
> issues:
>
> 1. When EAGAIN occurs, the direction of skb is incorrect, causing data
>lo
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko :
On Wed, 9 Apr 2025 15:26:33 +0530 you wrote:
> For systems with missing iptables-legacy tool, this selftest fails.
>
> Add check to find if iptables-legacy tool is available and skip the
> test if the tool is missin
Hi,
AFAIK, the commit c9c1e20b4c7d ("KVM: x86: Introduce Intel specific quirk
KVM_X86_QUIRK_IGNORE_GUEST_PAT") which re-allows honoring guest PAT on Intel's
platforms has been in kvm/queue now.
However, as the quirk is enabled by default, userspace(like QEMU) needs to turn
it off by code like "kv
Hello,
kernel test robot noticed
"WARNING:at_mm/truncate.c:#truncate_folio_batch_exceptionals" on:
commit: bde708f1a65d025c45575bfe1e7bf7bdf7e71e87 ("fs/dax: always remove DAX
page-cache entries when breaking layouts")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
i
If the git.Repo object's scope extends to the Python interpreter's
shutdown phase, its destructor may fail due to the interpreter's state.
Exception ignored in:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/git/cmd.py", line 565, in __del__
File "/usr/lib/python3/dis
On Fri, Mar 21, 2025 at 01:47:26PM +0100, Joel Granados wrote:
> As we add more test functions in lib/tests_sysctl the main test function
> (test_sysctl_init) grows. Condense the logic to make it easier to
> add/remove tests.
>
> Signed-off-by: Joel Granados
Nice cleanup!
Reviewed-by: Kees Cook
On Tue, Apr 8, 2025 at 7:25 AM Shivank Garg wrote:
>
> KVM guest_memfd is implementing its own inodes to store metadata for
> backing memory using a custom filesystem. This requires the ability to
> initialize anonymous inode using security_inode_init_security_anon().
>
> As guest_memfd currently
Tim!
On Wed, Apr 09 2025 at 17:44, Tim Bird wrote:
>> From: Thomas Gleixner
>> On Tue, Apr 08 2025 at 17:34, Tim Bird wrote:
>> And yes, it ignores not yet tracked files, but if you want to check
>> them, then it's easy enough to commit them temporarily or provide a
>> dedicated file target to th
From: Iuliana Prodan
Some DSP firmware requires a FW_READY signal before proceeding, while
others do not.
Therefore, add support to handle i.MX DSP-specific features.
Implement handle_rsc callback to handle resource table parsing and to
process DSP-specific resource, to determine if waiting is n
On Tue, Apr 01, 2025 at 09:59:20PM -0400, Gregory Price wrote:
> Device capacity intended for use as system ram should be aligned to the
> archite-defined memory block size or that capacity will be silently
> truncated and capacity stranded.
>
> As hotplug dax memory becomes more prevelant, the me
Creating an enclave with xfrm == 3 disables extended CPU states and instruction
sets, like AVX2 and AVX512 inside the enclave. Thus the enclave code has to be
built with a compiler which does not produce instructions from the extended
instruction sets. Nevertheless certain Linux distributions confg
Am Wed, Apr 09, 2025 at 08:04:19PM + schrieb Ricardo Ribalda:
> Changes in v2:
> - Make repo a local variable
> - Link to v1:
> https://lore.kernel.org/r/20250225-spx-v1-1-e935b27eb...@chromium.org
This is not necessary as it was Python's fault and is fixed by 3.13.3
which came out yesterday.
On Fri, Mar 21, 2025 at 01:47:24PM +0100, Joel Granados wrote:
> If the test added in commit b5ffbd139688 ("sysctl: move the extra1/2
> boundary check of u8 to sysctl_check_table_array") is run as a module, a
> lingering reference to the module is left behind, and a 'sysctl -a'
> leads to a panic.
On Wed, Apr 9, 2025 at 5:38 PM Borislav Petkov wrote:
>
> On Wed, Apr 09, 2025 at 05:32:39PM +0200, Uros Bizjak wrote:
> > The workaround is posted to the list. It should be committed to the
> > mainline until genksyms is fixed.
>
> I'll take it through tip.
Thanks!
Best regards,
Uros.
On Wed, Apr 09, 2025 at 03:21:53PM -0700, Alison Schofield wrote:
> Existing unit test 'daxctl-devices.sh' hits this case:
> [ 52.547521] kmem dax3.0: DAX region truncated by 62.0 MiB due to alignment
>
> Tested-by: Alison Schofield
>
Thanks for testing, good to know there's an existing test f
Hi Linus,
Please pull the following kselftest fixes update for Linux 6.15-rc2
Fixes tpm2, futex, and mincore tests. Creates a dedicated .gitignore
for tpm2
Details:
selftests: tpm2: test_smoke: use POSIX-conformant expression operator
selftests/futex: futex_waitv wouldblock test should fail
se
On Wed, Apr 9, 2025 at 4:28 PM Andrii Nakryiko
wrote:
>
> On Tue, Apr 8, 2025 at 11:33 AM Malaya Kumar Rout
> wrote:
> >
> > Static Analyis for bench_htab_mem.c with cppcheck:error
>
> typo: analysis (lower case and typo)
>
> you can also make into a bit more human-readable sentence:
>
> "Static
On Tue, Apr 8, 2025 at 11:33 AM Malaya Kumar Rout
wrote:
>
> Static Analyis for bench_htab_mem.c with cppcheck:error
typo: analysis (lower case and typo)
you can also make into a bit more human-readable sentence:
"Static analysis found an issue in bench_htab_mem.c:
> tools/testing/selftests/b
The pull request you sent on Wed, 9 Apr 2025 16:13:39 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux_kselftest-fixes-6.15-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3b07108ada81a8ebcebf1fe61367b4e436c895bd
Thank you!
Gregory Price wrote:
> Device capacity intended for use as system ram should be aligned to the
> archite-defined memory block size or that capacity will be silently
> truncated and capacity stranded.
>
> As hotplug dax memory becomes more prevelant, the memory block size
> alignment becomes more i
Hello,
I am completely new to and uninformed about kernel development. I was
pointed here from Mesa documentation for Venus (Vulkan encapsulation for
KVM/QEMU): https://docs.mesa3d.org/drivers/venus.html
Based on my limited understanding of what has happened here, this patch
series was partial
On Wed, Apr 9, 2025 at 5:28 PM Borislav Petkov wrote:
>
> On Sun, Apr 06, 2025 at 05:36:13PM +0200, Uros Bizjak wrote:
> > On Fri, Apr 4, 2025 at 9:14 PM Masahiro Yamada wrote:
> > >
> > > On Fri, Apr 4, 2025 at 11:37 PM Uros Bizjak wrote:
> > > >
> > > > On Fri, Apr 4, 2025 at 4:06 PM Masahiro
On Wed, Apr 09, 2025 at 05:32:39PM +0200, Uros Bizjak wrote:
> The workaround is posted to the list. It should be committed to the
> mainline until genksyms is fixed.
I'll take it through tip.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
On Wed, 9 Apr 2025 13:58:13 +0200 Matthieu Baerts wrote:
> On 08/04/2025 21:03, Jakub Kicinski wrote:
> > On Tue, 8 Apr 2025 20:18:26 +0200 Matthieu Baerts wrote:
> >> On 02/04/2025 19:23, Stanislav Fomichev wrote:
> >>> Recent change [0] resulted in a "BUG: using __this_cpu_read() in
> >>> pre
On Wed, Apr 09, 2025 at 02:24:32PM +0200, David Hildenbrand wrote:
> On 09.04.25 14:07, Michael S. Tsirkin wrote:
> > On Wed, Apr 09, 2025 at 01:12:19PM +0200, David Hildenbrand wrote:
> > > On 09.04.25 12:56, Michael S. Tsirkin wrote:
> > > > On Wed, Apr 09, 2025 at 12:46:41PM +0200, David Hildenb
On Wed, Jan 15, 2025 at 2:53 AM Peter Seiderer wrote:
>
> Fix compile on openSUSE Tumbleweed (gcc-14.2.1, glibc-2.40):
> - add missing sys/mount.h include
>
> Fixes:
>
> pid_max.c: In function ‘pid_max_cb’:
> pid_max.c:42:15: error: implicit declaration of function ‘mount’
> [-Wimplicit-fun
Hi Jakub,
On 08/04/2025 21:03, Jakub Kicinski wrote:
> On Tue, 8 Apr 2025 20:18:26 +0200 Matthieu Baerts wrote:
>> On 02/04/2025 19:23, Stanislav Fomichev wrote:
>>> Recent change [0] resulted in a "BUG: using __this_cpu_read() in
>>> preemptible" splat [1]. PREEMPT kernels have additional require
On 4/9/25 3:50 AM, Harry Yoo wrote:
> On Mon, Mar 17, 2025 at 03:33:04PM +0100, Vlastimil Babka wrote:
>
> Hmm this hunk in v3 is fine, but on your slub-percpu-shaves-v4r0 branch
> it's calling local_unlock() twice. Probably a rebase error?
Yeah, thanks a lot for catching that! I've just pushed
h
Recently, during a debugging session using local MPTCP connections, I
noticed MPJoinAckHMacFailure was strangely not zero on the server side.
The first patch fixes this issue -- present since v5.9 -- and the second
one validates it in the selftests.
Signed-off-by: Matthieu Baerts (NGI0)
---
Matt
On Tue, Apr 8, 2025 at 12:31 AM Jiayuan Chen wrote:
>
> There are potential concurrency issues, as shown below.
> '''
> CPU0 CPU1
> sk_psock_verdict_data_ready:
> socket *sock = sk->sk_socket
> if (!sock) return
>close(fd):
>
Add core KVM selftests support for LoongArch, it includes exception
handler, mmu page table setup and vcpu startup entry supporting etc.
Signed-off-by: Bibo Mao
---
.../selftests/kvm/lib/loongarch/exception.S | 59 +++
.../selftests/kvm/lib/loongarch/processor.c | 349 ++
2
Add KVM selftests header files for LoongArch, including processor.h
and kvm_util_base.h. It mainly contains LoongArch CSR register
definition and page table entry definition.
Signed-off-by: Bibo Mao
---
.../testing/selftests/kvm/include/kvm_util.h | 5 +
.../kvm/include/loongarch/kvm_util_arc
On 09.04.25 14:07, Michael S. Tsirkin wrote:
On Wed, Apr 09, 2025 at 01:12:19PM +0200, David Hildenbrand wrote:
On 09.04.25 12:56, Michael S. Tsirkin wrote:
On Wed, Apr 09, 2025 at 12:46:41PM +0200, David Hildenbrand wrote:
On 07.04.25 23:20, Michael S. Tsirkin wrote:
On Mon, Apr 07, 2025 at
On Sun, Apr 06, 2025 at 05:36:13PM +0200, Uros Bizjak wrote:
> On Fri, Apr 4, 2025 at 9:14 PM Masahiro Yamada wrote:
> >
> > On Fri, Apr 4, 2025 at 11:37 PM Uros Bizjak wrote:
> > >
> > > On Fri, Apr 4, 2025 at 4:06 PM Masahiro Yamada
> > > wrote:
> > >
> > > > > > > Current version of genksyms
The test_memcontrol selftest consistently fails its test_memcg_low
sub-test due to the fact that two of its test child cgroups which
have a memmory.low of 0 or an effective memory.low of 0 still have low
events generated for them since mem_cgroup_below_low() use the ">="
operator when comparing to
On 09/04/2025 3:24 pm, Mark Brown wrote:
On Wed, Apr 09, 2025 at 11:45:44AM +0100, Richard Fitzgerald wrote:
Depend on SND_SOC_CS_AMP_LIB instead of selecting it.
KUNIT_ALL_TESTS should only build tests for components that are
already being built, it should not cause other stuff to be added
to
On 4/9/25 09:55, Vladis Dronov wrote:
...
> Fix this by adding "-mno-avx" to ENCL_CFLAGS in Makefile. Add some comments
> about this to code locations where enclave's xfrm field is set.
>
> Suggested-by: Dave Hansen
> Signed-off-by: Vladis Dronov
First of all, this looks fine to me:
Acked-by: D
On Wed, Apr 9, 2025 at 7:07 PM Dave Hansen wrote:
>
> On 4/9/25 09:55, Vladis Dronov wrote:
> ...
> > Fix this by adding "-mno-avx" to ENCL_CFLAGS in Makefile. Add some comments
> > about this to code locations where enclave's xfrm field is set.
> >
> > Suggested-by: Dave Hansen
> > Signed-off-by
On 4/9/25 15:51, David Hildenbrand wrote:
> On 09.04.25 12:09, Anshuman Khandual wrote:
>>
>>
>> On 4/9/25 15:27, David Hildenbrand wrote:
>>> On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. F
This patch resolves resource leaks reported by cppcheck in lam.c.
Specifically, the 'file_fd' and 'fd' were not closed in do_uring()
and allocate_dsa_pasid() functions, respectively.
cppcheck output before this patch:
tools/testing/selftests/x86/lam.c:685:3: error: Resource leak: file_fd
[resourc
On Wed, Apr 9, 2025 at 1:53 AM Peter Seiderer wrote:
>
> Hello T.J.,
>
> On Tue, 8 Apr 2025 23:02:02 +, "T.J. Mercier"
> wrote:
>
> > pid_max.c: In function ‘pid_max_cb’:
> > pid_max.c:42:15: error: implicit declaration of function ‘mount’
> >[-Wimpli
On Fri, Mar 21, 2025 at 01:47:25PM +0100, Joel Granados wrote:
> Add a sysctl test that uses the new u8 test ctl files in a created by
> the sysctl test module. Check that the u8 proc file that is valid is
> created and that there are two messages in dmesg for the files that were
> out of range.
>
Hello T.J.,
On Tue, 8 Apr 2025 23:02:02 +, "T.J. Mercier" wrote:
> pid_max.c: In function ‘pid_max_cb’:
> pid_max.c:42:15: error: implicit declaration of function ‘mount’
>[-Wimplicit-function-declaration]
>42 | ret = mount("", "/", NULL,
> -Original Message-
> From: Thomas Gleixner
> On Tue, Apr 08 2025 at 17:34, Tim Bird wrote:
> >> -Original Message-
> > For what it's worth, I've always been a bit skeptical of the use of the
> > python git module
> > in spdxcheck.py. Its use makes it impossible to use spdxcheck
For systems with missing iptables-legacy tool, this selftest fails.
Add check to find if iptables-legacy tool is available and skip the
test if the tool is missing.
Fixes: de9c8d848d90 ("selftests/bpf: S/iptables/iptables-legacy/ in the bpf_nf
and xdp_synproxy test")
Signed-off-by: Saket Kumar B
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. Fix the warning via zero init for the variable.
CC cow
cow.c: In function ‘do_test_vmsplice_in_parent’:
cow.c:365:61: warning: ‘transferred’ may
On Tue, Apr 8, 2025 at 7:56 PM Michael S. Tsirkin wrote:
>
> On Fri, Mar 28, 2025 at 06:02:52PM +0800, Cindy Lu wrote:
> > Introduce a new config knob `CONFIG_VHOST_ENABLE_FORK_OWNER_IOCTL`,
> > to control the availability of the `VHOST_FORK_FROM_OWNER` ioctl.
> > When CONFIG_VHOST_ENABLE_FORK_OWN
On 4/9/25 15:27, David Hildenbrand wrote:
> On 09.04.25 11:50, Anshuman Khandual wrote:
>> Following build warning comes up for cow test as 'transferred' variable has
>> not been initialized. Fix the warning via zero init for the variable.
>>
>> CC cow
>> cow.c: In function ‘do_test_vms
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. Fix the warning via zero init for the variable.
CC cow
cow.c: In function ‘do_test_vmsplice_in_parent’:
cow.c:365:61: warning: ‘transferred’ may be used uninitialized
[-Wmaybe-uninitialized]
On 09.04.25 12:09, Anshuman Khandual wrote:
On 4/9/25 15:27, David Hildenbrand wrote:
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred' variable has
not been initialized. Fix the warning via zero init for the variable.
CC cow
On 07.04.25 23:20, Michael S. Tsirkin wrote:
On Mon, Apr 07, 2025 at 08:47:05PM +0200, David Hildenbrand wrote:
In my opinion, it makes the most sense to keep the spec as it is and
change QEMU and the kernel to match, but obviously that's not trivial
to do in a way that doesn't break existing de
On 09.04.25 12:25, Anshuman Khandual wrote:
On 4/9/25 15:51, David Hildenbrand wrote:
On 09.04.25 12:09, Anshuman Khandual wrote:
On 4/9/25 15:27, David Hildenbrand wrote:
On 09.04.25 11:50, Anshuman Khandual wrote:
Following build warning comes up for cow test as 'transferred' variable h
On Wed, Apr 09, 2025 at 12:46:41PM +0200, David Hildenbrand wrote:
> On 07.04.25 23:20, Michael S. Tsirkin wrote:
> > On Mon, Apr 07, 2025 at 08:47:05PM +0200, David Hildenbrand wrote:
> > > > In my opinion, it makes the most sense to keep the spec as it is and
> > > > change QEMU and the kernel to
On 07.04.25 23:09, Daniel Verkamp wrote:
On Mon, Apr 7, 2025 at 11:47 AM David Hildenbrand wrote:
Heh, but that one said:
+\item[ VIRTIO_BALLOON_F_WS_REPORTING(6) ] The device has support for
Working Set
Which does not seem to reflect reality ...
Please feel free to disregard these featur
On 09.04.25 12:56, Michael S. Tsirkin wrote:
On Wed, Apr 09, 2025 at 12:46:41PM +0200, David Hildenbrand wrote:
On 07.04.25 23:20, Michael S. Tsirkin wrote:
On Mon, Apr 07, 2025 at 08:47:05PM +0200, David Hildenbrand wrote:
In my opinion, it makes the most sense to keep the spec as it is and
c
bpf_check(), as it currently exists, will soon be going away to make way
for loadable BPF verifier support. Fixup selftests so they fentry attach
to a more reliable location.
Signed-off-by: Daniel Xu
---
tools/testing/selftests/bpf/progs/exceptions_assert.c | 2 +-
tools/testing/selftests/bpf/pr
On Wed, Apr 09, 2025 at 01:12:19PM +0200, David Hildenbrand wrote:
> On 09.04.25 12:56, Michael S. Tsirkin wrote:
> > On Wed, Apr 09, 2025 at 12:46:41PM +0200, David Hildenbrand wrote:
> > > On 07.04.25 23:20, Michael S. Tsirkin wrote:
> > > > On Mon, Apr 07, 2025 at 08:47:05PM +0200, David Hildenb
62 matches
Mail list logo
