On Fri, Jan 31, 2014 at 11:07:22AM +0100, Borislav Petkov wrote: > On Thu, Jan 30, 2014 at 02:23:46PM -0800, H. Peter Anvin wrote: > > On 01/30/2014 02:19 PM, Alex Thorlton wrote: > > > > > > The quick answer is I think it is a virtual address, because it does > > > not work in physical mode. If you ever see "virtefi" on the RHEL > > > bootline it is because RH switched the default to physical mode, > > > which caused UV to not boot. "virtefi" forced it back to virtual > > > mode. > > > > > That is interesting, as it is definitely not the direction we have been > > going in within the Linux community. > > Right, for the new scheme to work, we'll have to map the region > containing the code for uv_systab->function in order to do all those > uv_bios_call()'s. Physical/virtual shouldn't matter all that much > because we map the region *both* as a 1:1 map and in virtual space too. > > Can SGI please give us a reliable way to do that during boot? I'm not sure what you are asking for. We had a reliable way to boot before the recent patch broke it. (commit d2f7cbe7b26a74dbbbf8f325b2a6fd01bc34032c) -- Russ Anderson, Kernel and Performance Software Team Manager SGI - Silicon Graphics Inc rja@xxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
