Re: [RFC PATCH v4 12/16] powerpc/e500: Encode hugepage size in PTE bits

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:10PM +0200, Christophe Leroy wrote: > Use U0-U3 bits to encode hugepage size, more exactly page shift. > > As we start using hugepages at shift 21 (2Mbytes), substract 20 > so that it fits into 4 bits. That may change in the future if > we want to use smaller hugepage

Re: [RFC PATCH v4 08/16] powerpc/8xx: Rework support for 8M pages using contiguous PTE entries

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:06PM +0200, Christophe Leroy wrote: > In order to fit better with standard Linux page tables layout, add > support for 8M pages using contiguous PTE entries in a standard > page table. Page tables will then be populated with 1024 similar > entries and two PMD entries w

Re: [PATCH v2 2/2] powerpc/configs: Update defconfig with now user-visible CONFIG_FSL_IFC

2024-05-29 Thread Michael Ellerman
Esben Haabendal writes: > Krzysztof Kozlowski writes: > >> On 28/05/2024 14:28, Esben Haabendal wrote: >>> With CONFIG_FSL_IFC now being user-visible, and thus changed from a select >>> to depends in CONFIG_MTD_NAND_FSL_IFC, the dependencies needs to be >>> selected in config snippets. >>> >>> S

Re: [PATCH] selftests/openat2: Fix build warnings on ppc64

2024-05-29 Thread Michael Ellerman
Muhammad Usama Anjum writes: > I was looking at if we can add this flag for ppc64 for all selftests > somewhere. But there isn't any suitable place other than in KHDR_INCLUDES. > But there is a series already trying to add _GNU_SOURCE to it. IMHO adding other flags to KHDR_INCLUDES is not the rig

Re: [RFC PATCH v4 13/16] powerpc/e500: Use contiguous PMD instead of hugepd

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:11PM +0200, Christophe Leroy wrote: > e500 supports many page sizes among which the following size are > implemented in the kernel at the time being: 4M, 16M, 64M, 256M, 1G. > > On e500, TLB miss for hugepages is exclusively handled by SW even > on e6500 which has HW

Re: [PATCH v3] mm/mm_init: use node's number of cpus in deferred_page_init_max_threads

2024-05-29 Thread Baoquan He
On 05/28/24 at 02:54pm, Eric Chanudet wrote: > When DEFERRED_STRUCT_PAGE_INIT=y, use a node's cpu count as maximum > thread count for the deferred initialization of struct pages via padata. > This should result in shorter boot times for these configurations by > going through page_alloc_init_late()

[PATCH v4 0/2] ASoC: fsl_xcvr: Support i.MX95 platform

2024-05-29 Thread Shengjiu Wang
On i.MX95 wakeup domain, there is one instance of Audio XCVR supporting SPDIF mode with a connection to the Audio XCVR physical interface. changes in v4: - refine the constarint for 'clocks' according to Rob's comments changes in v3: - refine the constraint for 'resets', 'clocks', 'interrupts' in

[PATCH v4 2/2] ASoC: fsl_xcvr: Add support for i.MX95 platform

2024-05-29 Thread Shengjiu Wang
On i.MX95, the XCVR uses a new PLL in the PHY, which is General Purpose (GP) PLL. Add GP PLL configuration support in the driver and add the 'pll_ver' flag to distinguish different PLL on different platforms. The XCVR also use PHY but limited for SPDIF only case Add 'use_phy' flag to distinguish t

[PATCH v4 1/2] ASoC: dt-bindings: fsl,xcvr: Add compatible string for i.MX95

2024-05-29 Thread Shengjiu Wang
Add compatible string "fsl,imx95-xcvr" for i.MX95 platform. The difference between each platform is in below table. +-++--++ | SOC| PHY | eARC/ARC | SPDIF | +-++--++ | i.MX8MP | V1| Yes | Yes | +-+--

Re: [RFC PATCH v4 14/16] powerpc/64s: Use contiguous PMD/PUD instead of HUGEPD

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:12PM +0200, Christophe Leroy wrote: > On book3s/64, the only user of hugepd is hash in 4k mode. > > All other setups (hash-64, radix-4, radix-64) use leaf PMD/PUD. > > Rework hash-4k to use contiguous PMD and PUD instead. > > In that setup there are only two huge pa

Re: [RFC PATCH v4 08/16] powerpc/8xx: Rework support for 8M pages using contiguous PTE entries

