On 4/12/2025 12:56 AM, Konrad Dybcio wrote:
> On 4/11/25 1:37 PM, Jagadeesh Kona wrote:
>>
>>
>> On 4/11/2025 2:42 PM, Konrad Dybcio wrote:
>>> On 4/11/25 9:15 AM, Jagadeesh Kona wrote:
On 4/1/2025 10:03 PM, Konrad Dybcio wrote:
> On 3/24/25 9:41 AM, Luca Weiss wrote:
>> A
Jonathan Cameron wrote:
[..]
> To me we don't need to answer the question of whether we fully understand
> requirements, or whether this support covers them, but rather to ask
> if anyone has requirements that are not sensible to satisfy with additional
> work building on this?
Wearing only my ups
On Mon, Apr 14, 2025 at 09:37:02PM -0500, Ira Weiny wrote:
> Fan Ni wrote:
> > On Sun, Apr 13, 2025 at 05:52:08PM -0500, Ira Weiny wrote:
> > > A git tree of this series can be found here:
> > >
> > > https://github.com/weiny2/linux-kernel/tree/dcd-v6-2025-04-13
> > >
> > > This is now based on
Fan Ni wrote:
> On Sun, Apr 13, 2025 at 05:52:08PM -0500, Ira Weiny wrote:
> > A git tree of this series can be found here:
> >
> > https://github.com/weiny2/linux-kernel/tree/dcd-v6-2025-04-13
> >
> > This is now based on 6.15-rc2.
> >
> > Due to the stagnation of solid requirements for use
From: Ackerley Tng
TDX guests' registers cannot be initialized directly using
vcpu_regs_set(), hence the stack pointer needs to be initialized by
the guest itself, running boot code beginning at the reset vector.
Store the stack address as part of struct kvm_vcpu so that it can
be accessible lat
From: Ackerley Tng
Turn vCPU descriptor table initialization into a utility for use by tests
needing finer control, for example for TDX TD creation.
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/include/x86/processor.h | 1 +
tools/testing/selftests/kv
On Sun, Apr 13, 2025 at 05:52:20PM -0500, Ira Weiny wrote:
snip
> +
> +void memdev_release_extent(struct cxl_memdev_state *mds, struct range *range)
> +{
> + struct device *dev = mds->cxlds.dev;
> + struct xarray extent_list;
> +
> + struct cxl_extent extent = {
> + .start
The test checks report_fatal_error functionality.
TD guest can use TDG.VP.VMCALL to report the fatal error
it has experienced. TD guest is requesting a termination with the error
information that include 16 general-purpose registers.
Co-developed-by: Binbin Wu
Signed-off-by: Binbin Wu
Signed-of
The test verifies IO reads of various sizes from the host to the guest.
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/x86/tdx_vm_test.c | 76 ++-
1 file changed, 75 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kvm/x86/tdx_vm_test.c
b/tools/test
On 2025/4/14 下午9:59, Huacai Chen wrote:
Hi, Bibo,
On Thu, Apr 10, 2025 at 11:57 AM Bibo Mao wrote:
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:
From: Ryan Afranji
Test that host and guest can exchange data via shared memory.
Set up shared memory by first allocating as private and then mapping
the same GPA as shared. The guest starts with a request to map a
page of memory to shared. This request is done via a hypercall
(TDG.VP.VMCALL) fr
From: Ackerley Tng
This also exercises the KVM_TDX_CAPABILITIES ioctl.
Suggested-by: Isaku Yamahata
Co-developed-by: Isaku Yamahata
Signed-off-by: Isaku Yamahata
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/lib/x86/tdx/tdx_util.c| 17
The test reads CPUID values from inside a TD VM and compare them
to expected values.
The test targets CPUID values which are virtualized as "As Configured",
"As Configured (if Native)", "Calculated", "Fixed" and "Native"
according to the TDX spec.
Co-developed-by: Isaku Yamahata
Signed-off-by: I
From: Erdem Aktas
Adding a test to verify TDX lifecycle by creating a TD and running a
dummy TDG.VP.VMCALL inside it.
Co-developed-by: Sagi Shahar
Signed-off-by: Sagi Shahar
Co-developed-by: Ackerley Tng
Signed-off-by: Ackerley Tng
Co-developed-by: Reinette Chatre
Signed-off-by: Reinette C
┌┐ ┌───┐ ┌┐
││ │ │ ││
││ │ PCI Endpoint │ │ PCI Host │
││ │ │ │
From: Ryan Afranji
The test checks that host can only read fixed values when trying to
access the guest's private memory.
Signed-off-by: Ryan Afranji
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/x86/tdx_vm_test.c | 83 ++-
1 file changed, 82 insertions(+), 1 dele
The test calls TDG.VP.VMCALL hypercall from the guest
and verifies the expected returned values.
TDG.VP.VMCALL hypercall is a subleaf of TDG.VP.VMCALL to
enumerate which TDG.VP.VMCALL sub leaves are supported. This hypercall is
for future enhancement of the Guest-Host-Communication Interface (GHC
From: Yan Zhao
Add a selftest to verify that adding flag KVM_MEM_LOG_DIRTY_PAGES to a
!KVM_MEM_GUEST_MEMFD memslot does not produce host errors in TDX.
Signed-off-by: Yan Zhao
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/x86/tdx_vm_test.c | 45 ++-
1 file changed
From: Ackerley Tng
This tests the use of guest memory without explicit TDG.VP.VMCALL
calls.
Provide a 2MB memory region to the TDX guest with a 40KB focus area at
offset 1MB intended to be shared between host and guest. The guest does
not request memory to be shared or private using TDG.VP.VMCAL
From: Ackerley Tng
This tests the use of guest memory with explicit TDG.VP.VMCALL
calls.
Provide a 2MB memory region to the TDX guest with a 40KB focus area at
offset 1MB intended to be shared between host and guest. The entire 2MB
region starts out as private with the guest filling it with a pa
From: Ackerley Tng
Add support for TDG.MEM.PAGE.ACCEPT that the guest uses to accept
a pending private page, previously added by TDH.MEM.PAGE.AUG or after
conversion using the KVM_SET_MEMORY_ATTRIBUTES ioctl().
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
tools/testing/selftests
From: Ackerley Tng
vm_vaddr_alloc_private allow specifying both the virtual and physical
addresses for the allocation.
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
tools/testing/selftests/kvm/include/kvm_util.h | 3 +++
tools/testing/selftests/kvm/lib/kvm_util.c | 7 +++
From: Ackerley Tng
virt_map() enforces a private mapping for private memory. Introduce
virt_map_shared() that creates a shared mapping for private as
well as shared memory. This way, the TD does not have to remap its
page tables at runtime.
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
From: Roger Wang
Adds a test for TDG.VP.INFO.
Introduce __tdx_module_call() that does needed shuffling from function
parameters to registers used by the TDCALL instruction that is used by the
guest to communicate with the TDX module. The first function parameter is
the leaf number indicating whi
This test issues a CPUID TDVMCALL from inside the guest to get the CPUID
values as seen by KVM.
Co-developed-by: Isaku Yamahata
Signed-off-by: Isaku Yamahata
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/tdx/tdx.h | 4 +
tools/testing/selftests/kvm/lib/x86/tdx/tdx.c | 25
The test verifies MMIO writes of various sizes from the guest to the host.
Co-developed-by: Isaku Yamahata
Signed-off-by: Isaku Yamahata
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/tdx/tdx.h | 2 +
tools/testing/selftests/kvm/lib/x86/tdx/tdx.c | 14 +++
tools/testing/se
The test verifies MMIO reads of various sizes from the host to the guest.
Co-developed-by: Isaku Yamahata
Signed-off-by: Isaku Yamahata
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/tdx/tdx.h | 4 +
.../selftests/kvm/include/x86/tdx/tdx_util.h | 1 +
.../selftests/kvm/i
From: Erdem Aktas
The test verifies that the guest runs TDVMCALL and the
guest vCPU enters to the halted state.
Co-developed-by: Sagi Shahar
Signed-off-by: Sagi Shahar
Signed-off-by: Erdem Aktas
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/tdx/tdx.h | 2 +
tools/testi
The test verifies IO writes of various sizes from the guest to the host.
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/tdx/tdcall.h| 3 +
tools/testing/selftests/kvm/x86/tdx_vm_test.c | 79 ++-
2 files changed, 81 insertions(+), 1 deletion(-)
diff --git a/too
Verifies TDVMCALL READ and WRITE operations.
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/tdx/test_util.h | 20 +
.../selftests/kvm/lib/x86/tdx/test_util.c | 35 +
tools/testing/selftests/kvm/x86/tdx_vm_test.c | 78 ++-
3 files changed, 130 inserti
From: Ackerley Tng
If guest memory is backed by restricted memfd
+ UPM is being used, hence encrypted memory region has to be
registered
+ Can avoid making a copy of guest memory before getting TDX to
initialize the memory region
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
From: Erdem Aktas
TDX requires additional IOCTLs to initialize VM and vCPUs to add
private memory and to finalize the VM memory. Also additional utility
functions are provided to manipulate a TD, similar to those that
manipulate a VM in the current selftest framework.
A TD's initial register sta
From: Isaku Yamahata
Let kvm_init_vm_address_properties() initialize vm->arch.{s_bit, tag_mask}
similar to SEV.
Set shared bit position based on guest maximum physical address width
instead of maximum physical address width, because that is what KVM
uses, refer to setup_tdparams_eptp_controls(),
This is v6 of the TDX selftests that follow RFC v5 sent more than a year
ago. While it has been a while since the previous posting, the TDX
selftests kept up to date with the latest TDX development and supported
the health of the TDX base series.
With TDX base support now in kvm-coco-queue it is a
From: Ackerley Tng
One-to-one GVA to GPA mappings can be used in the guest to set up boot
sequences during which paging is enabled, hence requiring a transition
from using physical to virtual addresses in consecutive instructions.
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
...
From: Ackerley Tng
This allows initializing sregs without setting vCPU registers in
KVM.
No functional change intended.
Signed-off-by: Ackerley Tng
Signed-off-by: Sagi Shahar
---
.../selftests/kvm/include/x86/processor.h | 1 +
.../testing/selftests/kvm/lib/x86/processor.c | 45
Am Montag, dem 07.04.2025 um 21:10 +0200 schrieb André Apitzsch:
> Am Montag, dem 10.03.2025 um 23:35 +0100 schrieb André Apitzsch:
> > Hi Sakari,
> >
> > Am Montag, dem 10.03.2025 um 11:11 + schrieb Sakari Ailus:
> > > Hi André,
> > >
> > > On Sat, Mar 08, 2025 at 10:47:54PM +0100, André Api
On Sun, 13 Apr 2025 17:52:11 -0500
Ira Weiny wrote:
> Additional DCD partition (AKA region) information is contained in the
> DSMAS CDAT tables, including performance, read only, and shareable
> attributes.
>
> Match DCD partitions with DSMAS tables and store the meta data.
>
> Signed-off-by: I
Hello Jiri,
On Mon Apr 14, 2025 at 1:04 PM CEST, Jiri Olsa wrote:
> On Fri, Apr 11, 2025 at 10:32:10PM +0200, Alexis Lothoré (eBPF Foundation)
> wrote:
[...]
>> +for_each_member(i, t, member) {
>> +mtype = btf_type_by_id(btf, member->type);
>> +while (mtype && btf_ty
On Sun, 13 Apr 2025 17:52:08 -0500
Ira Weiny wrote:
> A git tree of this series can be found here:
>
> https://github.com/weiny2/linux-kernel/tree/dcd-v6-2025-04-13
>
> This is now based on 6.15-rc2.
Hi Ira,
Firstly thanks for the update and your hard work driving this forwards.
>
> D
Add msi-map for pci-ep device.
Signed-off-by: Frank Li
---
change from v14 to v16
- none
change from v13 to v14
- new patch
---
arch/arm64/boot/dts/freescale/imx95.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/freescale/imx95.dtsi
b/arch/arm64/boot/dts/freescale/
Doorbell feature is implemented by mapping the EP's MSI interrupt
controller message address to a dedicated BAR in the EPC core. It is the
responsibility of the EPF driver to pass the actual message data to be
written by the host to the doorbell BAR region through its own logic.
Tested-by: Niklas
Add doorbell test case.
Signed-off-by: Frank Li
---
change from v14 to v16
- Add set IRQ type
change from v13 to v14
- merge to selftests framework
---
.../selftests/pci_endpoint/pci_endpoint_test.c | 28 ++
1 file changed, 28 insertions(+)
diff --git a/tools/testing/se
Support only one physical function, so call imx_pcie_add_lut_by_rid(0)
to add a single LUT entry when operating in EP mode.
Signed-off-by: Frank Li
---
change from v14 to v16
- none
change from v13 to v14
- new patch
---
drivers/pci/controller/dwc/pci-imx6.c | 8 +++-
1 file changed, 7 inse
On Tue, 2025-04-08 at 19:49 +0100, Mark Brown wrote:
> +int arch_shstk_validate_clone(struct task_struct *t,
> + struct vm_area_struct *vma,
> + struct page *page,
> + struct kernel_clone_args *args)
> +{
> + /*
> +
Powering off RPU using force_pwrdwn call results in system failure
if there are multiple users of that RPU node. Better mechanism is to use
request_node and release_node EEMI calls. With use of these EEMI calls,
platform management controller will take-care of powering off RPU
when there is no user
Document the use of (msi|iommu)-map for PCI Endpoint (EP) controllers,
which can use MSI as a doorbell mechanism. Each EP controller can support
up to 8 physical functions and 65,536 virtual functions.
Define how to construct device IDs using function bits [2:0] and virtual
function index bits [31
Add helper function imx_pcie_add_lut_by_rid(), which will be used for
Endpoint mode in the future. No functional change.
Signed-off-by: Frank Li
---
change from v14 to v16
- none
change from v13 to v14
- new patch
---
drivers/pci/controller/dwc/pci-imx6.c | 17 ++---
1 file changed,
Introduce the helper function pci_epf_align_inbound_addr() to adjust
addresses according to PCI BAR alignment requirements, converting addresses
into base and offset values.
Signed-off-by: Frank Li
---
Change from v15 to v16
- none
Change from v14 to v15
- change out address type to dma_addr_t t
Add three registers: PCIE_ENDPOINT_TEST_DB_BAR, PCIE_ENDPOINT_TEST_DB_ADDR,
and PCIE_ENDPOINT_TEST_DB_DATA.
Trigger the doorbell by writing data from PCI_ENDPOINT_TEST_DB_DATA to the
address provided by PCI_ENDPOINT_TEST_DB_OFFSET and wait for endpoint
feedback.
Add two command to COMMAND_ENABLE_
Add three registers: doorbell_bar, doorbell_addr, and doorbell_data. Use
pci_epf_alloc_doorbell() to allocate a doorbell address space.
Enable the Root Complex (RC) side driver to trigger pci-epc-test's doorbell
callback handler by writing doorbell_data to the mapped doorbell_bar's
address space.
Some MSI controller change address/data pair when irq_set_affinity().
Current PCI endpoint can't support this type MSI controller. So add flag
MSI_FLAG_MUTABLE in include/linux/msi.h and check it when allocate
doorbell.
Signed-off-by: Frank Li
---
change from v14 to v16
- none
change from v13 t
Set device ID as 'vfunc_no << 3 | func_no' and use
'device_set_of_node_from_dev()' to set 'of_node' the same as the EPC parent
device.
Currently, EPF 'of_node' is NULL, but many functions depend on 'of_node'
settings, such as DMA, IOMMU, and MSI. At present, all DMA allocation
functions use the EP
Some platform devices create child devices dynamically and require the
parent device's msi-map to map device IDs to actual sideband information.
A typical use case is using ITS as a PCIe Endpoint Controller(EPC)'s
doorbell function, where PCI hosts send TLP memory writes to the EP
controller. The
Set the IRQ_DOMAIN_FLAG_MSI_IMMUTABLE flag for ITS, as it does not change
the address/data pair after setup.
Ensure compatibility with MSI users, such as PCIe Endpoint Doorbell, which
require the address/data pair to remain unchanged. Enable PCIe endpoints to
use ITS for triggering doorbells from
Add the flag IRQ_DOMAIN_FLAG_MSI_IMMUTABLE and the API function
irq_domain_is_msi_immutable() to check if the MSI controller retains an
immutable address/data pair during irq_set_affinity().
Ensure compatibility with MSI users like PCIe Endpoint Doorbell, which
require the address/data pair to rem
platform_device_msi_init_and_alloc_irqs() performs two tasks: allocating
the MSI domain for a platform device, and allocate a number of MSIs in that
domain.
platform_device_msi_free_irqs_all() only frees the MSIs, and leaves the MSI
domain alive.
Given that platform_device_msi_init_and_alloc_irqs
On Mon, Apr 14, 2025 at 08:01:42PM +0200, Michal Koutný wrote:
> On Mon, Apr 14, 2025 at 12:47:21PM -0400, Johannes Weiner
> wrote:
> > It's not a functional change to the protection semantics or the
> > reclaim behavior.
>
> Yes, that's how I understand it, therefore I'm wondering what does it
On Mon, Apr 14, 2025 at 03:55:39PM +0200, Michal Koutný wrote:
> On Mon, Apr 14, 2025 at 09:15:57AM -0400, Waiman Long
> wrote:
> > I did see some low event in the no usage case because of the ">=" comparison
> > used in mem_cgroup_below_min().
>
> Do you refer to A/B/E or A/B/F from the test?
>
On Fri, Apr 11, 2025 at 10:32:45AM +0200, Stefano Garzarella wrote:
> On Thu, Apr 10, 2025 at 06:07:59PM -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 are designed to
> > validate both G2H an
Hi Michael,
On 4/14/25 9:32 AM, Michael S. Tsirkin wrote:
> On Wed, Apr 02, 2025 at 11:29:54PM -0700, Dongli Zhang wrote:
>> Since long time ago, the only user of vq->log is vhost-net. The concern is
>> to add support for more devices (i.e. vhost-scsi or vsock) may reveals
>> unknown issue in the
F(6667, P_GPLL0, 12, 0, 0),
{ }
};
---
base-commit: b425262c07a6a643ebeed91046e161e20b944164
change-id: 20250414-gcc-msm8939-fixes-mclk-v2-resend2-9458a45e3629
Best regards,
--
Vincent Knecht
On Wed, Apr 02, 2025 at 11:29:54PM -0700, Dongli Zhang wrote:
> Since long time ago, the only user of vq->log is vhost-net. The concern is
> to add support for more devices (i.e. vhost-scsi or vsock) may reveals
> unknown issue in the vhost API. Add a WARNING.
>
> Suggested-by: Joao Martins
> Sig
On Mon, Apr 14, 2025 at 10:56:24AM -0400, Joel Fernandes wrote:
> On 4/14/2025 10:24 AM, Paul E. McKenney wrote:
> > On Mon, Apr 14, 2025 at 08:07:24AM -0400, Joel Fernandes wrote:
> >>> On Apr 11, 2025, at 3:18 PM, Paul E. McKenney wrote:
> >>> On Fri, Apr 11, 2025 at 05:36:32AM -, Joel Fern
On Sun, 13 Apr 2025 17:52:24 -0500
Ira Weiny wrote:
> Dynamic capacity device extents may be left in an accepted state on a
> device due to an unexpected host crash. In this case it is expected
> that the creation of a new region on top of a DC partition can read
> those extents and surface them
On Sun, Apr 13, 2025 at 05:52:08PM -0500, Ira Weiny wrote:
> A git tree of this series can be found here:
>
> https://github.com/weiny2/linux-kernel/tree/dcd-v6-2025-04-13
>
> This is now based on 6.15-rc2.
>
> Due to the stagnation of solid requirements for users of DCD I do not
> plan to
On Sun, 13 Apr 2025 17:52:20 -0500
Ira Weiny wrote:
> A dynamic capacity device (DCD) sends events to signal the host for
> changes in the availability of Dynamic Capacity (DC) memory. These
> events contain extents describing a DPA range and meta data for memory
> to be added or removed. Event
On Thu, Apr 10, 2025 at 12:30:30AM +0300, Iuliana Prodan (OSS) wrote:
> 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 resou
On Sun, 13 Apr 2025 17:52:15 -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. CX
On Sun, 13 Apr 2025 17:52:14 -0500
Ira Weiny wrote:
> Endpoints can now support a single dynamic ram partition following the
> persistent memory partition.
>
> Expand the mode to allow a decoder to point to the first dynamic ram
> partition.
>
> Signed-off-by: Ira Weiny
Reviewed-by: Jonathan
On Sun, 13 Apr 2025 17:52:13 -0500
Ira Weiny wrote:
> To properly configure CXL regions user space will need to know the
> details of the dynamic ram partition.
>
> Expose the first dynamic ram partition through sysfs.
>
> Signed-off-by: Ira Weiny
>
LGTM
Reviewed-by: Jonathan Cameron
On Sun, 13 Apr 2025 17:52:12 -0500
Ira Weiny wrote:
> Device partitions have an implied order which is made more complex by
> the addition of a dynamic partition.
>
> Remove the ram special case information calls in favor of generic calls
> with a check ahead of time to ensure the preservation o
On Mon, Apr 14, 2025 at 08:07:24AM -0400, Joel Fernandes wrote:
>
>
> > On Apr 11, 2025, at 3:18 PM, Paul E. McKenney wrote:
> >
> > On Fri, Apr 11, 2025 at 05:36:32AM -, Joel Fernandes wrote:
> >> Hello, Paul,
> >>
> >>> On Fri, 11 Apr 2025 05:33:16 GMT, "Paul E. McKenney" wrote:
> >>> O
On 4/10/2025 2:29 PM, Paul E. McKenney wrote:
>> +static int rcu_gpwrap_lag_init(void)
>> +{
>> +if (gpwrap_lag_cycle_mins <= 0 || gpwrap_lag_active_mins <= 0) {
>> +pr_alert("rcu-torture: lag timing parameters must be
>> positive\n");
>> +return -EINVAL;
> When rcutort
On Sun, 13 Apr 2025 17:52:10 -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.
> Without the Get DC Confi
On 4/14/2025 10:24 AM, Paul E. McKenney wrote:
> On Mon, Apr 14, 2025 at 08:07:24AM -0400, Joel Fernandes wrote:
>>
>>
>>> On Apr 11, 2025, at 3:18 PM, Paul E. McKenney wrote:
>>>
>>> On Fri, Apr 11, 2025 at 05:36:32AM -, Joel Fernandes wrote:
Hello, Paul,
> On Fri, 11 Apr 20
Enabling a (modular) test should not silently enable additional kernel
functionality, as that may increase the attack vector of a product.
Fix this by making PRIME_NUMBERS_KUNIT_TEST depend on PRIME_NUMBERS
instead of selecting it.
After this, one can safely enable CONFIG_KUNIT_ALL_TESTS=m to bui
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
Hi Zhijian,
We recreated the failure for the cases you mentioned below. We will be
adding the fix into v4 I am working on now.
Regards,
Terry
On 4/7/2025 2:31 AM, Zhijian Li (Fujitsu) wrote:
> Hi Terry,
>
> If I understand correctly, this patch set has only considered the situation
> where t
Hi, Bibo,
On Thu, Apr 10, 2025 at 11:57 AM Bibo Mao wrote:
>
> 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/selft
On Mon, Apr 14, 2025 at 09:15:57AM -0400, Waiman Long wrote:
> I did see some low event in the no usage case because of the ">=" comparison
> used in mem_cgroup_below_min().
Do you refer to A/B/E or A/B/F from the test?
It's OK to see some events if there was non-zero usage initially.
Neverthele
Hello Bjorn,
Gentle reminder.
For your information, I proposed to Mathieu that he wait for your first review,
as this revision is intended to address your comments on revision 15."
Thanks,
Arnaud
On 3/25/25 10:58, Arnaud Pouliquen wrote:
> Main updates from version V15[1]:
> - Removed the rpro
-Cc: non-lists
On Tue, Mar 04, 2025 at 03:20:58PM +0100, Michal Koutný
wrote:
> Actually, I noticed test_memcontrol failure yesterday (with ~mainline
> kernel) but I remember they used to work also rather recently. I haven't
> got time to look into that but at least that one may be a regression
On 11/04/2025 23:18, Jakub Kicinski wrote:
On Fri, 11 Apr 2025 15:50:49 +0200 Sabrina Dubroca wrote:
My understanding is that this is the standard approach to:
1) hook in the middle of registration/deregistration;
2) handle events generated by other components/routines.
I see in /drivers/net/ a
On Mon, Apr 14, 2025 at 5:02 AM Geert Uytterhoeven wrote:
>
> On Mon, 14 Apr 2025 at 10:50, Geert Uytterhoeven wrote:
> > Enabling a (modular) test should not silently enable additional kernel
> > functionality, as that may increase the attack vector of a product.
> >
> > Fix this by making PRIME
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
From: Qiuxu Zhuo
[ Upstream commit 197c1eaa7ba633a482ed7588eea6fd4aa57e08d4 ]
When running the mincore_selftest on a system with an XFS file system, it
failed the "check_file_mmap" test case due to the read-ahead pages reaching
the end of the file. The failure log is as below:
RUN
On 4/14/25 8:42 AM, Michal Koutný wrote:
On Sun, Apr 13, 2025 at 10:12:48PM -0400, Waiman Long
wrote:
2) memory.low is set to a non-zero value but the cgroup has no task in
it so that it has an effective low value of 0. Again it may have a
non-zero low event count if memory reclaim h
On Sun, Apr 13, 2025 at 10:12:48PM -0400, Waiman Long
wrote:
> 2) memory.low is set to a non-zero value but the cgroup has no task in
>it so that it has an effective low value of 0. Again it may have a
>non-zero low event count if memory reclaim happens. This is probably
>not a result
> On Apr 11, 2025, at 3:18 PM, Paul E. McKenney wrote:
>
> On Fri, Apr 11, 2025 at 05:36:32AM -, Joel Fernandes wrote:
>> Hello, Paul,
>>
>>> On Fri, 11 Apr 2025 05:33:16 GMT, "Paul E. McKenney" wrote:
>>> On Thu, Apr 10, 2025 at 11:54:13AM -0700, Paul E. McKenney wrote:
On Thu, Apr
On Mon, Apr 14, 2025 at 12:08:35PM +0700, Bui Quang Minh wrote:
> When pausing rx (e.g. set up xdp, xsk pool, rx resize), we call
> napi_disable() on the receive queue's napi. In delayed refill_work, it
> also calls napi_disable() on the receive queue's napi. When
> napi_disable() is called on an
On Fri, Apr 11, 2025 at 10:32:10PM +0200, Alexis Lothoré (eBPF Foundation)
wrote:
> In order to properly JIT the trampolines needed to attach BPF programs
> to functions, some architectures like ARM64 need to know about the
> alignment needed for the function arguments. Such alignment can
> genera
On Fri, 11 Apr 2025 17:09:40 +0200, Nam Cao wrote:
> While trying the coredump test on qemu-system-riscv64, I observed test
> failures for various reasons.
>
> This series makes the test works on qemu-system-riscv64.
>
> Best regards,
> Nam
>
> [...]
Applied to the vfs-6.16.coredump branch of t
On Mon, Apr 14, 2025 at 05:32:47PM +0800, Huacai Chen wrote:
> Hi, Thomas,
>
> On Mon, Apr 14, 2025 at 4:29 PM Thomas Weißschuh
> wrote:
> >
> > Not all tasks have an ABI associated or vDSO mapped,
> > for example kthreads never do.
> > If such a task ever ends up calling stack_top(), it will der
On Sun, Apr 13, 2025 at 01:06:26AM +0800, KaFai Wan wrote:
> Adding verifier test for accessing const void pointer argument in
> tracing programs.
>
> The test program loads 2nd argument of kfree tp_btf which is
> const void pointer and checks that verifier allows that.
>
> Signed-off-by: KaFai W
On Sun, Apr 13, 2025 at 01:06:25AM +0800, KaFai Wan wrote:
> Adding support to access arguments with const void pointer arguments
> in tracing programs.
>
> Currently we allow tracing programs to access void pointers. If we try to
> access argument which is pointer to const void like 2nd argument
1 - 100 of 109 matches
Mail list logo
