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

From: David Vrabel
Date: Mon Jun 23 2014 - 05:53:15 EST

Next message: Vincent Guittot: "Re: [PATCH v3 3/3] clocksource: exynos_mct: Only use 32-bits where possible"
Previous message: Vlastimil Babka: "Re: [PATCH v3 01/13] mm, THP: don't hold mmap_sem in khugepaged when allocating THP"
In reply to: Daniel Kiper: "[PATCH v6 2/9] arch/x86: Do not access EFI memory map if it is not available"
Next in thread: Jan Beulich: "Re: [PATCH v6 2/9] arch/x86: Do not access EFI memory map if it is not available"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Vincent Guittot: "Re: [PATCH v3 3/3] clocksource: exynos_mct: Only use 32-bits where possible"
Previous message: Vlastimil Babka: "Re: [PATCH v3 01/13] mm, THP: don't hold mmap_sem in khugepaged when allocating THP"
In reply to: Daniel Kiper: "[PATCH v6 2/9] arch/x86: Do not access EFI memory map if it is not available"
Next in thread: Jan Beulich: "Re: [PATCH v6 2/9] arch/x86: Do not access EFI memory map if it is not available"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]