Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1312256

Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM virtual platforms

From Shannon Zhao <shannon.zhao@linaro.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM virtual platforms
Date 2016-01-19 14:50 +0100
Message-ID <qSEPx-8d-33@gated-at.bofh.it> (permalink)
References (3 earlier) <qSlWy-3Wp-7@gated-at.bofh.it> <qSBHY-6r0-5@gated-at.bofh.it> <qSC1k-6y1-11@gated-at.bofh.it> <qSDA6-7Pd-15@gated-at.bofh.it> <qSEmv-8o1-19@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



On 2016/1/19 21:13, Mark Rutland wrote:
> On Tue, Jan 19, 2016 at 12:23:17PM +0000, Stefano Stabellini wrote:
>> >On Tue, 19 Jan 2016, Mark Rutland wrote:
>>> > >On Tue, Jan 19, 2016 at 06:25:25PM +0800, Shannon Zhao wrote:
>>>>>> > > > >>We don't do this in Documentation/arm/uefi.txt, and I don't see why we
>>>>>> > > > >>should do so here.
>>>>>> > > > >>
>>>>>> > > > >>Does Xen handle arbitrary size memory map descriptors? I'm not sure what
>>>>>> > > > >>new information might be passed in future additions to the descriptor
>>>>>> > > > >>format, and I'm not sure what should happen in the Dom0 case.
>>>>> > > > >
>>>>> > > > >Xen passes to Dom0 the memory map in the same format as the native
>>>>> > > > >memory map.
>>> > >
>>> > >Does Xen parse or modify the EFI memory map in any way?
>> >
>> >Xen:
>> >- calls EFI_BOOT_SERVICES.GetMemoryMap()
>> >- takes note of the memory regions for its own usage
>> >- create the fdt notes, including efi-mmap-start, with a pointer to it
>> >
>> >
>>> > >Does it pass the raw values returned by EFI_BOOT_SERVICES.GetMemoryMap()
>>> > >through to the xen,uefi-* properties, or does is make any static
>>> > >assumptions about what the values will be?
>> >
>> >It just passes the raw values.
> I take it that means that any memory carved out for Xen itself is
> described/discovered via a separate mechanism? How does that work

For Xen hypervisor booting on UEFI, it get the EFI memory map through 
the similar way like Linux, e.g. call EFI_BOOT_SERVICES.GetMemoryMap().
For Dom0, Xen will create a new EFI memory map for Dom0.

See [PATCH v3 52/62] arm/acpi: Prepare EFI memory descriptor for Dom0
http://lists.xen.org/archives/html/xen-devel/2015-11/msg01884.html

Thanks,
-- 
Shannon

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Mark Rutland <mark.rutland@arm.com> - 2016-01-18 12:00 +0100
  Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Stefano Stabellini <stefano.stabellini@eu.citrix.com> - 2016-01-18 18:40 +0100
    Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM virtual  platforms Shannon Zhao <zhaoshenglong@huawei.com> - 2016-01-19 11:30 +0100
      Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Mark Rutland <mark.rutland@arm.com> - 2016-01-19 11:50 +0100
        Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Stefano Stabellini <stefano.stabellini@eu.citrix.com> - 2016-01-19 13:30 +0100
          Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Ard Biesheuvel <ard.biesheuvel@linaro.org> - 2016-01-19 14:20 +0100
          Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Mark Rutland <mark.rutland@arm.com> - 2016-01-19 14:20 +0100
            Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM virtual  platforms Shannon Zhao <shannon.zhao@linaro.org> - 2016-01-19 14:50 +0100
              Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Stefano Stabellini <stefano.stabellini@eu.citrix.com> - 2016-01-19 15:20 +0100
              Re: [PATCH v2 12/16] ARM: Xen: Document UEFI support on Xen ARM  virtual platforms Mark Rutland <mark.rutland@arm.com> - 2016-01-21 13:00 +0100

csiph-web