aware of will wrap the line if it's too long, so the
length should not be a functional problem. If anything it should help on
consoles like VGA by using less vertical space.
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/process.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff
7c 7d295378
^D
All code
0: f0 ff c1 fb std r30,-16(r1)
4: c1 ff 21 f8 stdur1,-64(r1)
8: 78 1b 7d 7c mr r29,r3
...
Note that the script doesn't cope well with printk timestamps or printk
caller info.
Reported-by: Matthew Wilcox
Signed
Christophe Leroy writes:
> Le 05/10/2022 à 07:32, Benjamin Gray a écrit :
>> Implement static call support for 64 bit V2 ABI. This requires making
>> sure the TOC is kept correct across kernel-module boundaries. As a
>> secondary concern, it tries to use the local entry point of a target
>>
Matthew Wilcox writes:
> On Fri, Sep 30, 2022 at 12:01:26PM +1000, Michael Ellerman wrote:
>> Matthew Wilcox writes:
>> >> [ 4681.238745] Instruction dump:
>> >> [ 4681.238749] fbc1fff0 f821ffc1 7c7d1b78 7c9c2378 ebc30028 7fdff378
>> >> 4800
On Thu, 8 Sep 2022 23:25:41 +1000, Nicholas Piggin wrote:
> On guest entry, vcpu->cpu and vcpu->arch.thread_cpu are set after
> disabling host irqs. On guest exit there is a window whre tick time
> accounting briefly enables irqs before these fields are cleared.
>
> Move them up to ensure they
On Tue, 23 Aug 2022 01:17:51 +0200, Pali Rohár wrote:
> 'extern' keywork is pointless and deprecated for function prototypes.
>
>
Applied to powerpc/next.
[1/1] powerpc: udbg: Remove extern function prototypes
https://git.kernel.org/powerpc/c/6bd7ff497b4af13ea3d53781ffca7dc744dbb4da
On Wed, 21 Sep 2022 16:55:40 +1000, Rohan McLure wrote:
> V5 available here:
>
> Link:
> https://lore.kernel.org/all/20220916053300.786330-2-rmcl...@linux.ibm.com/T/
>
> Implement a syscall wrapper, causing arguments to handlers to be passed
> via a struct pt_regs on the stack. The syscall
On Tue, 23 Aug 2022 01:15:01 +0200, Pali Rohár wrote:
> Currently powerpc early debugging contains lot of platform specific
> options, but does not support standard UART / serial 16550 console.
>
> Later legacy_serial.c code supports registering UART as early debug console
> from device tree but
On Wed, 31 Aug 2022 00:55:00 +0200, Pali Rohár wrote:
> Partition partition@2 contains generic kernel image and it does not
> have to be used only for rescue purposes. Partition partition@1c
> contains bootable rescue system and partition partition@34 contains
> factory image/data for
On Mon, 26 Sep 2022 15:42:58 +1000, Nicholas Piggin wrote:
> No real changes since last posting, I just pulled fixes from several
> series together and rearranged them and updated changelogs slightly.
>
> Thanks,
> Nick
>
> Nicholas Piggin (7):
> powerpc/64/interrupt: Fix false warning in
On Sat, 27 Aug 2022 15:15:38 +0200, Pali Rohár wrote:
> DSA cpu port node has to be marked with "cpu" label.
> So fix it for both cpu port nodes.
>
>
Applied to powerpc/next.
[1/1] powerpc: dts: turris1x.dts: Fix labels in DSA cpu port nodes
On Sat, 27 Aug 2022 15:44:54 +0200, Pali Rohár wrote:
> uImage boot wrapper should not use SPE instructions, like kernel itself.
> Boot wrapper has already disabled Altivec and VSX instructions but not SPE.
> Options -mno-spe and -mspe=no already set when compilation of kernel, but
> not when
On Mon, 26 Sep 2022 15:56:15 +1000, Nicholas Piggin wrote:
> This series provides a machine check handler to catch out of
> bounds memory accesses in early boot before the MMU is enabled.
>
> Since v1:
> - 64e compile fix
>
> Nicholas Piggin (5):
> powerpc/64s/interrupt: move early boot ILE
On Fri, 2 Sep 2022 23:21:02 +0200, Pali Rohár wrote:
> Commit 2eb28006431c ("powerpc/e500v2: Add Power ISA properties to comply
> with ePAPR 1.1") introduced new include file e500v2_power_isa.dtsi and
> should have used it for all e500v2 platforms. But apparently it was used
> also for e500v1
On Tue, 20 Sep 2022 22:22:58 +1000, Nicholas Piggin wrote:
> The wait instruction encoding changed between ISA v2.07 and ISA v3.0.
> In v3.1 the instruction gained a new field.
>
> Update the PPC_WAIT macro to the current encoding. Rename the older
> incompatible one with a _v203 suffix as it was
On Fri, 16 Sep 2022 14:07:48 +1000, Nicholas Piggin wrote:
> This series is mainly about moving more things out of writable and
> executable memory, and slightly moving the linker script in the
> direction of the binutils ld internal linker script as we do.
>
> Thanks,
> Nick
>
> [...]
Applied
On Mon, 26 Sep 2022 13:40:52 +1000, Nicholas Piggin wrote:
> This is a cleaned up set of the initial prep patches from the pcrel
> series, dealing with regularising addressing variables from asm
> and using helper macros more consistently.
>
> Changes since v1:
> - Use "REGS" stack frame marker
On Sat, 10 Sep 2022 00:24:57 +1000, Nicholas Piggin wrote:
> Setting DEC to maximum at the start of the timer interrupt is not
> necessary and can be avoided for performance when MSR[EE] is not
> enabled during the handler as explained in commit 0faf20a1ad16
> ("powerpc/64s/interrupt: Don't enable
On Thu, 29 Sep 2022 13:21:20 +1000, Nicholas Piggin wrote:
> arch/powerpc/kernel/systbl_chk.sh has not been referenced since commit
> ab66dcc76d6a ("powerpc: generate uapi header and system call table
> files"). Remove it.
>
>
Applied to powerpc/next.
[1/1] powerpc: remove orphan systbl_chk.sh
On Mon, 26 Sep 2022 07:57:23 +, Nicholas Miehlbradt wrote:
> There is support for DEBUG_PAGEALLOC on hash but not on radix.
> Add support on radix.
>
>
Applied to powerpc/next.
[1/4] powerpc/64s: Add DEBUG_PAGEALLOC for radix
On Mon, 26 Sep 2022 15:38:23 +1000, Nicholas Piggin wrote:
> The .toc section is not really intended for arbitrary data. Writable
> data in particular prevents making the TOC read-only after relocation.
> Move hcall_tracepoint_refcount into the .data section.
>
>
Applied to powerpc/next.
[1/1]
On Fri, 23 Sep 2022 13:30:04 +1000, Nicholas Piggin wrote:
> This adds basic POWER10_CPU option, which builds with -mcpu=power10.
>
>
Applied to powerpc/next.
[1/1] powerpc/64s: POWER10 CPU Kconfig build option
https://git.kernel.org/powerpc/c/4b2a9315f20d98576e25c9e4572e9a8e028d7aa2
On Thu, 8 Sep 2022 23:25:41 +1000, Nicholas Piggin wrote:
> On guest entry, vcpu->cpu and vcpu->arch.thread_cpu are set after
> disabling host irqs. On guest exit there is a window whre tick time
> accounting briefly enables irqs before these fields are cleared.
>
> Move them up to ensure they
On Wed, 21 Sep 2022 11:41:02 +1000, Nicholas Piggin wrote:
> Big-endian GENERIC_CPU supports 970, but builds with -mcpu=power5.
> POWER5 is ISA v2.02 whereas 970 is v2.01 plus Altivec. 2.02 added
> the popcntb instruction which a compiler might use.
>
> Use -mcpu=power4.
>
>
> [...]
Applied to
On Mon, 26 Sep 2022 17:02:50 -0500, Nathan Lynch wrote:
> At boot time, it is not necessary to delay between polls of
> cpu_callin_map when waiting for a kicked CPU to come up. Remove the
> delay intervals, but preserve the overall deadline (five seconds).
>
> At run time, the first poll result
On Mon, 26 Sep 2022 08:16:41 -0500, Nathan Lynch wrote:
> Add two new lockdown reasons for use in powerpc's pseries platform
> code.
>
> The pseries platform allows hardware-level error injection via certain
> calls to the RTAS (Run Time Abstraction Services) firmware. ACPI-based
> error
On Fri, 16 Sep 2022 23:15:23 +1000, Michael Ellerman wrote:
> Currently powerpc selects HAVE_EFFICIENT_UNALIGNED_ACCESS in all cases
> but one. The exception is if the kernel is being built little endian and
> explicitly targetted for Power7.
>
> The combination of Power7 an
On Fri, 30 Sep 2022 18:27:04 +1000, Michael Ellerman wrote:
> Create a hardware description string, which we will use to record
> various details of the hardware platform we are running on.
>
> Print the accumulated description at boot, and use it to set the generic
> description w
On Wed, 28 Sep 2022 23:09:41 +1000, Michael Ellerman wrote:
> The bulk of this was moved/reworded in:
> 57f266497d81 ("powerpc: Use gas sections for arranging exception vectors")
>
> And now appears around line 700 in arch/powerpc/kernel/exceptions-64s.S.
>
>
Ap
On Mon, 19 Sep 2022 15:27:55 +1000, Michael Ellerman wrote:
> The original microwatt submission[1] included some early debug code for
> using the Microwatt "potato" UART.
>
> The series that was eventually merged switched to using a standard UART,
> and so doesn't nee
On Wed, 28 Sep 2022 23:09:51 +1000, Michael Ellerman wrote:
> No toolchain we support should be generating stabs debug information
> anymore. Drop the sections entirely from our linker scripts.
>
> We removed all the manual stabs annotations in commit
> 12318163737c ("powerpc/
On Thu, 29 Sep 2022 15:15:17 +1000, Michael Ellerman wrote:
> Make sure the ultravisor code at least gets some build testing by
> enabling it in powernv_defconfig.
>
>
Applied to powerpc/next.
[1/1] powerpc/configs: Enable PPC_UV in powernv_defconfig
https://git.kernel.o
On Wed, 28 Sep 2022 23:09:12 +1000, Michael Ellerman wrote:
> This used to be about the 0x4300 handler, but that was moved in commit
> da2bc4644c75 ("powerpc/64s: Add new exception vector macros").
>
> Note that "STAB" here refers to "Segment Table" not t
On Tue, 13 Sep 2022 22:45:45 +1000, Michael Ellerman wrote:
> In interrupt_64.S, formerly entry_64.S, there are two toc entries
> created for sys_call_table and compat_sys_call_table.
>
> These are no longer used, since the system call entry was converted from
> asm to C,
On Fri, 16 Sep 2022 23:14:21 +1000, Michael Ellerman wrote:
> Add a check that STRICT_ALIGN_SIZE is aligned to at least PAGE_SIZE.
>
> That then makes the alignment to PAGE_SIZE immediately after the
> alignment to STRICT_ALIGN_SIZE redundant, so remove it.
>
>
Applied to p
On Sat, 3 Sep 2022 22:36:39 +1000, Michael Ellerman wrote:
> On powerpc there are two ways for huge pages to be represented in the
> top level page table, aka PGD (Page Global Directory).
>
> If the address space mapped by an individual PGD entry does not
> correspond to a given
On Wed, 28 Sep 2022 01:04:18 +1000, Michael Ellerman wrote:
> Now that the stack frame regs marker is only 32-bits it is not as
> obvious in memory dumps and easier to miss, eg:
>
> c4733e40 ||
> c4733e50 0
On Thu, 29 Sep 2022 12:15:02 +0200, Lukas Bulwahn wrote:
> Clean up config files by:
> - removing configs that were deleted in the past
> - removing configs not in tree and without recently pending patches
> - adding new configs that are replacements for old configs in the file
>
> For some
On Fri, 23 Sep 2022 17:32:53 +0800, Li Huafei wrote:
> I found a null pointer reference in arch_prepare_kprobe():
>
> # echo 'p cmdline_proc_show' > kprobe_events
> # echo 'p cmdline_proc_show+16' >> kprobe_events
> [ 67.278533][ T122] Kernel attempted to read user page (0) - exploit
>
On Mon, 12 Sep 2022 12:20:31 +0530, Hari Bathini wrote:
> Since commit e641eb03ab2b0 ("powerpc: Fix up the kdump base cap to
> 128M") memory for kdump kernel has been reserved at an offset of
> 128MB. This held up well for a long time before running into boot
> failure on LPARs having a lot of
On Tue, 27 Sep 2022 18:29:27 -0700, Haren Myneni wrote:
> The data storage interrupt (DSI) error will be generated when the
> paste operation is issued on the suspended Nest Accelerator (NX)
> window due to NX state changes. The hypervisor expects the
> partition to ignore this error during page
On Wed, 28 Sep 2022 18:57:33 -0700, Haren Myneni wrote:
> Generally the hypervisor decides to allocate a window on different
> VAS instances. But if the user space wishes to allocate on the
> current VAS instance where the process is executing, the kernel has
> to pass associativity domain IDs to
On Thu, 22 Sep 2022 01:27:07 -0700, Haren Myneni wrote:
> When the migration is initiated, the hypervisor changes VAS
> mappings as part of pre-migration event. Then the OS gets the
> migration event which closes all VAS windows before the migration
> starts. NX generates continuous faults until
On Tue, 20 Sep 2022 14:22:59 +0200, David Hildenbrand wrote:
> As it seems to be rather unclear if/when to use BUG(), BUG_ON(),
> VM_BUG_ON(), WARN_ON_ONCE(), ... let's try to document the result of a
> recent discussion.
>
> Details can be found in patch #1.
>
> RFC -> v1:
> *
On Mon, 19 Sep 2022 19:01:25 +0200, Christophe Leroy wrote:
> CONFIG_PPC_FSL_BOOKE doesn't exist. Should be CONFIG_FSL_BOOKE.
>
>
Applied to powerpc/next.
[01/19] powerpc/Kconfig: Fix non existing CONFIG_PPC_FSL_BOOKE
On Wed, 7 Sep 2022 12:05:01 +0200, Christophe Leroy wrote:
> PAGE_KERNEL_TEXT, PAGE_KERNEL_EXEC and PAGE_AGP are the same
> for all powerpcs.
>
> Remove duplicated definitions.
>
>
Applied to powerpc/next.
[1/1] powerpc: Reduce redundancy in pgtable.h
On Wed, 7 Sep 2022 12:05:21 +0200, Christophe Leroy wrote:
> Avoid multi-lines to help getting a complete view when using
> grep. They still remain under the 100 chars limit.
>
>
Applied to powerpc/next.
[1/1] powerpc: Make PAGE_KERNEL_xxx macros grep-friendly
On Tue, 20 Sep 2022 08:41:08 +0200, Christophe Leroy wrote:
> This partialy reapply commit ef5b570d3700 ("powerpc/irq: Don't
> open code irq_soft_mask helpers") which was reverted by
> commit 684c68d92e2e ("Revert "powerpc/irq: Don't open code
> irq_soft_mask helpers"")
>
>
On Tue, 20 Sep 2022 19:36:42 +0200, Christophe Leroy wrote:
> In addition to checking whether a page is reserved before allocating
> it to highmem, verify that it is valid memory.
>
> Otherwise the kernel Oopses as below:
>
> [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
On Mon, 5 Sep 2022 11:38:25 +0200, Christophe Leroy wrote:
> update_mmu_cache() voids when hash page tables are not used.
> On PPC32 that means when MMU_FTR_HPTE_TABLE is not defined.
> On PPC64 that means when RADIX is enabled.
>
> Rename core part of update_mmu_cache() as __update_mmu_cache()
>
On Wed, 7 Sep 2022 11:34:44 +0200, Christophe Leroy wrote:
> linux/hugetlb.h has a fallback pgd_huge() macro for when
> pgd_huge is not defined.
>
> Remove the powerpc redundant definitions.
>
>
Applied to powerpc/next.
[1/2] powerpc/nohash: Remove pgd_huge() stub
On Thu, 25 Aug 2022 07:26:57 +, cgel@gmail.com wrote:
> From: ye xingchen
>
> Return the value vas_register_coproc_api() directly instead of storing it
> in another redundant variable.
>
>
Applied to powerpc/next.
[1/1] powerpc/pseries/vas: Remove the unneeded result variable
On Thu, 8 Sep 2022 12:54:40 +0530, Aneesh Kumar K.V wrote:
> Powerpc architecture supports 16GB hugetlb pages with hash translation. For 4K
> page size, this is implemented as a hugepage directory entry at PGD level and
> for 64K it is implemented as a huge page pte at PUD level
>
> With 16GB
On Mon, 4 Jul 2022 12:08:51 +0530, Aneesh Kumar K.V wrote:
> For both CONFIG_NUMA enabled/disabled use mem_topology_setup to
> update max/min_low_pfn.
>
> This also add min_low_pfn update to CONFIG_NUMA which was initialized
> to zero before.
>
>
> [...]
Applied to powerpc/next.
[1/1]
On Tue, 6 Sep 2022 07:20:06 +, cgel@gmail.com wrote:
> From: ye xingchen
>
> Return the value opal_npu_spa_clear_cache() directly instead of storing
> it in another redundant variable.
>
>
Applied to powerpc/next.
[1/1] ocxl: Remove the unneeded result variable
On Wed, 21 Sep 2022 20:22:53 +0530, Athira Rajeev wrote:
> For PERF_SAMPLE_BRANCH_STACK sample type, different branch_sample_type
> ie branch filters are supported. The branch filters are requested via
> event attribute "branch_sample_type". Multiple branch filters can be
> passed in event
On Wed, 7 Sep 2022 13:49:41 +0530, Aneesh Kumar K.V wrote:
> This function does the hash page table update. Hence rename it to
> indicate this better to avoid confusion with flush_pmd_tlb_range()
>
>
Applied to powerpc/next.
[1/1] powerpc/mm/book3s/hash: Rename flush_tlb_pmd_range
On Tue, 16 Aug 2022 19:25:17 -0300, Fabiano Rosas wrote:
> We used to have a workaround[1] for a hang during migration that was
> made ineffective when we converted the decrementer expiry to be
> relative to guest timebase.
>
> The point of the workaround was that in the absence of an explicit
>
"Sven Peter" writes:
> On Sun, Oct 2, 2022, at 16:07, Arminder Singh wrote:
>> Hi,
>>
>>> #define REG_MTXFIFO0x00
>>> #define REG_MRXFIFO0x04
>>> #define REG_SMSTA 0x14
>>> +#define REG_IMASK 0x18
>>
>>> This doesn't seem to be aligned correctly, this file seems to use a tab
"Arnd Bergmann" writes:
> On Wed, Sep 28, 2022, at 2:15 PM, Michael Ellerman wrote:
>
>> But I think it makes more sense to do the same as mmap2() and pass the
>> 4K offset through, and pass shift = PAGE_SHIFT - 12. I also borrowed the
>> "off_4k&quo
Lukas Bulwahn writes:
> On Fri, Sep 30, 2022 at 9:42 AM Michael Ellerman wrote:
>>
>> Lukas Bulwahn writes:
>> > Clean up config files by:
>> > - removing configs that were deleted in the past
>> > - removing configs not in tree and without re
Michal Suchánek writes:
> On Thu, Sep 29, 2022 at 05:16:40PM -0500, Nathan Lynch wrote:
>> Haren Myneni writes:
>> > Generally the hypervisor decides to allocate a window on different
>> > VAS instances. But if the user space wishes to allocate on the
>> > current VAS instance where the process
re running under PowerVM.
Failing that look for "ibm,fw-net-version" which is seen on PowerVM
going back to at least Power6.
eg: Hardware name: ... of:IBM,FW860.42 (SV860_138) hv:phyp
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 30 ++
Add OPAL version details to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 22 ++
1 file changed, 22 insertions(+)
v3: Drop quotes
Add the PVR and CPU name to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... POWER8E (raw) 0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4
1 file changed, 4 insertions(+)
v3: Drop "cpu:" and &
ed by qemu) POWER9 (raw) 0x4e1200 0xf05
of:SLOF,git-5b4c5a pSeries
printk: bootconsole [udbg0] enabled
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup-common.c | 19 ++-
2 files changed, 20 insertions(+), 1 deletion(-)
If we detect a logical PVR add that to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: ... 0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
v3: Drop "lpvr:
Add the model of the machine we're on to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: IBM,8247-22L
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
v3: Drop "model:
Lukas Bulwahn writes:
> Clean up config files by:
> - removing configs that were deleted in the past
> - removing configs not in tree and without recently pending patches
> - adding new configs that are replacements for old configs in the file
>
> For some detailed information, see Link.
>
Christophe Leroy writes:
> Le 01/09/2022 à 10:54, ruanjinjie a écrit :
>> [Vous ne recevez pas souvent de courriers de ruanjin...@huawei.com.
>> Découvrez pourquoi ceci est important à
>> https://aka.ms/LearnAboutSenderIdentification ]
>>
>> When build Linux kernel, encounter the following
Nathan Lynch writes:
> Michael Ellerman writes:
>
>> Add firmware version details to the dump stack arch description, which
>> is printed in case of an oops.
>>
>> Currently /hypervisor only exists on KVM, so if we don't find that
>> look for something t
Nathan Lynch writes:
> Michael Ellerman writes:
>> Create a hardware description string, which we will use to record
>> various details of the hardware platform we are running on.
>>
>> Print the accumulated description at boot, and use it to set the generic
>
Nathan Lynch writes:
> Michael Ellerman writes:
>> Add firmware version details to the hardware description, which is
>> printed at boot and in case of an oops.
>>
>> Use /hypervisor if we find it, though currently it only exists if we're
>> running under
Matthew Wilcox writes:
> On Tue, Sep 27, 2022 at 09:17:20AM +0800, Zorro Lang wrote:
>> Hi mm and ppc list,
>>
>> Recently I started to hit a kernel panic [2] rarely on *ppc64le* with *1k
>> blocksize* ext4. It's not easy to reproduce, but still has chance to trigger
>> by loop running
re running under PowerVM.
Failing that look for "ibm,fw-net-version" which is seen on PowerVM
going back to at least Power6.
eg: Hardware name: ... of:'IBM,FW860.42 (SV860_138)' hv:'phyp'
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 30 ++
Add OPAL version details to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 22 ++
1 file changed, 22 insertions(+)
v2: Use
Add the model of the machine we're on to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: model:'IBM,8247-22L'
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
diff --git
If we detect a logical PVR add that to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: ... lpvr:0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch
Add the PVR and CPU name to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... cpu:'POWER8E (raw)' pvr:0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc
(emulated by qemu)' cpu:'POWER8 (raw)'
pvr:0x4d0200 lpvr:0xf04 of:'SLOF,HEAD' machine:pSeries
printk: bootconsole [udbg0] enabled
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup-common.c | 19 ++-
2 files changed, 20
Michael Ellerman writes:
> Create a hardware description string, which we will use to record
> various details of the hardware platform we are running on.
>
> Print the accumulated description at boot, and use it to set the generic
> description which is printed in oopses.
>
&
Add OPAL version details to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 22 ++
1 file changed, 22 insertions(+)
v2: Use
(emulated by qemu)' cpu:'POWER8 (raw)'
pvr:0x4d0200 lpvr:0xf04 of:'SLOF,HEAD' machine:pSeries
printk: bootconsole [udbg0] enabled
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup-common.c | 19 ++-
2 files changed, 20
Add the PVR and CPU name to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... cpu:'POWER8E (raw)' pvr:0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc
re running under PowerVM.
Failing that look for "ibm,fw-net-version" which is seen on PowerVM
going back to at least Power6.
eg: Hardware name: ... of:'IBM,FW860.42 (SV860_138)' hv:'phyp'
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 30 ++
If we detect a logical PVR add that to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: ... lpvr:0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch
Add the model of the machine we're on to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: model:'IBM,8247-22L'
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
diff --git
Arnaldo Carvalho de Melo writes:
> Em Wed, Sep 21, 2022 at 08:22:54PM +0530, Athira Rajeev escreveu:
>> commit b55878c90ab9 ("perf test: Add test for branch stack sampling")
>> added test for branch stack sampling. There is a sanity check in the
>> beginning to skip the test if the hardware
Make sure the ultravisor code at least gets some build testing by
enabling it in powernv_defconfig.
Signed-off-by: Michael Ellerman
---
arch/powerpc/configs/powernv_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/configs/powernv_defconfig
b/arch/powerpc/configs
Alistair Popple writes:
> Michael Ellerman writes:
>> Alistair Popple writes:
>>> When the CPU tries to access a device private page the migrate_to_ram()
>>> callback associated with the pgmap for the page is called. However no
>>> reference is taken on the f
Alistair Popple writes:
> When the CPU tries to access a device private page the migrate_to_ram()
> callback associated with the pgmap for the page is called. However no
> reference is taken on the faulting page. Therefore a concurrent
> migration of the device private page can free the page and
-version
seems to be a full path so is too long to add to the description.
eg: Hardware name: ... of:'IBM,FW860.42 (SV860_138)' hv:phyp
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 36 ++
1 file changed, 36 insertions(+)
diff --git a/arch
Add the PVR and CPU name to the dump stack arch description, which is
printed in case of an oops.
eg: Hardware name: ... POWER8E (raw) pvr:0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/kernel/prom.c
Add OPAL version details to the dump stack arch description, which is
printed in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/arch
As soon as we know the name of the machine description we're using,
add it to the dump stack arch description, which is printed in case of
an oops.
eg: Hardware name: ... machine:pSeries
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup
Add the model of the machine we're on to the dump stack arch
description, which is printed in case of an oops.
eg: Hardware name: model:'IBM,8247-22L'
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch
If we detect a logical PVR add that to the dump stack arch
description, which is printed in case of an oops.
eg: Hardware name: ... lpvr:0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc
No toolchain we support should be generating stabs debug information
anymore. Drop the sections entirely from our linker scripts.
We removed all the manual stabs annotations in commit
12318163737c ("powerpc/32: Remove remaining .stabs annotations").
Signed-off-by: Michael Ellerman
The bulk of this was moved/reworded in:
57f266497d81 ("powerpc: Use gas sections for arranging exception vectors")
And now appears around line 700 in arch/powerpc/kernel/exceptions-64s.S.
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/exceptions-64s.S | 10 --
1 fi
This used to be about the 0x4300 handler, but that was moved in commit
da2bc4644c75 ("powerpc/64s: Add new exception vector macros").
Note that "STAB" here refers to "Segment Table" not the debug format.
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/
1501 - 1600 of 15001 matches
Mail list logo
