Add verbosity support to show the commands executed while
running tests. Enable verbosity if either an environment
variable 'VERBOSE' is set to a non-zero number or it is defined
in a config file under driver tests as discussed here:
https://github.com/linux-netdev/nipa/wiki/Running-driver-tests.
Hi Jakub,
On Fri, 2 Aug 2024 at 16:18, Jakub Kicinski wrote:
>
> On Fri, 02 Aug 2024 10:23:24 +0100 Dmitry Safonov via B4 Relay wrote:
> > First 4 patches are more-or-less cleanups/preparations.
> >
> > Patch 5 was sent to me/contributed off-list by Mohammad, who wants 32-bit
> > kernels to run T
Define an IOMMU_RESV_SW_MSI region (within the mock aperture) as the ARM
SMMU drivers do.
Implement the get_msi_mapping_domain nested domain op to allow dma-iommu
to find the correct paging domain.
Add a new IOMMU_TEST_OP_MD_CHECK_SW_MSI to loopback test the MSI mapping
using public dma-iommu and
PATCH-1 is an optional cleanup. PATCH-2 is an essential infrastructure
for PATCH-3 to verify the loopback for IOMMU_RESV_SW_MSI.
You can find this series applied on the other two earlier patches here:
https://github.com/nicolinc/iommufd/commits/iommufd_selftest_sw_msi/
[changelog]
v2:
* Resent w
From: Robin Murphy
Currently, iommu-dma is the only place outside of IOMMUFD and drivers
which might need to be aware of the stage 2 domain encapsulated within
a nested domain. This would be in the legacy-VFIO-style case where we're
using host-managed MSIs with an identity mapping at stage 1, whe
Reorder include files to alphabetic order to simplify maintenance, and
separate local headers and global headers with a blank line.
No functional change intended.
Signed-off-by: Nicolin Chen
---
drivers/iommu/iommufd/device.c | 4 ++--
drivers/iommu/iommufd/fault.c | 4 ++--
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Thu, 1 Aug 2024 17:03:07 -0700 you wrote:
> Verify that total device stats don't decrease after it has been turned down.
> Also make sure the device doesn't crash when we access per-queue stats
> when it's down (
On 8/1/24 23:38, Muhammad Usama Anjum wrote:
On 8/1/24 9:27 PM, Shuah Khan wrote:
On 8/1/24 02:42, Muhammad Usama Anjum wrote:
On 7/31/24 9:57 PM, Shuah Khan wrote:
On 7/31/24 07:39, Muhammad Usama Anjum wrote:
Don't print that 88 sub-tests are going to be executed, but then skip.
This is aga
Currently the get-reg-list test uses directly specified numeric values to
define system registers to validate. Since we already have a macro which
allows us to use the generated system register definitions from the main
kernel easily let's update all the registers where we have specified the
name i
Since we already import the generated sysreg definitions from the main
kernel and reference them in processor.h for use in other KVM tests we
can also make use of them for get-reg-list as well instead of having hard
coded magic numbers in the program. Do this for the table defining which
registers
)
---
base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
change-id: 20240802-kvm-arm64-get-reg-list-a86a37460bdd
Best regards,
--
Mark Brown
On Fri, Aug 02, 2024 at 02:23:45PM -0700, Nicolin Chen wrote:
> This adds a small series to cover the reserved-IOVA change:
> https://lore.kernel.org/all/20240802053458.2754673-1-nicol...@nvidia.com/
>
> PATCH-1 is an optional cleanup. PATCH-2 is an essential infrastructure
> for PATCH-3 to verify
On Fri, Aug 02, 2024 at 06:13:37PM +0200, Alessandro Zanni wrote:
> Inserted raw strings because Python3 interpretes string literals as Unicode
> strings,
> so '\d' is considered an invalid escaped sequence but this is not the case.
> This fix avoids the "SyntaxWarning: invalid escape sequence '\d
Define an IOMMU_RESV_SW_MSI region (within the mock aperture) as the ARM
SMMU drivers do.
Implement the get_msi_mapping_domain nested domain op to allow dma-iommu
to find the correct paging domain.
Add a new IOMMU_TEST_OP_MD_CHECK_SW_MSI to loopback test the MSI mapping
using public dma-iommu and
From: Robin Murphy
Currently, iommu-dma is the only place outside of IOMMUFD and drivers
which might need to be aware of the stage 2 domain encapsulated within
a nested domain. This would be in the legacy-VFIO-style case where we're
using host-managed MSIs with an identity mapping at stage 1, whe
Reorder include files to alphabetic order to simplify maintenance, and
separate local headers and global headers with a blank line.
No functional change intended.
Signed-off-by: Nicolin Chen
---
drivers/iommu/iommufd/device.c | 4 ++--
drivers/iommu/iommufd/fault.c | 4 ++--
This adds a small series to cover the reserved-IOVA change:
https://lore.kernel.org/all/20240802053458.2754673-1-nicol...@nvidia.com/
PATCH-1 is an optional cleanup. PATCH-2 is an essential infrastructure
for PATCH-3 to verify the loopback for IOMMU_RESV_SW_MSI.
You can find this series applied o
On 8/2/24 09:48, Thomas Weißschuh wrote:
On 2024-07-31 17:01:09+, Shuah Khan wrote:
On 7/31/24 12:32, Thomas Weißschuh wrote:
The implementation is limited and only supports numeric arguments.
I would like to see more information in here. Why is this needed
etc. etc.
Ack.
Signed-off-
On 11/9/23 11:04, Konstantin Ryabitsev wrote:
On Thu, Nov 09, 2023 at 06:44:44PM +0100, Thomas Weißschuh wrote:
On Wed, Sep 15, 2077 at 02:13:51AM +0200, Thomas Weißschuh wrote:
I'm curious how this happened, especially since this was sent with b4.
My system time was me
Test PerfMonV2, which defines global registers to enable multiple
performance counters with a single MSR write, in its own function.
If the feature is available, ensure the global control register has
the ability to start and stop the performance counters and the global
status register correctly f
Test events on core counters by iterating through every combination of
events in amd_pmu_zen_events with every core counter.
For each combination, calculate the appropriate register addresses for
the event selection/control register and the counter register. The
base addresses and layout schemes c
Run a basic test to ensure we can write an arbitrary value to the core
counters and read it back.
Signed-off-by: Colton Lewis
---
.../selftests/kvm/x86_64/pmu_counters_test.c | 41 +++
1 file changed, 41 insertions(+)
diff --git a/tools/testing/selftests/kvm/x86_64/pmu_counters
Branch in main() depending on if the CPU is Intel or AMD. They are
subject to vastly different requirements because the AMD PMU lacks
many properties defined by the Intel PMU including the entire CPUID
0xa function where Intel stores all the PMU properties. AMD lacks this
as well as any consistent
This defined the CPUID calls to determine what extensions and
properties are available. AMD reference manual names listed below.
* PerfCtrExtCore (six core counters instead of four)
* PerfCtrExtNB (four counters for northbridge events)
* PerfCtrExtL2I (four counters for L2 cache events)
* PerfMonV
Without the leading underscore, these variables are referencing a
variable in the calling scope. It only worked before by accident
because all calling scopes had a variable with the right name.
Signed-off-by: Colton Lewis
---
tools/testing/selftests/kvm/x86_64/pmu_counters_test.c | 6 +++---
1 f
Extend pmu_counters_test to AMD CPUs.
As the AMD PMU is quite different from Intel with different events and
feature sets, this series introduces a new code path to test it,
specifically focusing on the core counters including the
PerfCtrExtCore and PerfMonV2 features. Northbridge counters and cac
On Fri Aug 2, 2024 at 1:58 AM EEST, Shuah Khan wrote:
> On 8/1/24 16:24, Jarkko Sakkinen wrote:
> > On Wed Jul 31, 2024 at 8:45 PM EEST, Shuah Khan wrote:
> >> On 7/31/24 07:42, Muhammad Usama Anjum wrote:
> >>> Reminder
> >>>
> >>
> >> top post???
> >>
> >>> On 7/10/24 1:15 PM, Muhammad Usama Anju
On Wed, Jul 31, 2024 at 3:02 AM David Gow wrote:
>
> kunit_driver_create() accepts a name for the driver, but does not copy
> it, so if that name is either on the stack, or otherwise freed, we end
> up with a use-after-free when the driver is cleaned up.
>
> Instead, strdup() the name, and manage
Inserted raw strings because Python3 interpretes string literals as Unicode
strings,
so '\d' is considered an invalid escaped sequence but this is not the case.
This fix avoids the "SyntaxWarning: invalid escape sequence '\d'" warning
for Python versions greater than 3.6.
Signed-off-by: Alessandr
On 2024-08-01 13:06, Mark Brown wrote:
> The arm64 Guarded Control Stack (GCS) feature provides support for
> hardware protected stacks of return addresses, intended to provide
> hardening against return oriented programming (ROP) attacks and to make
> it easier to gather call stacks for applicatio
Add a test case manipulating s390 storage keys from within the ucontrol
VM.
Signed-off-by: Christoph Schlameuss
---
.../selftests/kvm/s390x/ucontrol_test.c | 78 +++
1 file changed, 78 insertions(+)
diff --git a/tools/testing/selftests/kvm/s390x/ucontrol_test.c
b/tools/te
Add test case running code interacting with registers within a
ucontrol VM.
* Add uc_gprs test case
The test uses the same VM setup using the fixture and debug macros
introduced in earlier patches in this series.
Signed-off-by: Christoph Schlameuss
---
.../selftests/kvm/s390x/ucontrol_test.c
Add a uc_kvm fixture to create and destroy a ucontrol VM.
* uc_sie_assertions asserts basic settings in the SIE as setup by the
kernel.
* uc_attr_mem_limit asserts the memory limit is max value and cannot be
set (not supported).
* uc_no_dirty_log asserts dirty log is not supported.
Signed-off
Subsequent tests do require direct manipulation of the SIE control
block. This commit introduces the SIE control block definition for use
within the selftests.
There are already definitions of this within the kernel.
This differs in two ways.
* This is the first definition of this in userspace.
*
This patch series adds a selftest suite to validate the s390x
architecture specific ucontrol KVM interface.
When creating a VM on s390x it is possible to create it as userspace
controlled VM or in short ucontrol VM.
These VMs delegates the management of the VM to userspace instead
of handling most
To simplify testing enable UCONTROL KVM by default in debug kernels.
Signed-off-by: Christoph Schlameuss
Reviewed-by: Janosch Frank
---
arch/s390/configs/debug_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/s390/configs/debug_defconfig
b/arch/s390/configs/debug_defconfig
in
Add a test case verifying KVM_SET_USER_MEMORY_REGION and
KVM_SET_USER_MEMORY_REGION2 cannot be executed on ucontrol VMs.
Executing this test case on not patched kernels will cause a null
pointer dereference in the host kernel.
This is fixed with commit:
commit 7816e58967d0 ("kvm: s390: Reject memo
Multiple test cases need page size and shift definitions.
By moving the definitions to a single architecture specific header we
limit the repetition.
Make use of PAGE_SIZE, PAGE_SHIFT and PAGE_MASK defines in existing
code.
Signed-off-by: Christoph Schlameuss
Reviewed-by: Claudio Imbrenda
Revie
Add a test case verifying basic running and interaction of ucontrol VMs.
Fill the segment and page tables for allocated memory and map memory on
first access.
* uc_map_unmap
Store and load data to mapped and unmapped memory and use pic segment
translation handling to map memory on access.
Sig
Add functions to simply print some basic state information in selftests.
The output can be enabled by setting:
#define TH_LOG_ENABLED 1
#define DEBUG 1
* print_psw: current SIE state description and VM run state
* print_hex_bytes: print memory with some counting markers
* print_hex: PRIN
Add test suite to validate the s390x architecture specific ucontrol KVM
interface.
Make use of the selftest test harness.
* uc_cap_hpage testcase verifies that a ucontrol VM cannot be run with
hugepages.
To allow testing of the ucontrol interface the kernel needs a
non-default config containin
On 2024-07-31 17:01:09+, Shuah Khan wrote:
> On 7/31/24 12:32, Thomas Weißschuh wrote:
> > The implementation is limited and only supports numeric arguments.
>
> I would like to see more information in here. Why is this needed
> etc. etc.
Ack.
> >
> > Signed-off-by: Thomas Weißschuh
> > --
On Thu, Aug 01, 2024 at 10:04:36PM +, Bird, Tim wrote:
>
>
> > -Original Message-
> > From: Nícolas F. R. A. Prado
> > On Thu, Aug 01, 2024 at 02:13:05PM -0600, Shuah Khan wrote:
> > > On 8/1/24 13:15, Nícolas F. R. A. Prado wrote:
> > > > On Wed, Jul 31, 2024 at 05:19:45PM -0600, Sh
On Fri, Aug 02, 2024 at 02:36:14PM +0100, Marc Zyngier wrote:
> Mark Brown wrote:
> > > Not for a point fix, for sure. And if you do, make sure it is entirely
> > > scripted.
> > When you say "entirely scripted" here I take it you're referring to the
> > list of registers as well, and I guess al
On Fri, 2 Aug 2024 08:18:23 -0700 Jakub Kicinski wrote:
> On Fri, 02 Aug 2024 10:23:24 +0100 Dmitry Safonov via B4 Relay wrote:
> > First 4 patches are more-or-less cleanups/preparations.
> >
> > Patch 5 was sent to me/contributed off-list by Mohammad, who wants 32-bit
> > kernels to run TCP-AO.
>
On Fri, 02 Aug 2024 10:23:24 +0100 Dmitry Safonov via B4 Relay wrote:
> First 4 patches are more-or-less cleanups/preparations.
>
> Patch 5 was sent to me/contributed off-list by Mohammad, who wants 32-bit
> kernels to run TCP-AO.
>
> Patch 6 is a workaround/fix for slow VMs. Albeit, I can't repr
On Fri, 02 Aug 2024 13:43:03 +0100,
Mark Brown wrote:
>
> [1 ]
> On Fri, Aug 02, 2024 at 10:00:28AM +0100, Marc Zyngier wrote:
>
> > Also, the test predates the generated stuff by some margin.
>
> Yeah, there were still defines in the main kernel source that were being
> retyped rather than sh
Hello Davide,
In the following commit:
commit ca22da2fbd693b54dc8e3b7b54ccc9f7e9ba3640
Author: Davide Caratti
Date: Fri Jan 20 18:01:40 2023 +0100
act_mirred: use the backlog for nested calls to mirred ingress
you added the mirred_egress_to_ingress_tcp_test kselftest that, I noticed,
ha
CONFIG_RUST depends on !CONFIG_GCC_PLUGINS. Disable CONFIG_GCC_PLUGINS
in rust/config file to make sure it doesn't get enabled.
Signed-off-by: Anders Roxell
---
tools/testing/selftests/rust/config | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/rust/config
b/tools/te
If adding multiple config files to the merge_config.sh script and
rust/config is the fist one, then the last config fragment in this file
and the first config fragment in the second file wont be set, since
there isn't a newline in this file, so those two fragements end up at
the same row like:
CONF
On Fri, Aug 02, 2024 at 10:00:28AM +0100, Marc Zyngier wrote:
> Also, the test predates the generated stuff by some margin.
Yeah, there were still defines in the main kernel source that were being
retyped rather than shared previously which made me wonder.
> Mark Brown wrote:
> > I'd certainly
On Fri, Aug 02, 2024 at 08:26:48AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Thursday, June 20, 2024 10:34 PM
> >
> > On Thu, Jun 20, 2024 at 04:14:23PM +0200, David Hildenbrand wrote:
> >
> > > 1) How would the device be able to grab/access "private memory", if not
> > >
From: Dmitry Safonov <0x7f454...@gmail.com>
Setup trace points, add a new ftrace instance in order to not interfere
with the rest of the system, filtering by net namespace cookies.
Raise a new background thread that parses trace_pipe, matches them with
the list of expected events.
Wiring up trace
From: Dmitry Safonov <0x7f454...@gmail.com>
On tests that are expecting failure the timeout value is
TEST_RETRANSMIT_SEC == 1 second. Which is big enough for most of devices
under tests. But on a particularly slow machine/VM, 1 second might be
not enough for another thread to be scheduled and atte
From: Dmitry Safonov <0x7f454...@gmail.com>
Instead of pre-allocating a fixed-sized buffer of TEST_MSG_BUFFER_SIZE
and printing into it, call vsnprintf() with str = NULL, which will
return the needed size of the buffer. This hack is documented in
man 3 vsnprintf.
Essentially, in C++ terms, it re-
From: Dmitry Safonov <0x7f454...@gmail.com>
The switch_save_ns() helper suppose to help switching to another
namespace for some action and to return back to original namespace.
The fd should be closed.
Signed-off-by: Dmitry Safonov <0x7f454...@gmail.com>
---
tools/testing/selftests/net/tcp_ao/l
From: Mohammad Nassiri
It's not safe to use '%zu' specifier for printing uint64_t on 32-bit
systems. For uint64_t, we should use the 'PRIu64' macro from
the inttypes.h library. This ensures that the uint64_t is printed
correctly from the selftests regardless of the system architecture.
Signed-of
From: Dmitry Safonov <0x7f454...@gmail.com>
Correct copy'n'paste typo: the previous line already initialises get_all
to 1.
Reported-by: Nassiri, Mohammad
Closes:
https://lore.kernel.org/all/dm6pr04mb4202bc58a9fd5bdd24a16e8ec5...@dm6pr04mb4202.namprd04.prod.outlook.com/
Signed-off-by: Dmitry Saf
From: Dmitry Safonov <0x7f454...@gmail.com>
Most of the functions in tcp-ao lib/ return negative errno or -1 in case
of a failure. That creates inconsistencies in lib/kconfig, which saves
what was the error code. As well as the uninitialized kconfig value is
-1, which also may be the result of a c
First 4 patches are more-or-less cleanups/preparations.
Patch 5 was sent to me/contributed off-list by Mohammad, who wants 32-bit
kernels to run TCP-AO.
Patch 6 is a workaround/fix for slow VMs. Albeit, I can't reproduce
the issue, but I hope it will fix netdev flakes for connect-deny-*
tests.
A
On Thu, 01 Aug 2024 20:14:38 +0100,
Mark Brown wrote:
>
> [1 ]
> On Thu, Aug 01, 2024 at 05:45:49PM +0100, Marc Zyngier wrote:
>
> > Can we please switch all this stuff to symbolic naming instead of
> > magic numbers? Given how much effort is going into the "automated
> > generation" thing, it
> From: Jason Gunthorpe
> Sent: Thursday, June 20, 2024 10:34 PM
>
> On Thu, Jun 20, 2024 at 04:14:23PM +0200, David Hildenbrand wrote:
>
> > 1) How would the device be able to grab/access "private memory", if not
> >via the user page tables?
>
> The approaches I'm aware of require the secu
Hello Jakub,
On Thu, Aug 01, 2024 at 09:53:22AM -0700, Jakub Kicinski wrote:
> On Thu, 1 Aug 2024 09:11:58 -0700 Breno Leitao wrote:
> > .../net/netconsole/basic_integration_test.sh | 153 ++
>
> It needs to be included in a Makefile
> If we only have one script I'd put it direc
63 matches
Mail list logo
