Short answer: OBP on E25K was a source of headaches, unnecessary complexity, and instability when performing DR. We decided on an architectural change with sun4v, eliminating OBP from the DR equation, which greatly simplified the DR implementation.
-Eric On Feb 11, 2010, at 4:57 PM, Nathan Kroenert wrote: > huh? > > OBP on E25K's was always present for the adding and removal of CPU, memory, > and I/O devices... > > Not sure I see how that makes a case for removing it. ;) > > Nathan. > > > Alexandre Chartre wrote: >> That's mostly because the OBP relies on a static configuration >> initialized when the system (or a domain) is started, and it does >> not support things like dynamic reconfiguration (e.g. add/removing >> cpu while the system is running). If the OBP was kept then it >> could become out of sync compared with the actual configuration. >> alex. >> On 02/11/10 04:08, jf simon wrote: >>> Alex, >>> >>>>>> On sun4v platforms, when Solaris boots, the OBP is removed from >>>>>> the memory and you can not used it anymore when Solaris is running. >>>>>> This is done in order to properly support virtualization (with >>>>>> Logical Domains). >>> >>> BTW, why would OBP need to be removed for virtualization purposes? >>> -jfs >>> >> _______________________________________________ >> driver-discuss mailing list >> driver-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/driver-discuss > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2425 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/ldoms-discuss/attachments/20100217/062d6464/attachment.bin>
