[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: UEFI support in ARM DomUs
- To: Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien.grall.oss@xxxxxxxxx>
- From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@xxxxxxxx>
- Date: Mon, 22 Jun 2020 14:33:53 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=epam.com; dmarc=pass action=none header.from=epam.com; dkim=pass header.d=epam.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=W1MVAF7AYJDnpBfewUOntEO3RdJbQ5xhbYNZrtFpTLE=; b=DlTU4pOBGsNvoRQVuA9Ix7pbcSuJvbGv5eopP08VLV6pEXzqGfaqx2epKX2WEaqaRn32+OpqW0E4zsIghNg5X4zDnCYJazi3QFxNSmXqIoT/r84T6d15Yx2JJAUA5XDLlsihjCEZOtKHWC/hW0736rtKybR1SU1lH3eHY83v1HqeyDKbgKdG78SUDTegE+5PNdkleEZPZi4cln/hFUdWr0MSlAEI+XhzMmq7tXxNtGqMxcCoDIg5by5k+4DNc0rw2lX772k4hH3/IS8T5/unL26hZfbgWtA11/fg3BigTovgysB+ZYAsQd41geciq+LMMLQ82eZFVnY112SGd4iTvw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DOo85M+L+9z5oyyd+xwWwrJlMdVud17kCNV26VKYBVJkUImd0WCvTT+a6pRmsnuVcb8BozPLJ+nq2Ubp6t3uydFbVVXsI04S2sBqDWs8jadYxUSd4lC7JN9R+H/DUdFnwa5RXaCq0f8aN/aiUDgXDJxu8RcK8N6oFgUIXf3J1IFlV32wrh6kT4HYAjQ5aeOz3r4bPwLbeGxNl3RMRgCRTjVDiIklen+h2/G8eogCG9O6AeDgJnx/LeE0WM2yvTMeMqspLTAwmEgTF510c2jMDAsKlx/HVvhgPAtucczvzXlgAtxm3HtID10RkQ4Xic8t/WcQoYUrzn62i5NKn2SBQA==
- Authentication-results: xen.org; dkim=none (message not signed) header.d=none;xen.org; dmarc=none action=none header.from=epam.com;
- Cc: Anastasiia Lukianenko <Anastasiia_Lukianenko@xxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Peng Fan <peng.fan@xxxxxxx>, Oleksandr Andrushchenko <andr2000@xxxxxxxxx>, Roman Shaposhnik <roman@xxxxxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Nataliya Korovkina <malus.brandywine@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Mon, 22 Jun 2020 14:34:10 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHWOoSI1wnhumD+IkWBnAQX9mudyajIlWsAgBVWbwCAAJ62gIAAeBOAgAANxQCAAWPDgIAEUtgAgAAGgYCAAAHAgA==
- Thread-topic: UEFI support in ARM DomUs
On 6/22/20 5:27 PM, Julien Grall wrote:
> Hi Oleksandr,
>
> On 22/06/2020 15:04, Oleksandr Andrushchenko wrote:
>> On 6/19/20 11:02 PM, Stefano Stabellini wrote:
>>> On Thu, 18 Jun 2020, Julien Grall wrote:
>> ifeq ($(CONFIG_XEN),y)
>> arch-y += -D__XEN_INTERFACE_VERSION__=0x00040d00
>> endif
>>
>> and we also have Xen 4.13 headers in the U-boot tree.
>
> Sorry if this was already asked before. Why do you need to specify
> __XEN_INTERFACE_VERSION__?
This is because of include/xen/interface/xen-compat.h:
#if defined(__XEN__) || defined(__XEN_TOOLS__)
/* Xen is built with matching headers and implements the latest interface. */
#define __XEN_INTERFACE_VERSION__ __XEN_LATEST_INTERFACE_VERSION__
#elif !defined(__XEN_INTERFACE_VERSION__)
/* Guests which do not specify a version get the legacy interface. */
#define __XEN_INTERFACE_VERSION__ 0x00000000
#endif
So, one needs to specify the version (QEMU does that via its configure script
after
some tests)
>
>>
>> For the first part (__XEN_INTERFACE_VERSION__) I think we can provide it via
>>
>> CFLAGS or something. This can also be done for the location of Xen headers.
>
> __XEN_INTERFACE_VERSION__ should work through the CFLAGS. An alternative
> would be to allow the user to specify through the Kconfig.
You mean specifying via Kconfig something like "0x00040d00"?
And what about the headers? How will we provide their location if we decide not
to include those
in the tree?
> Cheers,
>
|
