<pie_>
damn lol looks like they used bluespec for some stuff?
<pie_>
3.2.3. BUILDING THE ACM BLUESPEC FPGA MODEL OF A POWER PC SERVER PROCESSOR ........................................................................................................... 9
<qyliss>
multi: > A new ISA release will include the PEF RFC02487 changes.
<qyliss>
So I assume not currently
<Shell>
"This firmware, which we refer to as the Ultravisor, will be open sourced to provide increased transparency and to allow the community to review and strengthen its security." yay!
<pie_>
qyliss: huh. havent seen this before.
<qyliss>
Although, who knows when the documentation was written
<hyperfekt>
'ultravisor' sounds pretty cool but essentially this is hypervisor nesting iiuc?
<pie_>
3.2.3.BUILDING THE ACM BLUESPEC FPGA MODEL OF A POWER PC SERVER PROCESSOR This approach was done by modifying an existing Bluespec PowerPCserver class processor model. A demonstration was run on a Verilog simulator and was shown atthe DHS S&T PI meeting in December 2014. The architecture of the ACM Bluespec model isshown in Figure 3.
<pie_>
i wonder if bluespec was still haskell in 2014
<hyperfekt>
so essentially the question if this is good or bad rests on your opinion of the ultravisor firmware?
<qyliss>
hyperfekt: well, my understanding is that the ultravisor does less
<hyperfekt>
qyliss: Ah yes, on second read. I like the concept. Just unfortunate that there's only a single trust domain apparently? And what's the difference to stuff like AMD SEV and Intel TME?