linux-kernel - Re: [PATCH v6 2/9] arch/x86: Do not access EFI memory map if it is not available

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]

Message-ID: <20140623141310.GI28489@olila.local.net-space.pl>
Date:	Mon, 23 Jun 2014 16:13:10 +0200
From:	Daniel Kiper <daniel.kiper@...cle.com>
To:	Jan Beulich <JBeulich@...e.com>
Cc:	David Vrabel <david.vrabel@...rix.com>, x86@...nel.org,
	xen-devel@...ts.xenproject.org, linux-efi@...r.kernel.org,
	linux-kernel@...r.kernel.org, andrew.cooper3@...rix.com,
	ian.campbell@...rix.com, stefano.stabellini@...citrix.com,
	jeremy@...p.org, matt.fleming@...el.com, tglx@...utronix.de,
	boris.ostrovsky@...cle.com, konrad.wilk@...cle.com,
	eshelton@...ox.com, mingo@...hat.com, mjg59@...f.ucam.org,
	hpa@...or.com
Subject: Re: [PATCH v6 2/9] arch/x86: Do not access EFI memory map if it is
 not available

On Mon, Jun 23, 2014 at 12:00:01PM +0100, Jan Beulich wrote:
> >>> On 23.06.14 at 11:53, <david.vrabel@...rix.com> wrote:
> > On 20/06/14 22:29, Daniel Kiper wrote:
> >> Do not access EFI memory map if it is not available. At least
> >> Xen dom0 EFI implementation does not have an access to it.
> >
> > Could it make one based on the XENMEM_memory_map or
> > XENMEM_machine_memory_map hypercall?
>
> No, the correct operation to implement this and efi_mem_type()
> similar function is XEN_FW_EFI_INFO, index XEN_FW_EFI_MEM_INFO.

efi_mem_attributes() is used only on IA-64 arch. So, that is why
I completely removed relevant Xen code.

Daniel
--
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/