linux-kernel - Re: [PATCH] efi: Retain boot service code until after switching to virtual mode

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] [day] [month] [year] [list]

Message-ID: <20110519203308.GA2106@srcf.ucam.org>
Date:	Thu, 19 May 2011 21:33:08 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	linux-kernel@...r.kernel.org, x86@...rnel.org, hpa@...or.com,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] efi: Retain boot service code until after switching to
 virtual mode

On Thu, May 19, 2011 at 01:26:27PM -0700, Yinghai Lu wrote:

> how many entries are listed in memmap?

So far I've been seeing about 20 boot services entries at most.

> Did you test this system that have lots of those entries ? like > 128?

Do any exist?

> because efi_init() is called before memblock_x86_fill(), that means
> memblock array for reserved can not be doubled yet. --- no usable
> entries in memblock array for ram.

Mm. I guess this can be shifted later.

> > +        * get rid of it all at this point
> > +        */
> > +       free_efi_boot_services();
> > +
> 
> No, at that point memblock is not used any more.  after mm_init()/mem_init()
> 
> need to use free_bootmem_late() in free_efi_boot_services

Ah, ok.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/