Page MenuHomeFreeBSD

hardware: update pSeries entries
ClosedPublic

Authored by minsoochoo0122_proton.me on Tue, May 19, 9:51 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, May 28, 8:56 PM
Unknown Object (File)
Tue, May 26, 7:49 AM
Unknown Object (File)
Tue, May 26, 3:56 AM
Unknown Object (File)
Tue, May 26, 3:17 AM
Unknown Object (File)
Mon, May 25, 7:45 PM
Unknown Object (File)
Mon, May 25, 6:23 PM
Unknown Object (File)
Mon, May 25, 5:28 PM
Unknown Object (File)
Mon, May 25, 5:27 PM

Details

Summary

14.4 and 15.1 support little-endian pSeries.
15.0 has boot panic due to bug in SLOF, but it should be reclassified as
QEMU pSeries instead of IBM.

Signed-off-by: Minsoo Choo <minsoo@minsoo.io>

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Thanks for doing this! I'll wait for @adrian since I don't have this hardware.

I wasn't sure what "IBM: pSeries VM" meant, so I'm making an assumption here that it means QEMU pSeries.

I wasn't sure what "IBM: pSeries VM" meant, so I'm making an assumption here that it means QEMU pSeries.

I wonder if that meant PowerVM (a native hypervisor) using LPARs (logical partitions) of the real hardware. It's parts which were shared to Power from the mainframe (systemz).

Yes, iiuc, ibm pseries hardware has a hypervisor, and that's what this is talking about

The modern terminology would be PAPR. This is what qemu, PowerVM, and LPARs implement. And different than PowerNV.

The original could mean PowerVM, but that's not "hardware" so that shouldn't on this note although PowerVM is pretty consistent across different Power servers (unlike x86 and arm).

@adrian I think it would be better to make two different sections for powernv and powervm.

PowerVM is "just" an I/O server, the device model is always PAPR for "bare metal", LPAR, and PowerVM. This is the traditional OpenFirmware derived interface.

PowerNV is a separate, clean break, open source firmware available on some Power7+ systems, notably the Raptor stuff and qemu.

PowerVM is "just" an I/O server, the device model is always PAPR for "bare metal", LPAR, and PowerVM. This is the traditional OpenFirmware derived interface.

PowerNV is a separate, clean break, open source firmware available on some Power7+ systems, notably the Raptor stuff and qemu.

Then a better commit message would be "Remove pSeries VM since it is not an actual hardware and add QEMU pSeries to the list". I'm assuming pSeries VM and PowerVM are the same thing. Am I correct?

website/content/en/releases/14.4R/hardware.adoc
169–170

Power9 for IC922?

Under QEMU I would probably say "pSeries (PAPR)" just because qemu refers to that name still for launch.

And under IBM, which should be kept, with the bullet point: PAPR (native, LPAR, PowerVM)

Under QEMU I would probably say "pSeries (PAPR)" just because qemu refers to that name still for launch.

And under IBM, which should be kept, with the bullet point: PAPR (native, LPAR, PowerVM)

So you mean we can write PAPR (native, LPAR, PowerVM) without listing every single hardware like PowerNV's case (e.g IC922)?

PAPR and PowerNV are oil and water. PAPR lets you not write out every POWER4+ machine ever. PowerNV lets you not write out every raptor and some IBM and misc systems

  • hardware.adoc: remove redundant LF at end of file
  • hardware.adoc: update powerpc64 entries
This revision is now accepted and ready to land.Wed, May 20, 1:09 AM

Thank you both so much for this effort, I really appreciate this.

This revision was automatically updated to reflect the committed changes.