On Fri, Oct 13, 2023 at 09:07:09PM -0300, Jason Gunthorpe wrote:
> On Fri, Oct 13, 2023 at 01:58:59PM -0700, Nicolin Chen wrote:
> > On Fri, Oct 13, 2023 at 12:19:23PM -0300, Jason Gunthorpe wrote:
> > > On Thu, Sep 21, 2023 at 12:51:31AM -0700, Yi Liu wrote:
> > > > IOMMU_HWPT_ALLOC already suppor
On Thu, Oct 12, 2023 at 05:13:59PM +0800, Yi Liu wrote:
> > > @@ -241,6 +245,21 @@ struct iommu_user_data {
> > > size_t len;
> > > };
> > >
> > > +/**
> > > + * struct iommu_user_data_array - iommu driver specific user space data
> > > array
> > > + * @uptr: Pointer to the user buffer a
On Tue, Sep 26, 2023 at 01:16:35AM -0700, Tian, Kevin wrote:
> > From: Liu, Yi L
> > Sent: Thursday, September 21, 2023 3:51 PM
> >
> > From: Nicolin Chen
> >
> > Now enforce_cache_coherency and msi_cookie are kernel-managed hwpt
> > things.
> > So, they should be only setup on kernel-managed dom
On Tue, Sep 26, 2023 at 01:14:47AM -0700, Tian, Kevin wrote:
> > From: Liu, Yi L
> > Sent: Thursday, September 21, 2023 3:51 PM
> >
> > +static void iommufd_user_managed_hwpt_abort(struct iommufd_object
> > *obj)
> > +{
> > + struct iommufd_hw_pagetable *hwpt =
> > + container_of(o
On Fri, Oct 13, 2023 at 01:58:59PM -0700, Nicolin Chen wrote:
> On Fri, Oct 13, 2023 at 12:19:23PM -0300, Jason Gunthorpe wrote:
> > On Thu, Sep 21, 2023 at 12:51:31AM -0700, Yi Liu wrote:
> > > IOMMU_HWPT_ALLOC already supports iommu_domain allocation for usersapce.
> > > But it can only allocate
kselftest/next kselftest-lib: 3 runs, 3 regressions (v6.6-rc2-43-g508934b5d15ab)
Regressions Summary
---
platform | arch | lab | compiler | defconfig
| regressions
-+---+---+--+-
kselftest/next kselftest-seccomp: 4 runs, 3 regressions
(v6.6-rc2-43-g508934b5d15ab)
Regressions Summary
---
platform | arch | lab | compiler | defconfig
| regressions
-+---+---+---
kselftest/next kselftest-lkdtm: 3 runs, 2 regressions
(v6.6-rc2-43-g508934b5d15ab)
Regressions Summary
---
platform | arch | lab | compiler | defconfig
| regressions
-+---+---+-
kselftest/next kselftest-livepatch: 1 runs, 1 regressions
(v6.6-rc2-43-g508934b5d15ab)
Regressions Summary
---
platform| arch | lab | compiler | defconfig
| regressions
+---+---+--+
kselftest/next kselftest-cpufreq: 7 runs, 3 regressions
(v6.6-rc2-43-g508934b5d15ab)
Regressions Summary
---
platform | arch | lab | compiler | defconfig
| regressions
-+---+---+---
kselftest/next build: 6 builds: 0 failed, 6 passed, 1 warning
(v6.6-rc2-43-g508934b5d15ab)
Full Build Summary:
https://kernelci.org/build/kselftest/branch/next/kernel/v6.6-rc2-43-g508934b5d15ab/
Tree: kselftest
Branch: next
Git Describe: v6.6-rc2-43-g508934b5d15ab
Git Commit: 508934b5d15ab79fd5
On Fri, Oct 13, 2023 at 07:42:50PM +0800, Yi Liu wrote:
> On 2023/10/12 17:12, Yi Liu wrote:
> > On 2023/9/26 14:56, Tian, Kevin wrote:
> > > > From: Yi Liu
> > > > Sent: Thursday, September 21, 2023 3:51 PM
> > > > +
> > > > +/**
> > > > + * iommu_copy_user_data - Copy iommu driver specific user
On 10/13/2023 2:03 PM, Shuah wrote:
> Applied this series and the following three - all 25 patches are
> in linux-kselftest next for Linux 6.7-rc1.
>
> [1]
> https://lore.kernel.org/all/cover.1696932728.git.maciej.wieczor-ret...@intel.com/
> [2]
> https://lore.kernel.org/all/20231002094813.66
On 10/13/23 05:36, Maciej Wieczor-Retman wrote:
kselftest.h declares many variadic functions that can print some
formatted message while also executing selftest logic. These
declarations don't have any compiler mechanism to verify if passed
arguments are valid in comparison with format specifiers
On Fri, Oct 13, 2023 at 12:19:23PM -0300, Jason Gunthorpe wrote:
> On Thu, Sep 21, 2023 at 12:51:31AM -0700, Yi Liu wrote:
> > IOMMU_HWPT_ALLOC already supports iommu_domain allocation for usersapce.
> > But it can only allocate a hw_pagetable that associates to a given IOAS,
> > i.e. only a kernel
On Wed, Oct 11, 2023 at 03:49:35PM -0400, Aaron Conole wrote:
> A number of corner cases were caught when trying to run the selftests on
> older systems. Missed skip conditions, some error cases, and outdated
> python setups would all report failures but the issue would actually be
> related to so
Add a new internal isolated_cpus mask to keep track of the CPUs that
are in isolated partitions. Expose that new cpumask as a new root-only
control file ".__DEBUG__.cpuset.cpus.isolated" when cgroup_debug command
line option is specified.
Signed-off-by: Waiman Long
---
kernel/cgroup/cpuset.c | 1
Minor cleanup of test matrix and relocation of test_isolated() function
to prepare for the next patch. There is no functional change.
Signed-off-by: Waiman Long
---
.../selftests/cgroup/test_cpuset_prs.sh | 142 +-
1 file changed, 71 insertions(+), 71 deletions(-)
diff --g
When the "isolcpus" boot command line option is used to add a set
of isolated CPUs, those CPUs will be excluded automatically from
wq_unbound_cpumask to avoid running work functions from unbound
workqueues.
Recently cpuset has been extended to allow the creation of partitions
of isolated CPUs dyna
To make CPUs in isolated cpuset partition closer in isolation to
the boot time isolated CPUs specified in the "isolcpus" boot command
line option, we need to take those CPUs out of the workqueue unbound
cpumask so that work functions from the unbound workqueues won't run
on those CPUs. Otherwise,
Isolated cpuset partition can currently be created to contain an
exclusive set of CPUs not used in other cgroups and with load balancing
disabled to reduce interference from the scheduler.
The main purpose of this isolated partition type is to dynamically
emulate what can be done via the "isolcpus
On Fri, Oct 13, 2023 at 11:04:56AM -0300, Jason Gunthorpe wrote:
> On Fri, Oct 13, 2023 at 12:33:13PM +0800, Yi Liu wrote:
>
> > not really. Below the users of the struct iommu_user_data in my current
> > iommufd_nesting branch. Only the domain_alloc_user op has type as there
> > can be multiple v
On Fri, Oct 13, 2023 at 09:49:10AM -0700, Lokesh Gidra wrote:
> On Fri, Oct 13, 2023 at 9:08 AM Peter Xu wrote:
> >
> > On Fri, Oct 13, 2023 at 11:56:31AM +0200, David Hildenbrand wrote:
> > > Hi Peter,
> >
> > Hi, David,
> >
> > >
> > > > I used to have the same thought with David on whether we c
On Fri, Oct 13, 2023 at 9:08 AM Peter Xu wrote:
>
> On Fri, Oct 13, 2023 at 11:56:31AM +0200, David Hildenbrand wrote:
> > Hi Peter,
>
> Hi, David,
>
> >
> > > I used to have the same thought with David on whether we can simplify the
> > > design to e.g. limit it to single mm. Then I found that t
On Fri, Oct 13, 2023 at 11:56:31AM +0200, David Hildenbrand wrote:
> Hi Peter,
Hi, David,
>
> > I used to have the same thought with David on whether we can simplify the
> > design to e.g. limit it to single mm. Then I found that the trickiest is
> > actually patch 1 together with the anon_vma
On Fri, Oct 13, 2023 at 11:31:14AM +0800, Meng Li wrote:
> +#define AMD_PSTATE_PREFCORE_THRESHOLD166
> +#define AMD_PSTATE_MAX_CPPC_PERF 255
> +static void amd_pstate_init_prefcore(struct amd_cpudata *cpudata)
> +{
> + int ret, prio;
> + u32 highest_perf;
> + static u32 ma
Hello.
On pátek 13. října 2023 5:31:11 CEST Meng Li wrote:
> Hi all:
>
> The core frequency is subjected to the process variation in semiconductors.
> Not all cores are able to reach the maximum frequency respecting the
> infrastructure limits. Consequently, AMD has redefined the concept of
> max
On Thu, Sep 21, 2023 at 12:51:31AM -0700, Yi Liu wrote:
> IOMMU_HWPT_ALLOC already supports iommu_domain allocation for usersapce.
> But it can only allocate a hw_pagetable that associates to a given IOAS,
> i.e. only a kernel-managed hw_pagetable of IOMMU_HWPT_TYPE_DEFAULT type.
>
> IOMMU drivers
On Fri, Oct 13, 2023 at 07:13:34AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Friday, October 13, 2023 3:10 AM
> >
> > Also, we probably should feed enforce_cache_coherency through the
> > alloc_hwpt uapi and not try to autodetect it..
> >
>
> In the past we had a long discus
On Fri, Oct 13, 2023 at 12:33:13PM +0800, Yi Liu wrote:
> not really. Below the users of the struct iommu_user_data in my current
> iommufd_nesting branch. Only the domain_alloc_user op has type as there
> can be multiple vendor specific alloc data types. Basically, I'm ok to
> make the change you
On Thu, Oct 12, 2023 at 05:34:58PM -0700, Nicolin Chen wrote:
> On Tue, Oct 10, 2023 at 01:58:44PM -0300, Jason Gunthorpe wrote:
> > On Thu, Sep 21, 2023 at 12:51:22AM -0700, Yi Liu wrote:
> > > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > > index 660dc1931dc9..12e12e5563e6 100644
On 2023/9/27 14:56, Tian, Kevin wrote:
From: Liu, Yi L
Sent: Thursday, September 21, 2023 3:55 PM
+ if (hwpt_type != IOMMU_HWPT_TYPE_DEFAULT &&
+ hwpt_type != IOMMU_HWPT_TYPE_VTD_S1)
+ return ERR_PTR(-EINVAL);
+
+ if ((hwpt_type == IOMMU_HWPT_TYPE_DEFAULT) =
On 2023/9/27 14:53, Tian, Kevin wrote:
From: Liu, Yi L
Sent: Thursday, September 21, 2023 3:54 PM
+
+ /* REVISIT:
+* VT-d has defined ITE, ICE, IQE for invalidation failure per hardware,
+* but no error code yet, so just set the error code to be 0.
+*/
+ *cerr
On 2023/10/13 20:40, Yi Liu wrote:
+ return -EINVAL;
+ }
+
+ if ((s1_cfg->flags & IOMMU_VTD_S1_SRE) && !ecap_srs(iommu-
ecap)) {
+ pr_err_ratelimited("No supervisor request support on %s\n",
+ iommu->name);
+ return -EINVAL;
+ }
+
+ if ((s1_c
On 2023/9/27 14:37, Tian, Kevin wrote:
From: Liu, Yi L
Sent: Thursday, September 21, 2023 3:54 PM
+
+/**
+ * intel_pasid_setup_nested() - Set up PASID entry for nested translation.
+ * @iommu: IOMMU which the device belong to
+ * @dev:Device to be set up for translation
+ * @pasid:
On 2023-10-12 at 08:30:37 -0600, Shuah Khan wrote:
>On 10/12/23 01:32, Maciej Wieczór-Retman wrote:
>> On 2023-10-11 at 13:40:48 -0600, Shuah wrote:
>> > On 10/11/23 02:23, Maciej Wieczor-Retman wrote:
>> > > Kselftest header defines multiple variadic functions that use printf
>> > > along with oth
On 2023/10/12 17:12, Yi Liu wrote:
On 2023/9/26 14:56, Tian, Kevin wrote:
From: Yi Liu
Sent: Thursday, September 21, 2023 3:51 PM
+
+/**
+ * iommu_copy_user_data - Copy iommu driver specific user space data
+ * @dst_data: Pointer to an iommu driver specific user data that is
defined
in
+ *
Compiling resctrl selftest after adding a __printf() attribute to
ksft_print_msg() exposes -Wformat warning in show_cache_info().
The format specifier used expects a variable of type int but a long
unsigned int variable is passed instead.
Change the format specifier to match the passed variable.
Compiling mm selftest after adding a __printf() attribute to
ksft_print_msg() exposes -Wformat warning in remap_region().
Fix the wrong format specifier causing the warning.
The mm selftest uses the printf attribute in its full form. Since the
header file that uses it also includes kselftests.h i
The __printf() macro is used in many tools in the linux kernel to
validate the format specifiers in functions that use printf. The kvm
selftest uses it without putting it in a macro definition while it
also imports the kselftests.h header where the macro attribute is
defined.
Use __printf() from k
Compiling sigaltstack selftest after adding a __printf() attribute to
ksft_print_msg() exposes -Wformat warning in main().
The format specifier inside ksft_print_msg() expects a long
unsigned int but the passed variable is of unsigned int type.
Fix the format specifier so it matches the passed var
Compiling pidfd selftest after adding a __printf() attribute to
ksft_print_msg() and ksft_test_result_pass() exposes -Wformat warnings
in error_report(), test_pidfd_poll_exec_thread(),
child_poll_exec_test(), test_pidfd_poll_leader_exit_thread(),
child_poll_leader_exit_test().
The ksft_test_result
Compiling openat2 selftest after adding a __printf() attribute to
ksft_print_msg() exposes a -Wformat warning in test_openat2_flags().
The wrong format specifier is used for printing test.how->flags
variable.
Change the format specifier to %llX so it matches the printed variable.
Signed-off-by: M
Compiling cachestat selftest after adding a __printf() attribute to
ksft_print_msg() exposes a -Wformat warning in print_cachestat().
The format specifier in printf() call expects long int variables and
received long long int.
Change format specifiers to long long int so they match passed
variable
Kselftest header defines multiple variadic functions that use printf
along with other logic.
There is no format checking for the variadic functions that use
printing inside kselftest.h. Because of this the compiler won't
be able to catch instances of mismatched printf formats and debugging
tests m
kselftest.h declares many variadic functions that can print some
formatted message while also executing selftest logic. These
declarations don't have any compiler mechanism to verify if passed
arguments are valid in comparison with format specifiers used in
printf() calls.
Attribute addition can m
On Thu, Oct 05, 2023 at 10:18 PM -07, Martin KaFai Lau wrote:
> On 10/5/23 12:21 AM, Geliang Tang wrote:
>> --- a/tools/testing/selftests/bpf/prog_tests/sockmap_listen.c
>> +++ b/tools/testing/selftests/bpf/prog_tests/sockmap_listen.c
>> @@ -1336,32 +1336,22 @@ static void test_redir(struct test_so
On 12.10.23 22:11, Peter Xu wrote:
On Mon, Oct 09, 2023 at 05:29:08PM +0100, Lokesh Gidra wrote:
On Mon, Oct 9, 2023 at 5:24 PM David Hildenbrand wrote:
On 09.10.23 18:21, Suren Baghdasaryan wrote:
On Mon, Oct 9, 2023 at 7:38 AM David Hildenbrand wrote:
On 09.10.23 08:42, Suren Baghdasary
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller :
On Tue, 10 Oct 2023 16:44:00 +0200 you wrote:
> From: Jiri Pirko
>
> The file name used in flash test was "dummy" because at the time test
> was written, drivers were responsible for file request and as netdevsim
>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller :
On Mon, 9 Oct 2023 13:06:07 +0300 you wrote:
> The merge commit 92716869375b ("Merge branch 'br-flush-filtering'") added
> support for FDB flushing in bridge driver. Extend VXLAN driver to support
> FDB flushing als
On Fri, Oct 13, 2023 at 9:35 AM zhujun2 wrote:
>
> These variables are never referenced in the code, just remove them.
You can't remove them because they are really referenced in the CHECK() marco.
Sending a patch without even testing a build is bad :(
>
> Signed-off-by: zhujun2
> ---
> tools/
On 13.10.23 00:01, Peter Xu wrote:
On Sun, Oct 08, 2023 at 11:42:26PM -0700, Suren Baghdasaryan wrote:
From: Andrea Arcangeli
For now, folio_move_anon_rmap() was only used to move a folio to a
different anon_vma after fork(), whereby the root anon_vma stayed
unchanged. For that, it was suffici
> From: Jason Gunthorpe
> Sent: Friday, October 13, 2023 3:10 AM
>
> Also, we probably should feed enforce_cache_coherency through the
> alloc_hwpt uapi and not try to autodetect it..
>
In the past we had a long discussion about this with the conclusion
that user opt is the ideal model but it's
53 matches
Mail list logo
