From: Michael Ellerman <mpe@ellerman.id.au>
To: Nathan Lynch <nathanl@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 6/6] powerpc/pseries: Add firmware details to the hardware description
Date: Fri, 30 Sep 2022 12:06:39 +1000 [thread overview]
Message-ID: <87tu4pehu8.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87zgehbznb.fsf@linux.ibm.com>
Nathan Lynch <nathanl@linux.ibm.com> writes:
> Michael Ellerman <mpe@ellerman.id.au> 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 qemu.
>>
>> Look for "ibm,powervm-partition" which is specified in PAPR+ v2.11 and
>> tells us we'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 <mpe@ellerman.id.au>
>> ---
>> arch/powerpc/platforms/pseries/setup.c | 30 ++++++++++++++++++++++++++
>> 1 file changed, 30 insertions(+)
>>
>> v2: Look for "ibm,powervm-partition" as suggested by Nathan.
>> Use of_property_read_string().
>
> LGTM.
>
> I noticed that we don't get an "of:" report with qemu+vof, because there's no
> /openprom node.
>
> $ qemu-system-ppc64 -nographic -vga none -M pseries,x-vof=off -kernel vmlinux | grep Hardware
> Hardware name: model:'IBM pSeries (emulated by qemu)' cpu:'POWER9 (raw)' pvr:0x4e1200 lpvr:0xf000005 of:'SLOF,HEAD' machine:pSeries
> $ qemu-system-ppc64 -nographic -vga none -M pseries,x-vof=on -kernel vmlinux | grep Hardware
> Hardware name: model:'IBM pSeries (emulated by qemu)' cpu:'POWER9 (raw)' pvr:0x4e1200 lpvr:0xf000005 machine:pSeries
> $ qemu-system-ppc64 --version
> QEMU emulator version 7.0.0 (qemu-7.0.0-6.fc36)
>
> I didn't see anything in the vof device tree that would help though.
OK. We don't boot via prom_init when booting with vof, so in that sense
there is no OF.
I think the combo of seeing qemu but no "of" is sufficient to recognise
that case.
cheers
next prev parent reply other threads:[~2022-09-30 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 14:22 [PATCH v2 1/6] powerpc: Add hardware description string Michael Ellerman
2022-09-29 14:22 ` [PATCH v2 2/6] powerpc: Add PVR & CPU name to hardware description Michael Ellerman
2022-09-29 14:22 ` [PATCH v2 3/6] powerpc/64: Add logical PVR to the " Michael Ellerman
2022-09-29 14:22 ` [PATCH v2 4/6] powerpc: Add device-tree model " Michael Ellerman
2022-09-29 14:22 ` [PATCH v2 5/6] powerpc/powernv: Add opal details " Michael Ellerman
2022-09-29 14:22 ` [PATCH v2 6/6] powerpc/pseries: Add firmware " Michael Ellerman
2022-09-29 22:10 ` Nathan Lynch
2022-09-30 2:06 ` Michael Ellerman [this message]
2022-09-29 22:01 ` [PATCH v2 1/6] powerpc: Add hardware description string Nathan Lynch
2022-09-30 2:13 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2022-09-29 13:59 Michael Ellerman
2022-09-29 13:59 ` [PATCH v2 6/6] powerpc/pseries: Add firmware details to the hardware description Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu4pehu8.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathanl@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox