Re: [PATCH V8 0/7] amd-pstate preferred core

2023-10-08 Thread Oleksandr Natalenko
Hello. On pondělí 9. října 2023 4:49:25 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 > ma

[PATCH v3 3/3] selftests/mm: add UFFDIO_MOVE ioctl test

2023-10-08 Thread Suren Baghdasaryan
Add a test for new UFFDIO_MOVE ioctl which uses uffd to move source into destination buffer while checking the contents of both after remapping. After the operation the content of the destination buffer should match the original source buffer's content while the source buffer should be zeroed. Sig

[PATCH v3 2/3] userfaultfd: UFFDIO_MOVE uABI

2023-10-08 Thread Suren Baghdasaryan
From: Andrea Arcangeli Implement the uABI of UFFDIO_MOVE ioctl. UFFDIO_COPY performs ~20% better than UFFDIO_MOVE when the application needs pages to be allocated [1]. However, with UFFDIO_MOVE, if pages are available (in userspace) for recycling, as is usually the case in heap compaction algorit

[PATCH v3 0/3] userfaultfd move option

2023-10-08 Thread Suren Baghdasaryan
This patch series introduces UFFDIO_MOVE feature to userfaultfd, which has long been implemented and maintained by Andrea in his local tree [1], but was not upstreamed due to lack of use cases where this approach would be better than allocating a new page and copying the contents. Previous upstrami

[PATCH v3 1/3] mm/rmap: support move to different root anon_vma in folio_move_anon_rmap()

2023-10-08 Thread Suren Baghdasaryan
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 sufficient to hold the folio lock when calling folio_move_anon_rmap(). However, we want to make use of folio_mov

Re: [PATCH V8 6/7] Documentation: amd-pstate: introduce amd-pstate preferred core

2023-10-08 Thread Wyes Karny
On 09 Oct 10:49, Meng Li wrote: > Introduce amd-pstate preferred core. > > check preferred core state set by the kernel parameter: > $ cat /sys/devices/system/cpu/amd-pstate/prefcore > > Reviewed-by: Mario Limonciello > Reviewed-by: Huang Rui Reviewed-by: Wyes Karny > Signed-off-by: Meng Li >

Re: [PATCH V8 3/7] cpufreq: amd-pstate: Enable amd-pstate preferred core supporting.

2023-10-08 Thread Wyes Karny
On 09 Oct 10:49, Meng Li wrote: > amd-pstate driver utilizes the functions and data structures > provided by the ITMT architecture to enable the scheduler to > favor scheduling on cores which can be get a higher frequency > with lower voltage. We call it amd-pstate preferrred core. > > Here sched_

Re: [PATCH V8 4/7] cpufreq: Add a notification message that the highest perf has changed

2023-10-08 Thread Wyes Karny
On 09 Oct 10:49, Meng Li wrote: > ACPI 6.5 section 8.4.6.1.1.1 specifies that Notify event 0x85 can be > emmitted to cause the the OSPM to re-evaluate the highest performance > register. Add support for this event. > > Reviewed-by: Mario Limonciello > Reviewed-by: Huang Rui Reviewed-by: Wyes Kar

Re: [PATCH V8 5/7] cpufreq: amd-pstate: Update amd-pstate preferred core ranking dynamically

2023-10-08 Thread Wyes Karny
Hi Meng Li, On 09 Oct 10:49, Meng Li wrote: > Preferred core rankings can be changed dynamically by the > platform based on the workload and platform conditions and > accounting for thermals and aging. > When this occurs, cpu priority need to be set. > > Reviewed-by: Mario Limonciello > Reviewed