2024-05-29 Thread Christophe Leroy
Le 29/05/2024 à 10:02, Oscar Salvador a écrit : > [Vous ne recevez pas souvent de courriers de osalva...@suse.com. D?couvrez > pourquoi ceci est important ? https://aka.ms/LearnAboutSenderIdentification ] > > On Mon, May 27, 2024 at 03:30:06PM +0200, Christophe Leroy wrote: >> In order to fit b

Re: [RFC PATCH v4 12/16] powerpc/e500: Encode hugepage size in PTE bits

2024-05-29 Thread Christophe Leroy
Le 29/05/2024 à 10:05, Oscar Salvador a écrit : > [Vous ne recevez pas souvent de courriers de osalva...@suse.com. D?couvrez > pourquoi ceci est important ? https://aka.ms/LearnAboutSenderIdentification ] > > On Mon, May 27, 2024 at 03:30:10PM +0200, Christophe Leroy wrote: >> Use U0-U3 bits to

Re: [RFC PATCH v4 13/16] powerpc/e500: Use contiguous PMD instead of hugepd

2024-05-29 Thread Christophe Leroy
Le 29/05/2024 à 10:49, Oscar Salvador a écrit : > [Vous ne recevez pas souvent de courriers de osalva...@suse.com. D?couvrez > pourquoi ceci est important ? https://aka.ms/LearnAboutSenderIdentification ] > > On Mon, May 27, 2024 at 03:30:11PM +0200, Christophe Leroy wrote: >> e500 supports man

Re: [RFC PATCH v4 13/16] powerpc/e500: Use contiguous PMD instead of hugepd

2024-05-29 Thread Oscar Salvador
On Wed, May 29, 2024 at 09:58:35AM +, Christophe Leroy wrote: > Yes I now have : > > +#define _PAGE_HSIZE_MSK (_PAGE_U0 | _PAGE_U1 | _PAGE_U2 | _PAGE_U3) > +#define _PAGE_HSIZE_SHIFT 14 > +#define _PAGE_HSIZE_SHIFT_OFFSET 20 > > and have added a helper to avoid doing the

Re: [RFC PATCH v4 14/16] powerpc/64s: Use contiguous PMD/PUD instead of HUGEPD

2024-05-29 Thread Christophe Leroy
Le 29/05/2024 à 11:23, Oscar Salvador a écrit : > On Mon, May 27, 2024 at 03:30:12PM +0200, Christophe Leroy wrote: >> On book3s/64, the only user of hugepd is hash in 4k mode. >> >> All other setups (hash-64, radix-4, radix-64) use leaf PMD/PUD. >> >> Rework hash-4k to use contiguous PMD and PUD

Re: [RFC PATCH v4 12/16] powerpc/e500: Encode hugepage size in PTE bits

2024-05-29 Thread Oscar Salvador
On Wed, May 29, 2024 at 09:49:48AM +, Christophe Leroy wrote: > Doesn't really matter if it's PUD or PMD at this point. On a 32 bits > kernel it will be all PMD while on a 64 bits kernel it is both PMD and PUD. > > At the time being (as implemented with hugepd), Linux support 4M, 16M, > 64M,

Re: [RFC PATCH v4 12/16] powerpc/e500: Encode hugepage size in PTE bits

2024-05-29 Thread Oscar Salvador
On Wed, May 29, 2024 at 10:14:15AM +, Christophe Leroy wrote: > > > Le 29/05/2024 à 12:09, Oscar Salvador a écrit : > > On Wed, May 29, 2024 at 09:49:48AM +, Christophe Leroy wrote: > >> Doesn't really matter if it's PUD or PMD at this point. On a 32 bits > >> kernel it will be all PMD wh

Re: [RFC PATCH v4 16/16] mm: Remove CONFIG_ARCH_HAS_HUGEPD

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:14PM +0200, Christophe Leroy wrote: > powerpc was the only user of CONFIG_ARCH_HAS_HUGEPD and doesn't > use it anymore, so remove all related code. > > Signed-off-by: Christophe Leroy Acked-by: Oscar Salvador -- Oscar Salvador SUSE Labs

Re: [RFC PATCH v4 14/16] powerpc/64s: Use contiguous PMD/PUD instead of HUGEPD

2024-05-29 Thread Oscar Salvador
On Wed, May 29, 2024 at 10:07:55AM +, Christophe Leroy wrote: > We can't but I didn't want to leave nb undefined or with a value that > might lead to writing in the weed. Value 1 seems a safe default. Might be worth to throw a WARN_ON? > >> diff --git a/arch/powerpc/mm/book3s64/hugetlbpage.c

Re: [RFC PATCH v4 15/16] powerpc/mm: Remove hugepd leftovers

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:13PM +0200, Christophe Leroy wrote: > All targets have now opted out of CONFIG_ARCH_HAS_HUGEPD so > remove left over code. > > Signed-off-by: Christophe Leroy Acked-by: Oscar Salvador -- Oscar Salvador SUSE Labs

Re: [RFC PATCH v4 12/16] powerpc/e500: Encode hugepage size in PTE bits

2024-05-29 Thread Christophe Leroy
Le 29/05/2024 à 12:09, Oscar Salvador a écrit : > On Wed, May 29, 2024 at 09:49:48AM +, Christophe Leroy wrote: >> Doesn't really matter if it's PUD or PMD at this point. On a 32 bits >> kernel it will be all PMD while on a 64 bits kernel it is both PMD and PUD. >> >> At the time being (as im

Re: [RFC PATCH v4 00/16] Reimplement huge pages without hugepd on powerpc (8xx, e500, book3s/64)

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:29:58PM +0200, Christophe Leroy wrote: > This is the continuation of the RFC v1 series "Reimplement huge pages > without hugepd on powerpc 8xx". It now get rid of hugepd completely > after handling also e500 and book3s/64 > > Also see https://github.com/linuxppc/issues/i

Re: [PATCH v2 3/6] KVM: x86: Fold kvm_arch_sched_in() into kvm_arch_vcpu_load()

2024-05-29 Thread Huang, Kai
On Tue, 2024-05-28 at 12:16 -0700, Sean Christopherson wrote: > On Fri, May 24, 2024, Kai Huang wrote: > > > @@ -1548,6 +1548,9 @@ static void svm_vcpu_load(struct kvm_vcpu *vcpu, > > > int cpu) > > > struct vcpu_svm *svm = to_svm(vcpu); > > > struct svm_cpu_data *sd = per_cpu_

[PATCH v2 1/2] powerpc/uaccess: Fix build errors seen with GCC 13/14

2024-05-29 Thread Michael Ellerman
Building ppc64le_defconfig with GCC 14 fails with assembler errors: CC fs/readdir.o /tmp/ccdQn0mD.s: Assembler messages: /tmp/ccdQn0mD.s:212: Error: operand out of domain (18 is not a multiple of 4) /tmp/ccdQn0mD.s:226: Error: operand out of domain (18 is not a multiple of 4) ...

[PATCH v2 2/2] powerpc/uaccess: Use YZ asm constraint for ld

2024-05-29 Thread Michael Ellerman
The 'ld' instruction requires a 4-byte aligned displacement because it is a DS-form instruction. But the "m" asm constraint doesn't enforce that. Add a special case of __get_user_asm2_goto() so that the "YZ" constraint can be used for "ld". The "Z" constraint is documented in the GCC manual Power

Re: [PATCH v2 3/6] KVM: x86: Fold kvm_arch_sched_in() into kvm_arch_vcpu_load()

2024-05-29 Thread Sean Christopherson
On Wed, May 29, 2024, Kai Huang wrote: > I am not familiar with SVM, but it seems the relevant parts are: > > control->pause_filter_count; > vmcb_mark_dirty(svm->vmcb, VMCB_INTERCEPTS); > > And it seems they are directly related to programming the hardware, i.e., > they got automatica

Re: [PATCH 04/23] scsi: initialize scsi midlayer limits before allocating the queue

2024-05-29 Thread Linux regression tracking (Thorsten Leemhuis)
[CCing the regression list, as it should be in the loop for regressions: https://docs.kernel.org/admin-guide/reporting-regressions.html] On 20.05.24 17:15, Christoph Hellwig wrote: > Adding ben and the linuxppc list. Hmm, no reply and no other progress to get this resolved afaics. So lets bring M

Re: [PATCH v4 07/29] KVM: arm64: Save/restore POE registers

2024-05-29 Thread Marc Zyngier
On Fri, 03 May 2024 14:01:25 +0100, Joey Gouly wrote: > > Define the new system registers that POE introduces and context switch them. > > Signed-off-by: Joey Gouly > Cc: Marc Zyngier > Cc: Oliver Upton > Cc: Catalin Marinas > Cc: Will Deacon > --- > arch/arm64/include/asm/kvm_host.h

Re: [PATCH v4 08/29] KVM: arm64: make kvm_at() take an OP_AT_*

2024-05-29 Thread Marc Zyngier
On Fri, 03 May 2024 14:01:26 +0100, Joey Gouly wrote: > > To allow using newer instructions that current assemblers don't know about, > replace the `at` instruction with the underlying SYS instruction. > > Signed-off-by: Joey Gouly > Cc: Marc Zyngier > Cc: Oliver Upton > Cc: Catalin Marinas

Re: [PATCH v4 09/29] KVM: arm64: use `at s1e1a` for POE

2024-05-29 Thread Marc Zyngier
On Fri, 03 May 2024 14:01:27 +0100, Joey Gouly wrote: > > FEAT_ATS1E1A introduces a new instruction: `at s1e1a`. > This is an address translation, without permission checks. > > POE allows read permissions to be removed from S1 by the guest. This means > that an `at` instruction could fail, and

Re: [PATCH v4 28/29] kselftest/arm64: Add test case for POR_EL0 signal frame records

2024-05-29 Thread Mark Brown
On Fri, May 03, 2024 at 02:01:46PM +0100, Joey Gouly wrote: > Ensure that we get signal context for POR_EL0 if and only if POE is present > on the system. Reviewed-by: Mark Brown signature.asc Description: PGP signature

[PATCH] powerpc: Limit ARCH_HAS_KERNEL_FPU_SUPPORT to PPC64

2024-05-29 Thread Samuel Holland
When building a 32-bit kernel, some toolchains do not allow mixing soft float and hard float object files: LD vmlinux.o powerpc64le-unknown-linux-musl-ld: lib/test_fpu_impl.o uses hard float, arch/powerpc/kernel/udbg.o uses soft float powerpc64le-unknown-linux-musl-ld: failed to merg

[PATCH v4 0/7] mm: multi-gen LRU: Walk secondary MMU page tables while aging

2024-05-29 Thread James Houghton
This patchset makes it possible for MGLRU to consult secondary MMUs while doing aging, not just during eviction. This allows for more accurate reclaim decisions, which is especially important for proactive reclaim. This series makes the necessary MMU notifier changes to MGLRU and then includes opt

[PATCH v4 1/7] mm/Kconfig: Add LRU_GEN_WALKS_SECONDARY_MMU

2024-05-29 Thread James Houghton
Add this option so that one building the kernel can choose whether or not they want to support walking the secondary MMU. We want users to be able to blindly enable all lru_gen features to have the best possible performance most of the time. Walking the secondary MMU is mainly useful for be able t

[PATCH v4 6/7] KVM: arm64: Relax locking for kvm_test_age_gfn and kvm_age_gfn

2024-05-29 Thread James Houghton
Replace the MMU write locks for read locks. Grabbing the read lock instead of the write lock is safe because the only requirement we have is that the stage-2 page tables do not get deallocated while we are walking them. The stage2_age_walker() callback is safe to race with itself; update the comme

[PATCH v4 4/7] KVM: Move MMU lock acquisition for test/clear_young to architecture

2024-05-29 Thread James Houghton
For implementation mmu_notifier_{test,clear}_young, the KVM memslot walker used to take the MMU lock for us. Now make the architectures take it themselves. Don't relax locking for any architecture except powerpc e500; its implementations of kvm_age_gfn and kvm_test_age_gfn simply return false, so

[PATCH v4 3/7] KVM: Add lockless memslot walk to KVM

2024-05-29 Thread James Houghton
Provide flexibility to the architecture to synchronize as optimally as they can instead of always taking the MMU lock for writing. The immediate application is to allow architectures to implement the test/clear_young MMU notifiers more cheaply. Suggested-by: Yu Zhao Signed-off-by: James Houghton

[PATCH v4 5/7] KVM: x86: Relax locking for kvm_test_age_gfn and kvm_age_gfn

2024-05-29 Thread James Houghton
Walk the TDP MMU in an RCU read-side critical section. This requires a way to do RCU-safe walking of the tdp_mmu_roots; do this with a new macro. The PTE modifications are now done atomically, and kvm_tdp_mmu_spte_need_atomic_write() has been updated to account for the fact that kvm_age_gfn can now

[PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging

2024-05-29 Thread James Houghton
Secondary MMUs are currently consulted for access/age information at eviction time, but before then, we don't get accurate age information. That is, pages that are mostly accessed through a secondary MMU (like guest memory, used by KVM) will always just proceed down to the oldest generation, and th

[PATCH v4 7/7] KVM: selftests: Add multi-gen LRU aging to access_tracking_perf_test

2024-05-29 Thread James Houghton
This test now has two modes of operation: 1. (default) To check how much vCPU performance was affected by access tracking (previously existed, now supports MGLRU aging). 2. (-p) To also benchmark how fast MGLRU can do aging while vCPUs are faulting in memory. Mode (1) also ser

Re: Xorg doesn't start and some other issues with the RC1 of kernel 6.10

2024-05-29 Thread Christian Zigotzky
On 28.05.24 22:00, Christian Zigotzky wrote: Hi All, Xorg doesn't start anymore since the RC1 of kernel 6.10. We tested it with the VirtIO GPU and with some Radeon cards. Another error message: Failed to start Setup Virtual Console. Maybe this is the issue: + CONFIG_ARCH_HAS_KERNEL_FPU_SUPPO

Re: [RFC PATCH v4 16/16] mm: Remove CONFIG_ARCH_HAS_HUGEPD

2024-05-29 Thread Oscar Salvador
On Mon, May 27, 2024 at 03:30:14PM +0200, Christophe Leroy wrote: > powerpc was the only user of CONFIG_ARCH_HAS_HUGEPD and doesn't > use it anymore, so remove all related code. > > Signed-off-by: Christophe Leroy > --- > v4: Rebased on v6.10-rc1 > --- > arch/powerpc/mm/hugetlbpage.c | 1 - >

Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging

2024-05-29 Thread Yu Zhao
On Wed, May 29, 2024 at 12:05 PM James Houghton wrote: > > Secondary MMUs are currently consulted for access/age information at > eviction time, but before then, we don't get accurate age information. > That is, pages that are mostly accessed through a secondary MMU (like > guest memory, used by K

Re: [PATCH v4 3/7] KVM: Add lockless memslot walk to KVM

2024-05-29 Thread Sean Christopherson
On Wed, May 29, 2024, James Houghton wrote: > @@ -686,10 +694,12 @@ static __always_inline int kvm_handle_hva_range(struct > mmu_notifier *mn, > return __kvm_handle_hva_range(kvm, &range).ret; > } > > -static __always_inline int kvm_handle_hva_range_no_flush(struct mmu_notifier > *mn, >

Re: [PATCH v4 4/7] KVM: Move MMU lock acquisition for test/clear_young to architecture

2024-05-29 Thread Sean Christopherson
On Wed, May 29, 2024, James Houghton wrote: > For implementation mmu_notifier_{test,clear}_young, the KVM memslot > walker used to take the MMU lock for us. Now make the architectures > take it themselves. Hmm, *forcing* architectures to take mmu_lock is a step backwards. Rather than add all of t

Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging

2024-05-29 Thread Sean Christopherson
On Wed, May 29, 2024, Yu Zhao wrote: > On Wed, May 29, 2024 at 12:05 PM James Houghton wrote: > > > > Secondary MMUs are currently consulted for access/age information at > > eviction time, but before then, we don't get accurate age information. > > That is, pages that are mostly accessed through

Re: [PATCH] selftests/overlayfs: Fix build error on ppc64

2024-05-29 Thread Shuah Khan
On 5/20/24 20:26, Michael Ellerman wrote: Fix build error on ppc64: dev_in_maps.c: In function ‘get_file_dev_and_inode’: dev_in_maps.c:60:59: error: format ‘%llu’ expects argument of type ‘long long unsigned int *’, but argument 7 has type ‘__u64 *’ {aka ‘long unsigned int *’} [-Werro

Re: [PATCH] selftests: cachestat: Fix build warnings on ppc64

2024-05-29 Thread Shuah Khan
On 5/20/24 21:01, Michael Ellerman wrote: Fix warnings like: test_cachestat.c: In function ‘print_cachestat’: test_cachestat.c:30:38: warning: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 2 has type ‘__u64’ {aka ‘long unsigned int’} [-Wformat=] By swi

Re: [PATCH] powerpc: Limit ARCH_HAS_KERNEL_FPU_SUPPORT to PPC64

2024-05-29 Thread Guenter Roeck
On Wed, May 29, 2024 at 09:28:50AM -0700, Samuel Holland wrote: > When building a 32-bit kernel, some toolchains do not allow mixing soft > float and hard float object files: > > LD vmlinux.o > powerpc64le-unknown-linux-musl-ld: lib/test_fpu_impl.o uses hard float, > arch/powerpc/kerne

Re: [PATCH] selftests/openat2: Fix build warnings on ppc64

2024-05-29 Thread Shuah Khan
On 5/20/24 21:03, Michael Ellerman wrote: Fix warnings like: openat2_test.c: In function ‘test_openat2_flags’: openat2_test.c:303:73: warning: format ‘%llX’ expects argument of type ‘long long unsigned int’, but argument 5 has type ‘__u64’ {aka ‘long unsigned int’} [-Wformat=] By sw

Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging

2024-05-29 Thread Yu Zhao
On Wed, May 29, 2024 at 3:59 PM Sean Christopherson wrote: > > On Wed, May 29, 2024, Yu Zhao wrote: > > On Wed, May 29, 2024 at 12:05 PM James Houghton > > wrote: > > > > > > Secondary MMUs are currently consulted for access/age information at > > > eviction time, but before then, we don't get a

Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging

2024-05-29 Thread Sean Christopherson
On Wed, May 29, 2024, Yu Zhao wrote: > On Wed, May 29, 2024 at 3:59 PM Sean Christopherson wrote: > > > > On Wed, May 29, 2024, Yu Zhao wrote: > > > On Wed, May 29, 2024 at 12:05 PM James Houghton > > > wrote: > > > > > > > > Secondary MMUs are currently consulted for access/age information at >

Re: [PATCH v4 2/7] mm: multi-gen LRU: Have secondary MMUs participate in aging

2024-05-29 Thread James Houghton
On Wed, May 29, 2024 at 3:58 PM Sean Christopherson wrote: > > On Wed, May 29, 2024, Yu Zhao wrote: > > On Wed, May 29, 2024 at 3:59 PM Sean Christopherson > > wrote: > > > > > > On Wed, May 29, 2024, Yu Zhao wrote: > > > > On Wed, May 29, 2024 at 12:05 PM James Houghton > > > > wrote: > > > >

Re: [PATCH] selftests/overlayfs: Fix build error on ppc64

2024-05-29 Thread Michael Ellerman
Shuah Khan writes: > On 5/20/24 20:26, Michael Ellerman wrote: >> Fix build error on ppc64: >>dev_in_maps.c: In function ‘get_file_dev_and_inode’: >>dev_in_maps.c:60:59: error: format ‘%llu’ expects argument of type >>‘long long unsigned int *’, but argument 7 has type ‘__u64 *’ {aka ‘

Re: [PATCH v4 3/7] KVM: Add lockless memslot walk to KVM

2024-05-29 Thread James Houghton
On Wed, May 29, 2024 at 2:51 PM Sean Christopherson wrote: > > On Wed, May 29, 2024, James Houghton wrote: > > @@ -686,10 +694,12 @@ static __always_inline int > > kvm_handle_hva_range(struct mmu_notifier *mn, > > return __kvm_handle_hva_range(kvm, &range).ret; > > } > > > > -static __alwa

Re: [PATCH v4 4/7] KVM: Move MMU lock acquisition for test/clear_young to architecture

2024-05-29 Thread James Houghton
On Wed, May 29, 2024 at 2:55 PM Sean Christopherson wrote: > > On Wed, May 29, 2024, James Houghton wrote: > > For implementation mmu_notifier_{test,clear}_young, the KVM memslot > > walker used to take the MMU lock for us. Now make the architectures > > take it themselves. > > Hmm, *forcing* arch

Re: [PATCH 04/23] scsi: initialize scsi midlayer limits before allocating the queue

2024-05-29 Thread Thorsten Leemhuis
On 29.05.24 16:36, Linux regression tracking (Thorsten Leemhuis) wrote: > [CCing the regression list, as it should be in the loop for regressions: > https://docs.kernel.org/admin-guide/reporting-regressions.html] > > On 20.05.24 17:15, Christoph Hellwig wrote: >> Adding ben and the linuxppc list.