* Re: [PATCH v2 01/12] powerpc/52xx: Blacklist functions running with MMU disabled for kprobe
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Christophe Leroy, Paul Mackerras, Benjamin Herrenschmidt,
Michael Ellerman, naveen.n.rao
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <1ae02b6637b87fc5aaa1d5012c3e2cb30e62b4a3.1585670437.git.christophe.leroy@c-s.fr>
On Tue, 31 Mar 2020 16:03:36 +0000 (UTC), Christophe Leroy wrote:
> kprobe does not handle events happening in real mode, all
> functions running with MMU disabled have to be blacklisted.
Applied to powerpc/next.
[01/12] powerpc/52xx: Blacklist functions running with MMU disabled for kprobe
https://git.kernel.org/powerpc/c/e83f01fdb9143a4f90b17fbf7d8b8b21efb2f968
[02/12] powerpc/82xx: Blacklist pq2_restart() for kprobe
https://git.kernel.org/powerpc/c/1740f15a99d30a5e2710b2b0754e65fc5ba68d1d
[03/12] powerpc/83xx: Blacklist mpc83xx_deep_resume() for kprobe
https://git.kernel.org/powerpc/c/7aa85127b1a170694b042cbc35a07afe3904173e
[04/12] powerpc/powermac: Blacklist functions running with MMU disabled for kprobe
https://git.kernel.org/powerpc/c/32a820670fa00419375a964ca8bc569e1499b90d
[05/12] powerpc/mem: Blacklist flush_dcache_icache_phys() for kprobe
https://git.kernel.org/powerpc/c/a64371b5d4fb37199dcd04cb7bf0132894018e33
[06/12] powerpc/32s: Make local symbols non visible in hash_low.
https://git.kernel.org/powerpc/c/f892c21d2efb3b86ecbf8f5a95ea4abeedcc91b0
[07/12] powerpc/32s: Blacklist functions running with MMU disabled for kprobe
https://git.kernel.org/powerpc/c/e6209318d63e2774c5ab214b14b948079e040064
[08/12] powerpc/rtas: Remove machine_check_in_rtas()
https://git.kernel.org/powerpc/c/32746dfe4cf37f4077929601e8877a7fd02676e8
[09/12] powerpc/32: Blacklist functions running with MMU disabled for kprobe
https://git.kernel.org/powerpc/c/5f32e8361cba8c58c4f272a389296f489ecc2823
[10/12] powerpc/entry32: Blacklist exception entry points for kprobe.
https://git.kernel.org/powerpc/c/a616c442119f2ea5641e6abc215d7255b73b982b
[11/12] powerpc/entry32: Blacklist syscall exit points for kprobe.
https://git.kernel.org/powerpc/c/7cdf4401388572f720403a7038a178a4b30ac14c
[12/12] powerpc/entry32: Blacklist exception exit points for kprobe.
https://git.kernel.org/powerpc/c/e51c3e13709fe55d4d0eb50ba435bc53a64152bf
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/32: disable KASAN with pages bigger than 16k
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Paul Mackerras, Benjamin Herrenschmidt, Michael Ellerman,
Christophe Leroy
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <7195fcde7314ccbf7a081b356084a69d421b10d4.1590660977.git.christophe.leroy@csgroup.eu>
On Thu, 28 May 2020 10:17:04 +0000 (UTC), Christophe Leroy wrote:
> Mapping of early shadow area is implemented by using a single static
> page table having all entries pointing to the same early shadow page.
> The shadow area must therefore occupy full PGD entries.
>
> The shadow area has a size of 128Mbytes starting at 0xf8000000.
> With 4k pages, a PGD entry is 4Mbytes
> With 16k pages, a PGD entry is 64Mbytes
> With 64k pages, a PGD entry is 256Mbytes which is too big.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/32: Disable KASAN with pages bigger than 16k
https://git.kernel.org/powerpc/c/888468ce725a4cd56d72dc7e5096078f7a9251a0
cheers
^ permalink raw reply
* Re: [PATCH v2] powerpc/32s: Fix another build failure with CONFIG_PPC_KUAP_DEBUG
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Paul Mackerras, Benjamin Herrenschmidt, Michael Ellerman,
Christophe Leroy
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <b459e1600b969047a74e34251a84a3d6fdf1f312.1590858925.git.christophe.leroy@csgroup.eu>
On Sat, 30 May 2020 17:16:33 +0000 (UTC), Christophe Leroy wrote:
> 'thread' doesn't exist in kuap_check() macro.
>
> Use 'current' instead.
Applied to powerpc/next.
[1/1] powerpc/32s: Fix another build failure with CONFIG_PPC_KUAP_DEBUG
https://git.kernel.org/powerpc/c/74016701fe5f873ae23bf02835407227138d874d
cheers
^ permalink raw reply
* Re: [PATCH v4 00/45] Use hugepages to map kernel mem on 8xx
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Paul Mackerras, Benjamin Herrenschmidt, Michael Ellerman,
Christophe Leroy
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <cover.1589866984.git.christophe.leroy@csgroup.eu>
On Tue, 19 May 2020 05:48:42 +0000 (UTC), Christophe Leroy wrote:
> The main purpose of this big series is to:
> - reorganise huge page handling to avoid using mm_slices.
> - use huge pages to map kernel memory on the 8xx.
>
> The 8xx supports 4 page sizes: 4k, 16k, 512k and 8M.
> It uses 2 Level page tables, PGD having 1024 entries, each entry
> covering 4M address space. Then each page table has 1024 entries.
>
> [...]
Patches 1-6 and 9-45 applied to powerpc/next.
[01/45] powerpc/kasan: Fix error detection on memory allocation
https://git.kernel.org/powerpc/c/d132443a73d7a131775df46f33000f67ed92de1e
[02/45] powerpc/kasan: Fix issues by lowering KASAN_SHADOW_END
https://git.kernel.org/powerpc/c/3a66a24f6060e6775f8c02ac52329ea0152d7e58
[03/45] powerpc/kasan: Fix shadow pages allocation failure
https://git.kernel.org/powerpc/c/d2a91cef9bbdeb87b7449fdab1a6be6000930210
[04/45] powerpc/kasan: Remove unnecessary page table locking
https://git.kernel.org/powerpc/c/7c31c05e00fc5ff2067332c5f80e525573e7269c
[05/45] powerpc/kasan: Refactor update of early shadow mappings
https://git.kernel.org/powerpc/c/7dec42ab57f2f59feba82abf0353164479bfde4c
[06/45] powerpc/kasan: Declare kasan_init_region() weak
https://git.kernel.org/powerpc/c/ec97d022f621c6c850aec46d8818b49c6aae95ad
[09/45] powerpc/ptdump: Add _PAGE_COHERENT flag
https://git.kernel.org/powerpc/c/3af4786eb429b2df76cbd7ce3bae21467ac3e4fb
[10/45] powerpc/ptdump: Display size of BATs
https://git.kernel.org/powerpc/c/6b30830e2003d9d77696084ebe2fc19dbe7d6f70
[11/45] powerpc/ptdump: Standardise display of BAT flags
https://git.kernel.org/powerpc/c/8961a2a5353cca5451f648f4838cd848a3b2354c
[12/45] powerpc/ptdump: Properly handle non standard page size
https://git.kernel.org/powerpc/c/b00ff6d8c1c3898b0f768cbb38ef722d25bd2f39
[13/45] powerpc/ptdump: Handle hugepd at PGD level
https://git.kernel.org/powerpc/c/6b789a26d7da2e0256d199da980369ef8fb49ec6
[14/45] powerpc/32s: Don't warn when mapping RO data ROX.
https://git.kernel.org/powerpc/c/4b19f96a81bceaf0bcf44d79c0855c61158065ec
[15/45] powerpc/mm: Allocate static page tables for fixmap
https://git.kernel.org/powerpc/c/925ac141d106b55acbe112a9272f970631a3c082
[16/45] powerpc/mm: Fix conditions to perform MMU specific management by blocks on PPC32.
https://git.kernel.org/powerpc/c/4e3319c23a66dabfd6c35f4d2633d64d99b68096
[17/45] powerpc/mm: PTE_ATOMIC_UPDATES is only for 40x
https://git.kernel.org/powerpc/c/fadaac67c9007cad9fc485e36dcc54460d6d5886
[18/45] powerpc/mm: Refactor pte_update() on nohash/32
https://git.kernel.org/powerpc/c/2db99aeb63dd6e8808dc054d181c4d0e8645bbe0
[19/45] powerpc/mm: Refactor pte_update() on book3s/32
https://git.kernel.org/powerpc/c/1c1bf294882bd12669e39ccd7680c4ce34b7c15c
[20/45] powerpc/mm: Standardise __ptep_test_and_clear_young() params between PPC32 and PPC64
https://git.kernel.org/powerpc/c/c7fa77016eb6093df38fdabdb7a89bb9617e7185
[21/45] powerpc/mm: Standardise pte_update() prototype between PPC32 and PPC64
https://git.kernel.org/powerpc/c/06f52524870122fb43b214d27e8f4546da36f8ba
[22/45] powerpc/mm: Create a dedicated pte_update() for 8xx
https://git.kernel.org/powerpc/c/6ad41bfbc907be0cd414f09fa5382d2133376595
[23/45] powerpc/mm: Reduce hugepd size for 8M hugepages on 8xx
https://git.kernel.org/powerpc/c/b12c07a4bb064c0a8db7554557b89d40f57c936f
[24/45] powerpc/8xx: Drop CONFIG_8xx_COPYBACK option
https://git.kernel.org/powerpc/c/d3efcd38c0b99162d889e36a30425345a18edb33
[25/45] powerpc/8xx: Prepare handlers for _PAGE_HUGE for 512k pages.
https://git.kernel.org/powerpc/c/a891c43b97d315ee5f9fe8e797d3d48fc351e053
[26/45] powerpc/8xx: Manage 512k huge pages as standard pages.
https://git.kernel.org/powerpc/c/b250c8c08c79d1eb5354c7eaa84b7505f5f2d921
[27/45] powerpc/8xx: Only 8M pages are hugepte pages now
https://git.kernel.org/powerpc/c/d4870b89acd7c362ded08f9295e8d143cf7e0024
[28/45] powerpc/8xx: MM_SLICE is not needed anymore
https://git.kernel.org/powerpc/c/555904d07eef3a2e5fc458419edf6174362c4ddd
[29/45] powerpc/8xx: Move PPC_PIN_TLB options into 8xx Kconfig
https://git.kernel.org/powerpc/c/5d4656696c30cef56b2ab506b203533c818af04d
[30/45] powerpc/8xx: Add function to set pinned TLBs
https://git.kernel.org/powerpc/c/f76c8f6d257cefda60221c83af7f97d9f74cb3ce
[31/45] powerpc/8xx: Don't set IMMR map anymore at boot
https://git.kernel.org/powerpc/c/136a9a0f74d2e0d9de5515190fe80344b86b45cf
[32/45] powerpc/8xx: Always pin TLBs at startup.
https://git.kernel.org/powerpc/c/684c1664e0de63398aceb748343541b48d398710
[33/45] powerpc/8xx: Drop special handling of Linear and IMMR mappings in I/D TLB handlers
https://git.kernel.org/powerpc/c/400dc0f86102d2ad11d3601f1948fbb02e926431
[34/45] powerpc/8xx: Remove now unused TLB miss functions
https://git.kernel.org/powerpc/c/1251288e64ba44969e1c4d59e5ee88a6e873447b
[35/45] powerpc/8xx: Move DTLB perf handling closer.
https://git.kernel.org/powerpc/c/0c8c2c9c201b44eed6c10d7c5c8d25fe5aab87ce
[36/45] powerpc/mm: Don't be too strict with _etext alignment on PPC32
https://git.kernel.org/powerpc/c/a0591b60eef965f7f5255ad4696bbba9af4b43d0
[37/45] powerpc/8xx: Refactor kernel address boundary comparison
https://git.kernel.org/powerpc/c/c8bef10a9f17b2b9549e37878b2bcd48039c136b
[38/45] powerpc/8xx: Add a function to early map kernel via huge pages
https://git.kernel.org/powerpc/c/34536d78068318def0a370462cbc3319e1ca9014
[39/45] powerpc/8xx: Map IMMR with a huge page
https://git.kernel.org/powerpc/c/a623bb5861dc442dc8de9edc9b3116f8b7c235c4
[40/45] powerpc/8xx: Map linear memory with huge pages
https://git.kernel.org/powerpc/c/cf209951fa7f2e7a8ec92f45f27ea11bc024bbfc
[41/45] powerpc/8xx: Allow STRICT_KERNEL_RwX with pinned TLB
https://git.kernel.org/powerpc/c/da1adea07576722da4597b0df7d00931f0203229
[42/45] powerpc/8xx: Allow large TLBs with DEBUG_PAGEALLOC
https://git.kernel.org/powerpc/c/fcdafd10a363cf3278ce29c6c9a92930380c6cd8
[43/45] powerpc/8xx: Implement dedicated kasan_init_region()
https://git.kernel.org/powerpc/c/a2feeb2c2ecbd9c9206d66f238ca710b760c9ef5
[44/45] powerpc/32s: Allow mapping with BATs with DEBUG_PAGEALLOC
https://git.kernel.org/powerpc/c/2b279c0348af62f42be346c1ea6d70bac98df0f9
[45/45] powerpc/32s: Implement dedicated kasan_init_region()
https://git.kernel.org/powerpc/c/7974c4732642f710b5111165ae1f7f7fed822282
cheers
^ permalink raw reply
* Re: [PATCH 0/3] powerpc/xive: PCI hotplug fixes under PowerVM
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Cédric Le Goater, Michael Ellerman; +Cc: linuxppc-dev
In-Reply-To: <20200429075122.1216388-1-clg@kaod.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Wed, 29 Apr 2020 09:51:19 +0200, Cédric Le Goater wrote:
> Here are a couple of fixes for PCI hotplug issues for machines running
> under the POWER hypervisor using hash MMU and the XIVE interrupt mode.
>
> Commit 1ca3dec2b2df ("powerpc/xive: Prevent page fault issues in the
> machine crash handler") forced the mapping of the XIVE ESB page and
> this is now blocking the removal of a passthrough IO adapter because
> the PCI isolation fails with "valid outstanding translations". Under
> KVM, the ESB pages for the adapter interrupts are un-mapped from the
> guest by the hypervisor in the KVM XIVE native device. This is is now
> redundant but it's harmless.
>
> [...]
Patches 1 & 3 pplied to powerpc/next.
[1/3] powerpc/xive: Clear the page tables for the ESB IO mapping
https://git.kernel.org/powerpc/c/a101950fcb78b0ba20cd487be6627dea58d55c2b
[3/3] powerpc/xive: Do not expose a debugfs file when XIVE is disabled
https://git.kernel.org/powerpc/c/0755e85570a4615ca674ad6489d44d63916f1f3e
cheers
^ permalink raw reply
* Re: [PATCH v5 00/13] Modernise powerpc 40x
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: michal.simek, Christophe Leroy, Paul Mackerras,
Benjamin Herrenschmidt, Michael Ellerman, arnd
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <cover.1590079968.git.christophe.leroy@csgroup.eu>
On Thu, 21 May 2020 16:55:51 +0000 (UTC), Christophe Leroy wrote:
> v1 and v2 of this series were aiming at removing 40x entirely,
> but it led to protests.
>
> v3 is trying to start modernising powerpc 40x:
> - Rework TLB miss handlers to not use PTE_ATOMIC_UPDATES and _PAGE_HWWRITE
> - Remove old versions of 40x processors, namely 403 and 405GP and associated
> errata.
> - Last two patches are trivial changes in TLB miss handlers to reduce number
> of scratch registers.
>
> [...]
Applied to powerpc/next.
[01/13] powerpc: Remove Xilinx PPC405/PPC440 support
https://git.kernel.org/powerpc/c/7ade8495dcfd788a76e6877c9ea86f5207369ea4
[02/13] powerpc/40x: Rework 40x PTE access and TLB miss
https://git.kernel.org/powerpc/c/2c74e2586bb96012ffc05f1c819b05d9cad86d6e
[03/13] powerpc/pgtable: Drop PTE_ATOMIC_UPDATES
https://git.kernel.org/powerpc/c/4e1df545e2fae53e07c93b835c3dcc9d4917c849
[04/13] powerpc/40x: Remove support for IBM 403GCX
https://git.kernel.org/powerpc/c/1b5c0967ab8aa9424cdd5108de4e055d8aeaa9d0
[05/13] powerpc/40x: Remove STB03xxx
https://git.kernel.org/powerpc/c/7583b63c343c1076c89b2012fd8758473f046f5f
[06/13] powerpc/40x: Remove WALNUT
https://git.kernel.org/powerpc/c/5786074b96e38691a0cb3d3644ca2aa5d6d8830d
[07/13] powerpc/40x: Remove EP405
https://git.kernel.org/powerpc/c/548f5244f1064c9facb19c5e97c21e1e80102ea0
[08/13] powerpc/40x: Remove support for ISS Simulator
https://git.kernel.org/powerpc/c/2874ec75708eed59a47a9a986c02add747ae6e9b
[09/13] powerpc/40x: Remove support for IBM 405GP
https://git.kernel.org/powerpc/c/7d372d4ccdd55d5ead4d4ecbc336af4dd7d04344
[10/13] powerpc/40x: Remove IBM405 Erratum #51
https://git.kernel.org/powerpc/c/59fb463b48e904dfdfff64c7dd4d67f20ae27170
[11/13] powerpc: Remove IBM405 Erratum #77
https://git.kernel.org/powerpc/c/455531e9d88048c025ff9099796413df748d92b9
[12/13] powerpc/40x: Avoid using r12 in TLB miss handlers
https://git.kernel.org/powerpc/c/797f4016f6da4a90ac83e32b213b68ff7be3812b
[13/13] powerpc/40x: Don't save CR in SPRN_SPRG_SCRATCH6
https://git.kernel.org/powerpc/c/3aacaa719b7bf135551cabde2480e8f7bfdf7c7d
cheers
^ permalink raw reply
* Re: [PATCH] macintosh/ams-input: switch to using input device polling mode
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Benjamin Herrenschmidt, Dmitry Torokhov
Cc: Jean Delvare, linuxppc-dev, linux-kernel
In-Reply-To: <20191002214854.GA114387@dtor-ws>
On Wed, 2 Oct 2019 14:48:54 -0700, Dmitry Torokhov wrote:
> Now that instances of input_dev support polling mode natively,
> we no longer need to create input_polled_dev instance.
Applied to powerpc/next.
[1/1] macintosh/ams-input: switch to using input device polling mode
https://git.kernel.org/powerpc/c/0c444d98efad89e2a189d1a5a188e0385edac647
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/fadump: account for memory_limit while reserving memory
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman, Hari Bathini
Cc: Sourabh Jain, stable, Mahesh J Salgaonkar, Vasant Hegde,
kbuild test robot
In-Reply-To: <159057266320.22331.6571453892066907320.stgit@hbathini.in.ibm.com>
On Wed, 27 May 2020 15:14:35 +0530, Hari Bathini wrote:
> If the memory chunk found for reserving memory overshoots the memory
> limit imposed, do not proceed with reserving memory. Default behavior
> was this until commit 140777a3d8df ("powerpc/fadump: consider reserved
> ranges while reserving memory") changed it unwittingly.
Applied to powerpc/next.
[1/1] powerpc/fadump: Account for memory_limit while reserving memory
https://git.kernel.org/powerpc/c/9a2921e5baca1d25eb8d21f21d1e90581a6d0f68
cheers
^ permalink raw reply
* Re: [PATCHv4] powerpc/crashkernel: take "mem=" option into account
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: linuxppc-dev, Pingfan Liu; +Cc: kexec, Hari Bathini
In-Reply-To: <1585749644-4148-1-git-send-email-kernelfans@gmail.com>
On Wed, 1 Apr 2020 22:00:44 +0800, Pingfan Liu wrote:
> 'mem=" option is an easy way to put high pressure on memory during some
> test. Hence after applying the memory limit, instead of total mem, the
> actual usable memory should be considered when reserving mem for
> crashkernel. Otherwise the boot up may experience OOM issue.
>
> E.g. it would reserve 4G prior to the change and 512M afterward, if passing
> crashkernel="2G-4G:384M,4G-16G:512M,16G-64G:1G,64G-128G:2G,128G-:4G", and
> mem=5G on a 256G machine.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/crashkernel: Take "mem=" option into account
https://git.kernel.org/powerpc/c/be5470e0c285a68dc3afdea965032f5ddc8269d7
cheers
^ permalink raw reply
* Re: [PATCH v10 0/5] powerpc/hv-24x7: Expose chip/sockets info to add json file metric support for the hv_24x7 socket/chip level events
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: suka, Kajol Jain, mpe, linuxppc-dev, nathanl
Cc: ravi.bangoria, maddy, mpetlan, gregkh, alexander.shishkin, peterz,
anju, mamatha4, jmario, namhyung
In-Reply-To: <20200525104308.9814-1-kjain@linux.ibm.com>
On Mon, 25 May 2020 16:13:02 +0530, Kajol Jain wrote:
> Patchset fixes the inconsistent results we are getting when
> we run multiple 24x7 events.
>
> "hv_24x7" pmu interface events needs system dependent parameter
> like socket/chip/core. For example, hv_24x7 chip level events needs
> specific chip-id to which the data is requested should be added as part
> of pmu events.
>
> [...]
Applied to powerpc/next.
[1/5] powerpc/perf/hv-24x7: Fix inconsistent output values incase multiple hv-24x7 events run
https://git.kernel.org/powerpc/c/b4ac18eead28611ff470d0f47a35c4e0ac080d9c
[2/5] powerpc/hv-24x7: Add rtas call in hv-24x7 driver to get processor details
https://git.kernel.org/powerpc/c/8ba21426738207711347335b2cf3e99c690fc777
[3/5] powerpc/hv-24x7: Add sysfs files inside hv-24x7 device to show processor details
https://git.kernel.org/powerpc/c/60beb65da1efd4cc23d05141181c39b98487950f
[4/5] Documentation/ABI: Add ABI documentation for chips and sockets
https://git.kernel.org/powerpc/c/15cd1d35ba4a59832df693858ef046457107bd8d
[5/5] powerpc/pseries: Update hv-24x7 information after migration
https://git.kernel.org/powerpc/c/373b373053384f12951ae9f916043d955501d482
cheers
^ permalink raw reply
* Re: [PATCH v2 1/1] powerpc/crash: Use NMI context for printk when starting to crash
From: Michael Ellerman @ 2020-06-09 5:28 UTC (permalink / raw)
To: Thomas Gleixner, Greg Kroah-Hartman, Christophe Leroy,
Alexios Zavras, Leonardo Bras, Paul Mackerras,
Benjamin Herrenschmidt, Michael Ellerman, Enrico Weigelt
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <20200512214533.93878-1-leobras.c@gmail.com>
On Tue, 12 May 2020 18:45:35 -0300, Leonardo Bras wrote:
> Currently, if printk lock (logbuf_lock) is held by other thread during
> crash, there is a chance of deadlocking the crash on next printk, and
> blocking a possibly desired kdump.
>
> At the start of default_machine_crash_shutdown, make printk enter
> NMI context, as it will use per-cpu buffers to store the message,
> and avoid locking logbuf_lock.
Applied to powerpc/next.
[1/1] powerpc/crash: Use NMI context for printk when starting to crash
https://git.kernel.org/powerpc/c/af2876b501e42c3fb5174cac9dd02598436f0fdf
cheers
^ permalink raw reply
* Re: [PATCH v6 0/2] Implement reentrant rtas call
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: Thomas Gleixner, Greg Kroah-Hartman, Nadav Amit,
Gautham R. Shenoy, Leonardo Bras, Allison Randal, Paul Mackerras,
Benjamin Herrenschmidt, Michael Ellerman, Nathan Lynch,
Nicholas Piggin
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <20200518234245.200672-1-leobras.c@gmail.com>
On Mon, 18 May 2020 20:42:43 -0300, Leonardo Bras wrote:
> Patch 2 implement rtas_call_reentrant() for reentrant rtas-calls:
> "ibm,int-on", "ibm,int-off",ibm,get-xive" and "ibm,set-xive",
> according to LoPAPR Version 1.1 (March 24, 2016).
>
> For that, it's necessary that every call uses a different
> rtas buffer (rtas_args). Paul Mackerras suggested using the PACA
> structure for creating a per-cpu buffer for these calls.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/rtas: Move type/struct definitions from rtas.h into rtas-types.h
https://git.kernel.org/powerpc/c/783a015b747f606e803b798eb8b50c73c548691d
[2/2] powerpc/rtas: Implement reentrant rtas call
https://git.kernel.org/powerpc/c/b664db8e3f976d9233cc9ea5e3f8a8c0bcabeb48
cheers
^ permalink raw reply
* Re: [PATCH v3] powerpc/XIVE: SVM: share the event-queue page with the Hypervisor.
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Ram Pai, kvm-ppc
Cc: aik, andmike, groug, clg, sukadev, bauerman, david
In-Reply-To: <20200426020518.GC5853@oc0525413822.ibm.com>
On Sat, 25 Apr 2020 19:05:18 -0700, Ram Pai wrote:
> >From 10ea2eaf492ca3f22f67a5a63a2b7865e45299ad Mon Sep 17 00:00:00 2001
> From: Ram Pai <linuxram@us.ibm.com>
> Date: Mon, 24 Feb 2020 01:09:48 -0500
> Subject: [PATCH v3] powerpc/XIVE: SVM: share the event-queue page with the
> Hypervisor.
>
> XIVE interrupt controller uses an Event Queue (EQ) to enqueue event
> notifications when an exception occurs. The EQ is a single memory page
> provided by the O/S defining a circular buffer, one per server and
> priority couple.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/xive: Share the event-queue page with the Hypervisor.
https://git.kernel.org/powerpc/c/094235222d41d68d35de18170058d94a96a82628
cheers
^ permalink raw reply
* Re: [PATCH v3 1/1] powerpc/kernel: Enables memory hot-remove after reboot on pseries guests
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: Thomas Gleixner, Greg Kroah-Hartman, Leonardo Bras, Hari Bathini,
Allison Randal, Claudio Carvalho, Benjamin Herrenschmidt,
Michael Ellerman, Paul Mackerras, Nathan Fontenot, Bharata B Rao
Cc: linuxppc-dev, linux-kernel
In-Reply-To: <20200402195156.626430-1-leonardo@linux.ibm.com>
On Thu, 2 Apr 2020 16:51:57 -0300, Leonardo Bras wrote:
> While providing guests, it's desirable to resize it's memory on demand.
>
> By now, it's possible to do so by creating a guest with a small base
> memory, hot-plugging all the rest, and using 'movable_node' kernel
> command-line parameter, which puts all hot-plugged memory in
> ZONE_MOVABLE, allowing it to be removed whenever needed.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/kernel: Enables memory hot-remove after reboot on pseries guests
https://git.kernel.org/powerpc/c/b6eca183e23e7a6625a0d2cdb806b7cd1abcd2d2
cheers
^ permalink raw reply
* Re: [PATCH v2 0/2] powerpc: Remove support for ppc405/440 Xilinx platforms
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: monstr, sfr, Michal Simek, linux-kernel, maz, git
Cc: Mark Rutland, Kate Stewart, linux-fbdev, Geert Uytterhoeven,
linux-doc, alsa-devel, dri-devel, Richard Fontana, Paul Mackerras,
Miquel Raynal, Mauro Carvalho Chehab, Fabio Estevam, Sasha Levin,
Jonathan Corbet, Masahiro Yamada, YueHaibing, Krzysztof Kozlowski,
Dmitry Vyukov, devicetree, Andrew Donnellan, Arnd Bergmann,
Bartlomiej Zolnierkiewicz, Alistair Popple, Nicholas Piggin,
Alexios Zavras, Desnes A. Nunes do Rosario, Mark Brown,
Jonathan Cameron, Thomas Gleixner, Andy Shevchenko,
Allison Randal, linux-arm-kernel, Enrico Weigelt, Wei Hu,
Greg Kroah-Hartman, Nick Desaulniers, Takashi Iwai, Rob Herring,
C hristophe Leroy, linuxppc-dev, David S. Miller,
Thiago Jung Bauermann
In-Reply-To: <cover.1585575111.git.michal.simek@xilinx.com>
On Mon, 30 Mar 2020 15:32:15 +0200, Michal Simek wrote:
> recently we wanted to update xilinx intc driver and we found that function
> which we wanted to remove is still wired by ancient Xilinx PowerPC
> platforms. Here is the thread about it.
> https://lore.kernel.org/linux-next/48d3232d-0f1d-42ea-3109-f44bbabfa2e8@xilinx.com/
>
> I have been talking about it internally and there is no interest in these
> platforms and it is also orphan for quite a long time. None is really
> running/testing these platforms regularly that's why I think it makes sense
> to remove them also with drivers which are specific to this platform.
>
> [...]
Applied to powerpc/next.
[1/2] sound: ac97: Remove sound driver for ancient platform
https://git.kernel.org/powerpc/c/f16dca3e30c14aff545a834a7c1a1bb02b9edb48
[2/2] powerpc: Remove Xilinx PPC405/PPC440 support
https://git.kernel.org/powerpc/c/7ade8495dcfd788a76e6877c9ea86f5207369ea4
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/configs: Add LIBNVDIMM to ppc64_defconfig
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: mpe, Michael Neuling; +Cc: linuxppc-dev
In-Reply-To: <20200519043009.3081885-1-mikey@neuling.org>
On Tue, 19 May 2020 14:30:09 +1000, Michael Neuling wrote:
> This gives us OF_PMEM which is useful in mambo.
>
> This adds 153K to the text of ppc64le_defconfig which 0.8% of the
> total text.
>
> LIBNVDIMM text data bss dec hex
> Without 18574833 5518150 1539240 25632223 1871ddf
> With 18727834 5546206 1539368 25813408 189e1a0
Applied to powerpc/next.
[1/1] powerpc/configs: Add LIBNVDIMM to ppc64_defconfig
https://git.kernel.org/powerpc/c/08b1add150a8863665676d0ac9c3ad2d34b2540c
cheers
^ permalink raw reply
* Re: [PATCH] powerpc: Fix misleading small cores print
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: mpe, Michael Neuling; +Cc: Gautham R . Shenoy, linuxppc-dev
In-Reply-To: <20200528230731.1235752-1-mikey@neuling.org>
On Fri, 29 May 2020 09:07:31 +1000, Michael Neuling wrote:
> Currently when we boot on a big core system, we get this print:
> [ 0.040500] Using small cores at SMT level
>
> This is misleading as we've actually detected big cores.
>
> This patch clears up the print to say we've detect big cores but are
> using small cores for scheduling.
Applied to powerpc/next.
[1/1] powerpc: Fix misleading small cores print
https://git.kernel.org/powerpc/c/82a7cebdd95cffa55449d6c1d97cc9b743a66056
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/tm: Document h/rfid and mtmsrd quirk
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: mpe, Michael Neuling; +Cc: linuxppc-dev, npiggin, Gustavo Romero
In-Reply-To: <20200325040546.3091563-1-mikey@neuling.org>
On Wed, 25 Mar 2020 15:05:46 +1100, Michael Neuling wrote:
> The ISA has a quirk that's useful for the Linux implementation.
> Document it here so others are less likely to trip over it.
Applied to powerpc/next.
[1/1] powerpc/tm: Document h/rfid and mtmsrd quirk
https://git.kernel.org/powerpc/c/b8707e2374f68cac79de553ae1ee5c35913813bd
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/4xx: Don't unmap NULL mbase
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman; +Cc: huhai
In-Reply-To: <20200521072648.1254699-1-mpe@ellerman.id.au>
On Thu, 21 May 2020 17:26:48 +1000, Michael Ellerman wrote:
>
Applied to powerpc/next.
[1/1] powerpc/4xx: Don't unmap NULL mbase
https://git.kernel.org/powerpc/c/bcec081ecc940fc38730b29c743bbee661164161
cheers
^ permalink raw reply
* Re: [PATCH] powerpc: Add ppc_inst_as_u64()
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman; +Cc: jniethe5
In-Reply-To: <20200525055004.2182328-1-mpe@ellerman.id.au>
On Mon, 25 May 2020 15:50:04 +1000, Michael Ellerman wrote:
> The code patching code wants to get the value of a struct ppc_inst as
> a u64 when the instruction is prefixed, so we can pass the u64 down to
> __put_user_asm() and write it with a single store.
>
> This is a bit awkward because the value differs based on the CPU
> endianness, so add a helper to do the conversion.
Applied to powerpc/next.
[1/1] powerpc: Add ppc_inst_as_u64()
https://git.kernel.org/powerpc/c/16ef9767e4dc5cf03a71ae7bc2bc588dbbe7983e
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/configs/64s: Enable CONFIG_PRINTK_CALLER
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman
In-Reply-To: <20200520121257.961112-1-mpe@ellerman.id.au>
On Wed, 20 May 2020 22:12:57 +1000, Michael Ellerman wrote:
> This adds the CPU or thread number to printk messages. This helps a
> lot when deciphering concurrent oopses that have been interleaved.
>
> Example output, of PID1 (T1) triggering a warning:
>
> [ 1.581678][ T1] WARNING: CPU: 0 PID: 1 at crypto/rsa-pkcs1pad.c:539 pkcs1pad_verify+0x38/0x140
> [ 1.581681][ T1] Modules linked in:
> [ 1.581693][ T1] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.5.0-rc5-gcc-8.2.0-00121-gf84c2e595927-dirty #1515
> [ 1.581700][ T1] NIP: c000000000207d64 LR: c000000000207d3c CTR: c000000000207d2c
> [ 1.581708][ T1] REGS: c0000000fd2e7560 TRAP: 0700 Not tainted (5.5.0-rc5-gcc-8.2.0-00121-gf84c2e595927-dirty)
> [ 1.581712][ T1] MSR: 9000000000029033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 44000222 XER: 00040000
Applied to powerpc/next.
[1/1] powerpc/configs/64s: Enable CONFIG_PRINTK_CALLER
https://git.kernel.org/powerpc/c/598c01b5b2fca3a9de8ad3400edbff98ec22f0b2
cheers
^ permalink raw reply
* Re: [PATCH v2] powerpc: Add ppc_inst_next()
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman; +Cc: christophe.leroy, jniethe5
In-Reply-To: <20200522133318.1681406-1-mpe@ellerman.id.au>
On Fri, 22 May 2020 23:33:18 +1000, Michael Ellerman wrote:
> In a few places we want to calculate the address of the next
> instruction. Previously that was simple, we just added 4 bytes, or if
> using a u32 * we incremented that pointer by 1.
>
> But prefixed instructions make it more complicated, we need to advance
> by either 4 or 8 bytes depending on the actual instruction. We also
> can't do pointer arithmetic using struct ppc_inst, because it is
> always 8 bytes in size on 64-bit, even though we might only need to
> advance by 4 bytes.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: Add ppc_inst_next()
https://git.kernel.org/powerpc/c/c5ff46d69c410f7fac173e4fde3eea484b4b4eda
cheers
^ permalink raw reply
* Re: [PATCH] input: i8042: Remove special PowerPC handling
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: Nathan Chancellor, Michael Ellerman
Cc: clang-built-linux, linuxppc-dev, Paul Mackerras, linux-kernel,
kbuild test robot
In-Reply-To: <20200518181043.3363953-1-natechancellor@gmail.com>
On Mon, 18 May 2020 11:10:43 -0700, Nathan Chancellor wrote:
> This causes a build error with CONFIG_WALNUT because kb_cs and kb_data
> were removed in commit 917f0af9e5a9 ("powerpc: Remove arch/ppc and
> include/asm-ppc").
>
> ld.lld: error: undefined symbol: kb_cs
> > referenced by i8042-ppcio.h:28 (drivers/input/serio/i8042-ppcio.h:28)
> > input/serio/i8042.o:(__i8042_command) in archive drivers/built-in.a
> > referenced by i8042-ppcio.h:28 (drivers/input/serio/i8042-ppcio.h:28)
> > input/serio/i8042.o:(__i8042_command) in archive drivers/built-in.a
> > referenced by i8042-ppcio.h:28 (drivers/input/serio/i8042-ppcio.h:28)
> > input/serio/i8042.o:(__i8042_command) in archive drivers/built-in.a
>
> [...]
Applied to powerpc/next.
[1/1] input: i8042 - Remove special PowerPC handling
https://git.kernel.org/powerpc/c/e4f4ffa8a98c24a4ab482669b1e2b4cfce3f52f4
cheers
^ permalink raw reply
* Re: [PATCH v2] powerpc: Add ppc_inst_as_u64()
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman; +Cc: jniethe5
In-Reply-To: <20200526072630.2487363-1-mpe@ellerman.id.au>
On Tue, 26 May 2020 17:26:30 +1000, Michael Ellerman wrote:
> The code patching code wants to get the value of a struct ppc_inst as
> a u64 when the instruction is prefixed, so we can pass the u64 down to
> __put_user_asm() and write it with a single store.
>
> The optprobes code wants to load a struct ppc_inst as an immediate
> into a register so it is useful to have it as a u64 to use the
> existing helper function.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc: Add ppc_inst_as_u64()
https://git.kernel.org/powerpc/c/16ef9767e4dc5cf03a71ae7bc2bc588dbbe7983e
cheers
^ permalink raw reply
* Re: [RFC PATCH 1/4] powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman; +Cc: alistair, mikey, npiggin, jniethe5
In-Reply-To: <20200527145843.2761782-1-mpe@ellerman.id.au>
On Thu, 28 May 2020 00:58:40 +1000, Michael Ellerman wrote:
> __init_FSCR() was added originally in commit 2468dcf641e4 ("powerpc:
> Add support for context switching the TAR register") (Feb 2013), and
> only set FSCR_TAR.
>
> At that point FSCR (Facility Status and Control Register) was not
> context switched, so the setting was permanent after boot.
>
> [...]
Applied to powerpc/next.
[1/4] powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()
https://git.kernel.org/powerpc/c/0828137e8f16721842468e33df0460044a0c588b
[2/4] powerpc/64s: Don't let DT CPU features set FSCR_DSCR
https://git.kernel.org/powerpc/c/993e3d96fd08c3ebf7566e43be9b8cd622063e6d
[3/4] powerpc/64s: Save FSCR to init_task.thread.fscr after feature init
https://git.kernel.org/powerpc/c/912c0a7f2b5daa3cbb2bc10f303981e493de73bd
[4/4] powerpc/64s: Don't set FSCR bits in INIT_THREAD
https://git.kernel.org/powerpc/c/c887ef5707591e84f80271e95e99ff9fb38987b5
cheers
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox