linux-kernel - Re: [BUG] Linux 3.14 fails to boot with new EFI changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 31 Jan 2014 11:07:22 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Alex Thorlton <athorlton@....com>,
	Matt Fleming <matt@...sole-pimps.org>,
	Russ Anderson <rja@....com>, linux-kernel@...r.kernel.org
Subject: Re: [BUG] Linux 3.14 fails to boot with new EFI changes

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?

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/