* Re: [PATCH] powerpc/powernv: Add a print indicating when an IODA PE is released
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: Oliver O'Halloran, linuxppc-dev
In-Reply-To: <20200408112213.5549-1-oohall@gmail.com>
On Wed, 8 Apr 2020 21:22:13 +1000, Oliver O'Halloran wrote:
> Quite useful to know in some cases.
Applied to powerpc/next.
[1/1] powerpc/powernv: Add a print indicating when an IODA PE is released
https://git.kernel.org/powerpc/c/e5500ab657c51bec5af8dcf564a096de48e7a132
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/64s: Fix early_init_mmu section mismatch
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Nicholas Piggin; +Cc: Christian Zigotzky
In-Reply-To: <20200429070247.1678172-1-npiggin@gmail.com>
On Wed, 29 Apr 2020 17:02:47 +1000, Nicholas Piggin wrote:
> Christian reports:
>
> MODPOST vmlinux.o
> WARNING: modpost: vmlinux.o(.text.unlikely+0x1a0): Section mismatch in
> reference from the function .early_init_mmu() to the function
> .init.text:.radix__early_init_mmu()
> The function .early_init_mmu() references
> the function __init .radix__early_init_mmu().
> This is often because .early_init_mmu lacks a __init
> annotation or the annotation of .radix__early_init_mmu is wrong.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/64s: Fix early_init_mmu section mismatch
https://git.kernel.org/powerpc/c/9384e552aabb647ec22acb00181ca1715b0fcdfe
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/64: refactor interrupt exit irq disabling sequence
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Nicholas Piggin
In-Reply-To: <20200429062421.1675400-1-npiggin@gmail.com>
On Wed, 29 Apr 2020 16:24:21 +1000, Nicholas Piggin wrote:
> The same complicated sequence for juggling EE, RI, soft mask, and
> irq tracing is repeated 3 times, tidy these up into one function.
>
> This differs qiute a bit between sub architectures, so this makes
> the ppc32 port cleaner as well.
Applied to powerpc/next.
[1/1] powerpc/64: Refactor interrupt exit irq disabling sequence
https://git.kernel.org/powerpc/c/0bdad33d6bd7b80722e2f9e588d3d7c6d6e34978
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/64s/radix: Don't prefetch DAR in update_mmu_cache
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Nicholas Piggin
In-Reply-To: <20200504122907.49304-1-npiggin@gmail.com>
On Mon, 4 May 2020 22:29:07 +1000, Nicholas Piggin wrote:
> The idea behind this prefetch was to kick off a page table walk before
> returning from the fault, getting some pipelining advantage.
>
> But this never showed up any noticable performance advantage, and in
> fact with KUAP the prefetches are actually blocked and cause some
> kind of micro-architectural fault. Removing this improves page fault
> microbenchmark performance by about 9%.
Applied to powerpc/next.
[1/1] powerpc/64s/radix: Don't prefetch DAR in update_mmu_cache
https://git.kernel.org/powerpc/c/18594f9b8c45484bd527ebc6b08383b95f58ba73
cheers
^ permalink raw reply
* Re: [PATCH 1/4] powerpc/powernv/pci: Add helper to find ioda_pe from BDFN
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: Oliver O'Halloran, linuxppc-dev
In-Reply-To: <20200417073508.30356-2-oohall@gmail.com>
On Fri, 17 Apr 2020 17:35:05 +1000, Oliver O'Halloran wrote:
> For each PHB we maintain a reverse-map that can be used to find the
> PE that a BDFN is currently mapped to. Add a helper for doing this
> lookup so we can check if a PE has been configured without looking
> at pdn->pe_number.
Applied to powerpc/next.
[1/4] powerpc/powernv/pci: Add helper to find ioda_pe from BDFN
https://git.kernel.org/powerpc/c/a8d7d5fc2e1672924a391aa37ef8c02d1ec84a4e
[2/4] powerpc/powernv/pci: Re-work bus PE configuration
https://git.kernel.org/powerpc/c/dc3d8f85bb571c3640ebba24b82a527cf2cb3f24
[3/4] powerpc/powernv/pci: Reserve the root bus PE during init
https://git.kernel.org/powerpc/c/718d249aeadff058f79c2e6b25212dd45bd711ae
[4/4] powerpc/powernv/pci: Sprinkle around some WARN_ON()s
https://git.kernel.org/powerpc/c/6ae8aedf8fa932541f48a85219d75ca041c22080
cheers
^ permalink raw reply
* Re: [PATCH 0/3] powerpc/module_64: Fix _mcount() stub
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: Naveen N. Rao, linuxppc-dev; +Cc: Qian Cai, Steven Rostedt
In-Reply-To: <cover.1587488954.git.naveen.n.rao@linux.vnet.ibm.com>
On Tue, 21 Apr 2020 23:05:42 +0530, Naveen N. Rao wrote:
> This series addresses the crash reported by Qian Cai on ppc64le with
> -mprofile-kernel here:
> https://lore.kernel.org/r/15AC5B0E-A221-4B8C-9039-FA96B8EF7C88@lca.pw
>
> While fixing patch_instruction() should address the crash, we should
> still change the default stub we setup for _mcount() for cases where a
> kernel is built without ftrace.
>
> [...]
Applied to powerpc/next.
[1/3] powerpc/module_64: Consolidate ftrace code
https://git.kernel.org/powerpc/c/03b51416e876aea5e7638947e50831b6c988c246
[2/3] powerpc/module_64: Simplify check for -mprofile-kernel ftrace relocations
https://git.kernel.org/powerpc/c/1f2aaed2db03150428dbcd2ddee02ae6cb4bac52
[3/3] powerpc/module_64: Use special stub for _mcount() with -mprofile-kernel
https://git.kernel.org/powerpc/c/bd55e792de0844631d34487d43eaf3f13294ebfe
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/wii: Fix declaration made after definition
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: <20200413190644.16757-1-natechancellor@gmail.com>
On Mon, 13 Apr 2020 12:06:45 -0700, Nathan Chancellor wrote:
> A 0day randconfig uncovered an error with clang, trimmed for brevity:
>
> arch/powerpc/platforms/embedded6xx/wii.c:195:7: error: attribute
> declaration must precede definition [-Werror,-Wignored-attributes]
> if (!machine_is(wii))
> ^
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/wii: Fix declaration made after definition
https://git.kernel.org/powerpc/c/91ffeaa7e5dd62753e23a1204dc7ecd11f26eadc
cheers
^ permalink raw reply
* Re: [PATCH] powerpc/xmon: Show task->thread.regs in process display
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman
In-Reply-To: <20200520111740.953679-1-mpe@ellerman.id.au>
On Wed, 20 May 2020 21:17:40 +1000, Michael Ellerman wrote:
> Show the address of the tasks regs in the process listing in xmon. The
> regs should always be on the stack page that we also print the address
> of, but it's still helpful not to have to find them by hand.
Applied to powerpc/next.
[1/1] powerpc/xmon: Show task->thread.regs in process display
https://git.kernel.org/powerpc/c/0e7e92efe11bc5993def689e10f7bcb36f127651
cheers
^ permalink raw reply
* Re: [PATCH v4 1/2] powerpc/64s/hash: Add stress_slb kernel boot option to increase SLB faults
From: Michael Ellerman @ 2020-06-09 5:29 UTC (permalink / raw)
To: linuxppc-dev, Michael Ellerman; +Cc: npiggin
In-Reply-To: <20200511125825.3081305-1-mpe@ellerman.id.au>
On Mon, 11 May 2020 22:58:24 +1000, Michael Ellerman wrote:
> This option increases the number of SLB misses by limiting the number
> of kernel SLB entries, and increased flushing of cached lookaside
> information. This helps stress test difficult to hit paths in the
> kernel.
>
> [mpe: Relocate the code into arch/powerpc/mm, s/torture/stress/]
Applied to powerpc/next.
[1/1] powerpc/64s/hash: Add stress_slb kernel boot option to increase SLB faults
https://git.kernel.org/powerpc/c/82a1b8ed5604cccf30b6ff03bcd61640cd26369b
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
* 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: [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_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] 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] 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/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/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: 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/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 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 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 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 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 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 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
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