- User Since
- Sep 10 2014, 9:01 PM (248 w, 5 d)
Sun, Jun 16
Tue, Jun 11
Feb 26 2019
Should we panic if freeze_timebase somehow doesn't get set? Or, alternately, fall back on the old lame thing?
Feb 10 2019
Jan 13 2019
Longer-term, it might be better to avoid a proliferation of special cases like this to set LOADER_MSDOS_SUPPORT for the U-boot loader and make loader flexible enough to find the kernel etc. in the root rather than /boot. But this is fine for now.
Oct 19 2018
Oct 11 2018
Aside from one inline note, this looks OK for non-SPE.
Oct 5 2018
Sep 19 2018
Sep 17 2018
Can we make the check the presence of a PHB4 node in the device tree rather than an #ifdef? It might also be best to do this in platform_powernv.c, but that's a bit larger of a project.
Aug 30 2018
Aug 29 2018
Aug 24 2018
Aug 19 2018
I just looked at the actual patch. The kernel sometimes (almost always on ppc64, less often on ppc32) relocates itself again post-loader to an address that loader does not know, so I think this does not solve the actual problem, or at least solves it in only a subset of cases. Processing these relocations in the kernel would solve the issue in all cases.
Aug 11 2018
Looks OK to me. One question: Do we want the various instances of fdt_check_header() in our code to be spelled FDT_RO_PROBE() now?
Jul 31 2018
Jul 19 2018
Since I'm not familiar with the clock code, where is EXT_RESOURCES defined? Can we just use that code unconditionally?
Jun 29 2018
Assuming you have tested this and it works, looks great.
Jun 21 2018
Looks good to me.
Jun 20 2018
Approved if you fix the #if 0 bit.
Jun 15 2018
Don't you want strcmp() == 0?
It's mildly stupid, since the universe of pci* isn't big, but I think I would prefer a check for "pci" || "pciex" to just checking the first three characters.
Jun 11 2018
Jun 5 2018
It's been another couple weeks. Any objections or approvals?
Jun 4 2018
May 30 2018
May 26 2018
This looks good to me, though I haven't tested on P8.
On POWER9, I think the lock is unnecessary (the ISA spec doesn't mention it).
May 25 2018
Any other thoughts? I'd like to get this in soon since it is blocking other things.
May 20 2018
Fix style and spelling issues in man pages.
Probe for pending devices at the end of each pass and after modules loaded. Add documentation.
See the comment on line 467 about powernv_smp_ap_init(). Otherwise, looks good.
May 19 2018
Approved if you also install it to EXC_HEA.
May 18 2018
This looks good, even if the deice tree situation is a bit lamentable. Two questions:
- Is there a document describing this that we can reference?
- If this is just part of the PowerNV platform, maybe the code belongs in platform_powernv.c instead?
May 14 2018
Thanks -- I'll tweak the implementation to handle KLDs properly and write a man page, then update this diff.
May 13 2018
Any further comments? I'd really like to get this, or something like it, in.
May 8 2018
We should do the same thing (check fdtbootcpu rather than PIR) on PowerNV too. Thanks for the work on this patch!
May 7 2018
Looks good to me. I haven't tested it, of course -- is this working well for you?
This is an interesting problem that I need to think about -- thanks for identifying it! I think this particular patch is not the right one, so let's put a pin in this for a couple days.
The CPU is stored in the device tree in one of two ways:
- As an ihandle "cpu" in /chosen
- The "fdtbootcpu" integer property from /chosen
May 6 2018
May 4 2018
May 1 2018
Apr 30 2018
Simplify logic dealing with pending attachments.
Apr 25 2018
We should fix that, too, though. This code assumes that we are booting on CPU 0 -- the same assumption could continue as a stopgap until we figure out a reliable way to evaluate the boot processor.
Apr 24 2018
Is there a reason not to just adopt the PowerNV version of this code, which already does the right thing?
Apr 23 2018
Apr 19 2018
Apr 18 2018
Apr 17 2018
This looks great, with one nit about the way you determine whether VSX is available.
Apr 5 2018
Mar 16 2018
I think there is also a subtlety for uncaught signals if the previous trap was a kernel fault, since you then end up in the wrong branch of the kernel/user if in trap() and probably crash.
Sure, it will deliver the signal. But the value of MSR when control is returned to userland may be wrong (it may even have MSR[PR] unset and return in supervisor mode if the previous trap on this CPU was in the kernel!) and it will resume execution in the wrong place if the signal is caught and handled.
Mar 15 2018
I'm looking at this again. Does this actually work? HEA interrupts set HSRR0/HSSR1, which we don't save, so I think this will jump back to some random other memory location (whatever happened to be in SRR0).
Mar 14 2018
Mar 13 2018
Use label arithmetic rather than instruction counting, which is much more robust.
Mar 11 2018
Looks good. Thanks for doing this!
Mar 7 2018
Mar 6 2018
Minor cleanups. Fix Book-E.
Mar 5 2018
Fix fault when synchronizing icache.