Re: [PATCH V8 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion.

2023-10-08 Thread Wyes Karny
On 09 Oct 10:49, Meng Li wrote: > amd-pstate driver also uses SCHED_MC_PRIO, so decouple the requirement > of CPU_SUP_INTEL from the dependencies to allow compilation in kernels > without Intel CPU support. > > Reviewed-by: Mario Limonciello > Reviewed-by: Huang Rui Reviewed-by: Wyes Karny > Si

Re: [PATCH v4 03/17] iommufd: Unite all kernel-managed members into a struct

2023-10-08 Thread Yan Zhao
On Mon, Oct 09, 2023 at 12:13:52PM +0800, Yi Liu wrote: > On 2023/10/7 18:08, Yan Zhao wrote: > > On Thu, Sep 21, 2023 at 12:51:24AM -0700, Yi Liu wrote: > > > From: Nicolin Chen > > > > > > The struct iommufd_hw_pagetable has been representing a kernel-managed > > > HWPT, yet soon will be reused

Re: [PATCH v4 03/17] iommufd: Unite all kernel-managed members into a struct

2023-10-08 Thread Yi Liu
On 2023/10/7 18:08, Yan Zhao wrote: On Thu, Sep 21, 2023 at 12:51:24AM -0700, Yi Liu wrote: From: Nicolin Chen The struct iommufd_hw_pagetable has been representing a kernel-managed HWPT, yet soon will be reused to represent a user-managed HWPT. These two types of HWPTs has the same IOMMUFD ob

[PATCH V8 7/7] Documentation: introduce amd-pstate preferrd core mode kernel command line options

2023-10-08 Thread Meng Li
amd-pstate driver support enable/disable preferred core. Default enabled on platforms supporting amd-pstate preferred core. Disable amd-pstate preferred core with "amd_prefcore=disable" added to the kernel command line. Signed-off-by: Meng Li Reviewed-by: Mario Limonciello Reviewed-by: Wyes Karn

[PATCH V8 6/7] Documentation: amd-pstate: introduce amd-pstate preferred core

2023-10-08 Thread Meng Li
Introduce amd-pstate preferred core. check preferred core state set by the kernel parameter: $ cat /sys/devices/system/cpu/amd-pstate/prefcore Reviewed-by: Mario Limonciello Reviewed-by: Huang Rui Signed-off-by: Meng Li --- Documentation/admin-guide/pm/amd-pstate.rst | 59

[PATCH V8 4/7] cpufreq: Add a notification message that the highest perf has changed

2023-10-08 Thread Meng Li
ACPI 6.5 section 8.4.6.1.1.1 specifies that Notify event 0x85 can be emmitted to cause the the OSPM to re-evaluate the highest performance register. Add support for this event. Reviewed-by: Mario Limonciello Reviewed-by: Huang Rui Signed-off-by: Meng Li Link: https://uefi.org/specs/ACPI/6.5/05

[PATCH V8 5/7] cpufreq: amd-pstate: Update amd-pstate preferred core ranking dynamically

2023-10-08 Thread Meng Li
Preferred core rankings can be changed dynamically by the platform based on the workload and platform conditions and accounting for thermals and aging. When this occurs, cpu priority need to be set. Reviewed-by: Mario Limonciello Reviewed-by: Wyes Karny Reviewed-by: Huang Rui Signed-off-by: Men

[PATCH V8 3/7] cpufreq: amd-pstate: Enable amd-pstate preferred core supporting.

2023-10-08 Thread Meng Li
amd-pstate driver utilizes the functions and data structures provided by the ITMT architecture to enable the scheduler to favor scheduling on cores which can be get a higher frequency with lower voltage. We call it amd-pstate preferrred core. Here sched_set_itmt_core_prio() is called to set priori

[PATCH V8 2/7] acpi: cppc: Add get the highest performance cppc control

2023-10-08 Thread Meng Li
Add support for getting the highest performance to the generic CPPC driver. This enables downstream drivers such as amd-pstate to discover and use these values. Please refer to the ACPI_Spec for details on continuous performance control of CPPC. Reviewed-by: Mario Limonciello Reviewed-by: Wyes K

[PATCH V8 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion.

2023-10-08 Thread Meng Li
amd-pstate driver also uses SCHED_MC_PRIO, so decouple the requirement of CPU_SUP_INTEL from the dependencies to allow compilation in kernels without Intel CPU support. Reviewed-by: Mario Limonciello Reviewed-by: Huang Rui Signed-off-by: Meng Li --- arch/x86/Kconfig | 5 +++-- 1 file changed,

[PATCH V8 0/7] amd-pstate preferred core

2023-10-08 Thread Meng Li
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 maximum frequency of a part. This means that a fraction of cores can reach

RE: [PATCH v2 6/6] iommu/vt-d: Add domain_alloc_user op

2023-10-08 Thread Tian, Kevin
> From: Liu, Yi L > Sent: Thursday, September 28, 2023 3:15 PM > > This adds the domain_alloc_user op implementation. It supports allocating > domains to be used as parent under nested translation. > > Signed-off-by: Yi Liu Reviewed-by: Kevin Tian

RE: [PATCH v2 5/6] iommufd/selftest: Add domain_alloc_user() support in iommu mock

2023-10-08 Thread Tian, Kevin
> From: Liu, Yi L > Sent: Thursday, September 28, 2023 3:15 PM > > This adds mock_domain_alloc_user function and also new test case for the > new flag IOMMU_HWPT_ALLOC_NEST_PARENT. > > Co-developed-by: Nicolin Chen > Signed-off-by: Nicolin Chen > Signed-off-by: Yi Liu Reviewed-by: Kevin Tian

RE: [PATCH v2 4/6] iommufd/hw_pagetable: Support allocating nested parent domain

2023-10-08 Thread Tian, Kevin
> From: Liu, Yi L > Sent: Thursday, September 28, 2023 3:15 PM > > This extends IOMMU_HWPT_ALLOC to allocate domains used as parent > (stage-2) > in nested translation. > > Signed-off-by: Yi Liu Reviewed-by: Kevin Tian

RE: [PATCH v2 1/6] iommu: Add new iommu op to create domains owned by userspace

2023-10-08 Thread Tian, Kevin
> From: Liu, Yi L > Sent: Thursday, September 28, 2023 3:15 PM > > Introduce a new iommu_domain op to create domains owned by userspace, > e.g. through IOMMUFD. These domains have a few different properties > compares to kernel owned domains: > > - They may be UNMANAGED domains, but created wit

Re: [RFC PATCH 5/7] tun: Introduce virtio-net hashing feature

2023-10-08 Thread Akihiko Odaki
On 2023/10/09 5:08, Willem de Bruijn wrote: On Sun, Oct 8, 2023 at 10:04 PM Akihiko Odaki wrote: On 2023/10/09 4:07, Willem de Bruijn wrote: On Sun, Oct 8, 2023 at 7:22 AM Akihiko Odaki wrote: virtio-net have two usage of hashes: one is RSS and another is hash reporting. Conventionally the

Re: [RFC PATCH 5/7] tun: Introduce virtio-net hashing feature

2023-10-08 Thread Willem de Bruijn
On Sun, Oct 8, 2023 at 10:04 PM Akihiko Odaki wrote: > > On 2023/10/09 4:07, Willem de Bruijn wrote: > > On Sun, Oct 8, 2023 at 7:22 AM Akihiko Odaki > > wrote: > >> > >> virtio-net have two usage of hashes: one is RSS and another is hash > >> reporting. Conventionally the hash calculation was d

Re: [RFC PATCH 5/7] tun: Introduce virtio-net hashing feature

2023-10-08 Thread Akihiko Odaki
On 2023/10/09 4:07, Willem de Bruijn wrote: On Sun, Oct 8, 2023 at 7:22 AM Akihiko Odaki wrote: virtio-net have two usage of hashes: one is RSS and another is hash reporting. Conventionally the hash calculation was done by the VMM. However, computing the hash after the queue was chosen defeats

Re: [RFC PATCH 1/7] net: skbuff: Add tun_vnet_hash flag

2023-10-08 Thread Akihiko Odaki
On 2023/10/09 3:39, Willem de Bruijn wrote: On Sun, Oct 8, 2023 at 7:22 AM Akihiko Odaki wrote: tun_vnet_hash can use this flag to indicate it stored virtio-net hash cache to cb. Signed-off-by: Akihiko Odaki --- include/linux/skbuff.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/

Re: [RFC PATCH 5/7] tun: Introduce virtio-net hashing feature

2023-10-08 Thread Willem de Bruijn
On Sun, Oct 8, 2023 at 7:22 AM Akihiko Odaki wrote: > > virtio-net have two usage of hashes: one is RSS and another is hash > reporting. Conventionally the hash calculation was done by the VMM. > However, computing the hash after the queue was chosen defeats the > purpose of RSS. > > Another appro

Re: [RFC PATCH 1/7] net: skbuff: Add tun_vnet_hash flag

2023-10-08 Thread Willem de Bruijn
On Sun, Oct 8, 2023 at 7:22 AM Akihiko Odaki wrote: > > tun_vnet_hash can use this flag to indicate it stored virtio-net hash > cache to cb. > > Signed-off-by: Akihiko Odaki > --- > include/linux/skbuff.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/linux/skbuff.h b/include

Re: [RFC PATCH 0/7] tun: Introduce virtio-net hashing feature

2023-10-08 Thread Willem de Bruijn
On Sun, Oct 8, 2023 at 7:21 AM Akihiko Odaki wrote: > > virtio-net have two usage of hashes: one is RSS and another is hash > reporting. Conventionally the hash calculation was done by the VMM. > However, computing the hash after the queue was chosen defeats the > purpose of RSS. > > Another appro

Re: selftests: cgroup: test_core - Unable to handle kernel NULL pointer dereference at virtual address

2023-10-08 Thread Roman Gushchin
On Sun, Oct 08, 2023 at 11:30:52AM +0530, Naresh Kamboju wrote: > While running selftests: cgroup: test_kmem on FVP following kernel crash > noticed on Linux next 6.6.0-rc4-next-20231006. Hi Naresh! Thank you for the report! I've tried to reproduce it, but wasn't successful so far: I've run test

[PATCH] selftests/nolibc: use qemu-system-ppc64 for ppc64le

2023-10-08 Thread Thomas Weißschuh
QEMU_ARCH_loongarch = loongarch64 --- base-commit: 361fbc295e965a3c7f606d281e6107e098d33730 change-id: 20231008-nolibc-qemu-ppc64-07b4f74043a6 Best regards, -- Thomas Weißschuh