On 2024/7/27 上午7:52, Sean Christopherson wrote:
Mark pages accessed only in the slow path, before dropping mmu_lock when
faulting in guest memory so that LoongArch can convert to
kvm_release_faultin_page() without tripping its lockdep assertion on
mmu_lock being held.
Signed-off-by: Sean Chri
On 2024/7/27 上午7:52, Sean Christopherson wrote:
Mark pages/folios dirty only the slow page fault path, i.e. only when
mmu_lock is held and the operation is mmu_notifier-protected, as marking a
page/folio dirty after it has been written back can make some filesystems
unhappy (backing KVM guests
From: Simon Horman
> Sent: 31 July 2024 09:45
>
> On Tue, Jul 30, 2024 at 08:31:33AM +0200, Herve Codina wrote:
> > Received frame from QMC contains the CRC.
> > Upper layers don't need this CRC and tcpdump mentioned trailing junk
> > data due to this CRC presence.
> >
> > As some other HDLC drive
On Fri, Aug 02, 2024 at 09:03:47AM +0300, Baruch Siach wrote:
> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
> index 3b4be4ca3b08..62b36fda44c9 100644
> --- a/kernel/dma/direct.c
> +++ b/kernel/dma/direct.c
> @@ -20,7 +20,7 @@
> * it for entirely different regions. In that case the arch
On Thu, 1 Aug 2024 09:08:07 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> There are no users of HAVE_ARCH_NODEDATA_EXTENSION left, so
> arch_alloc_nodedata() and arch_refresh_nodedata() are not needed
> anymore.
>
> Replace the call to arch_alloc_nodedata() in free_area_i
On Thu, 1 Aug 2024 09:08:09 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Architectures that support NUMA duplicate the code that allocates
> NODE_DATA on the node-local memory with slight variations in reporting
> of the addresses where the memory was allocated.
>
> Use
On Thu, 1 Aug 2024 09:08:10 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Allocation of numa_distance uses memblock_phys_alloc_range() to limit
> allocation to be below the last mapped page.
>
> But NUMA initializaition runs after the direct map is populated and
> there i
These symbols are not used outside of the files, make them static to fix
sparse warnings:
sound/soc/fsl/lpc3xxx-i2s.c:261:30: warning: symbol 'lpc3xxx_i2s_dai_ops' was
not declared. Should it be static?
sound/soc/fsl/lpc3xxx-i2s.c:271:27: warning: symbol 'lpc3xxx_i2s_dai_driver'
was not declared
On Thu, 1 Aug 2024 09:08:11 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Instead of looping over numa_meminfo array to detect node's start and
> end addresses use get_pfn_range_for_init().
>
> This is shorter and make it easier to lift numa_memblks to generic code.
>
>
On Thu, 1 Aug 2024 09:08:17 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Move code dealing with numa_memblks from arch/x86 to mm/ and add Kconfig
> options to let x86 select it in its Kconfig.
>
> This code will be later reused by arch_numa.
>
> No functional changes.
>
On Thu, 1 Aug 2024 09:08:18 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Move code dealing with numa_distance array from arch/x86 to
> mm/numa_memblks.c
>
> This code will be later reused by arch_numa.
>
> No functional changes.
>
> Signed-off-by: Mike Rapoport (Micros
Sean Christopherson writes:
> Remove all kvm_{release,set}_pfn_*() APIs not that all users are gone.
now?
Otherwise:
Reviewed-by: Alex Bennée
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
On Thu, 1 Aug 2024 09:08:20 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Move most of x86::numa_init() to numa_memblks so that the latter will be
> more self-contained.
>
> With this numa_memblk data structures should not be exposed to the
> architecture specific code.
>
On Thu, 1 Aug 2024 09:08:21 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Make functions and variables that are exclusively used by numa_memblks
> static.
>
> Move numa_nodemask_from_meminfo() before its callers to avoid forward
> declaration.
>
> Signed-off-by: Mike Rap
On Thu, 1 Aug 2024 09:08:22 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> numa_cleanup_meminfo() moves blocks outside system RAM to
> numa_reserved_meminfo and it uses 0 and PFN_PHYS(max_pfn) to determine
> the memory boundaries.
>
> Replace the memory range boundaries wi
Sean Christopherson writes:
> Rename gfn_to_page_many_atomic() to kvm_prefetch_pages() to try and
> communicate its true purpose, as the "atomic" aspect is essentially a
> side effect of the fact that x86 uses the API while holding mmu_lock.
It's never too late to start adding some kdoc annotati
On Thu, 1 Aug 2024 09:08:19 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Move numa_emulation codfrom arch/x86 to mm/numa_emulation.c
>
> This code will be later reused by arch_numa.
>
> No functional changes.
>
> Signed-off-by: Mike Rapoport (Microsoft)
> Tested-by: Z
On Wed, Jul 24, 2024 at 6:39 AM Viresh Kumar wrote:
>
> On 22-07-24, 10:14, Jeff Johnson wrote:
> > With ARCH=powerpc, make allmodconfig && make W=1 C=1 reports:
> > WARNING: modpost: missing MODULE_DESCRIPTION() in
> > drivers/cpufreq/ppc-cbe-cpufreq.o
> > WARNING: modpost: missing MODULE_DESCRI
On Thu, Jul 18, 2024 at 06:14:18PM -0700, Jeff Johnson wrote:
> Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
> description is missing"), a module without a MODULE_DESCRIPTION() will
> result in a warning with make W=1. The following warning is being
> observed when building
On Thu, 1 Aug 2024 09:08:23 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Currently of_numa_parse_memory_nodes() returns 0 if no "memory" node in
> device tree contains "numa-node-id" property. This makes of_numa_init()
> to return "success" despite no NUMA nodes were actu
On 8/2/2024 6:15 AM, Herbert Xu wrote:
> On Thu, Jul 18, 2024 at 06:14:18PM -0700, Jeff Johnson wrote:
>> Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
>> description is missing"), a module without a MODULE_DESCRIPTION() will
>> result in a warning with make W=1. The followin
On Thu, 1 Aug 2024 09:08:24 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Until now arch_numa was directly translating firmware NUMA information
> to memblock.
>
> Using numa_memblks as an intermediate step has a few advantages:
> * alignment with more battle tested x86 i
On Thu, 1 Aug 2024 09:08:26 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> NUMA emulation can be now enabled on arm64 and riscv in addition to x86.
>
> Move description of numa=fake parameters from x86 documentation of
> admin-guide/kernel-parameters.txt
>
> Suggested-by:
On Fri, Aug 02, 2024 at 07:27:09AM -0700, Jeff Johnson wrote:
> On 8/2/2024 6:15 AM, Herbert Xu wrote:
> > On Thu, Jul 18, 2024 at 06:14:18PM -0700, Jeff Johnson wrote:
> >> Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
> >> description is missing"), a module without a MODULE
On Fri, Aug 2, 2024, at 16:27, Jeff Johnson wrote:
> On 8/2/2024 6:15 AM, Herbert Xu wrote:
>> On Thu, Jul 18, 2024 at 06:14:18PM -0700, Jeff Johnson wrote:
>>> Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
>>> description is missing"), a module without a MODULE_DESCRIPTION()
Convert dt-binding rcpm from txt to yaml format.
Add fsl,ls1028a-rcpm compatible string.
Additional changes:
- Add missed compatible string fsl,-rcpm.
- Remove map fsl,-rcpm to fsl,qoriq-rcpm-.
Signed-off-by: Frank Li
---
Change from v3 to v4
- Add missed fsl,ls1088a-rcpm, fsl,ls208xa-rcpm, fsl,
On Fri, Aug 02, 2024 at 01:03:47PM GMT, Stephen Rothwell wrote:
> As more and more sites are using DKIM signing or emails (and DMARC),
> more and more of the list traffic is not being delivered due to Mailman
> altering messages in subtle ways (so the DKIM signature is no longer
> valid). The easi
On 8/2/2024 8:16 AM, Arnd Bergmann wrote:
> On Fri, Aug 2, 2024, at 16:27, Jeff Johnson wrote:
>> On 8/2/2024 6:15 AM, Herbert Xu wrote:
>>> On Thu, Jul 18, 2024 at 06:14:18PM -0700, Jeff Johnson wrote:
Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
description is mi
On Thu, 1 Aug 2024 09:08:00 +0300
Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)"
>
> Hi,
>
> Following the discussion about handling of CXL fixed memory windows on
> arm64 [1] I decided to bite the bullet and move numa_memblks from x86 to
> the generic code so they will be available
Hi Stefan,
On 2024/07/29 03:27 PM, Stefan Bader wrote:
> On 26.07.24 13:37, Rob Herring wrote:
> > + Ubuntu kernel list, again
> >
> > On Thu, Jul 25, 2024 at 11:15:39PM +0530, Amit Machhiwal wrote:
> > > Hi Lizhi, Rob,
> > >
> > > Sorry for responding late. I got busy with some other things.
>
Add compatible string, fsl,ls1088a-isc, fsl,ls2080a-isc, fsl,lx2160a-isc.
Fix the below warning:
arch/arm64/boot/dts/freescale/fsl-ls2080a-qds.dtb: /soc/syscon@1f7: failed
to match any schema with compatible: ['fsl,ls2080a-isc', 'syscon']
Signed-off-by: Frank Li
---
.../devicetree/bindings/
On Fri, 02 Aug 2024 18:10:44 +0800, Yue Haibing wrote:
> These symbols are not used outside of the files, make them static to fix
> sparse warnings:
>
> sound/soc/fsl/lpc3xxx-i2s.c:261:30: warning: symbol 'lpc3xxx_i2s_dai_ops' was
> not declared. Should it be static?
> sound/soc/fsl/lpc3xxx-i2s.c
With CONFIG_PCI_DYNAMIC_OF_NODES [1], a hot-plug and hot-unplug sequence
of a PCI device attached to a PCI-bridge causes following kernel Oops on
a pseries KVM guest:
RTAS: event: 2, Type: Hotplug Event (229), Severity: 1
Kernel attempted to read user page (10ec0048) - exploit attempt? (uid:
On Fri, Aug 02, 2024, maobibo wrote:
> On 2024/7/27 上午7:52, Sean Christopherson wrote:
> > Mark pages/folios dirty only the slow page fault path, i.e. only when
> > mmu_lock is held and the operation is mmu_notifier-protected, as marking a
> > page/folio dirty after it has been written back can mak
On Wed, Jul 31, 2024 at 02:04:38PM +0200, David Hildenbrand wrote:
> On 15.07.24 21:21, Peter Xu wrote:
> > Currently the dax fault handler dumps the vma range when dynamic debugging
> > enabled. That's mostly not useful. Dump the (aligned) address instead
> > with the order info.
> >
> > Signed
On 2024/8/3 上午3:32, Sean Christopherson wrote:
On Fri, Aug 02, 2024, maobibo wrote:
On 2024/7/27 上午7:52, Sean Christopherson wrote:
Mark pages/folios dirty only the slow page fault path, i.e. only when
mmu_lock is held and the operation is mmu_notifier-protected, as marking a
page/folio dirt
36 matches
Mail list logo
