From: Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>
To: Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien.grall.oss@gmail.com>
Cc: Anastasiia Lukianenko <Anastasiia_Lukianenko@epam.com>,
Juergen Gross <jgross@suse.com>, Peng Fan <peng.fan@nxp.com>,
Oleksandr Andrushchenko <andr2000@gmail.com>,
Roman Shaposhnik <roman@zededa.com>,
Bertrand Marquis <Bertrand.Marquis@arm.com>,
Nataliya Korovkina <malus.brandywine@gmail.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: UEFI support in ARM DomUs
Date: Mon, 22 Jun 2020 14:33:53 +0000 [thread overview]
Message-ID: <4ece84cf-dd68-6eb4-a0e2-e9008d264ba5@epam.com> (raw)
In-Reply-To: <94bfe57c-c1be-62b4-3799-b90415264487@xen.org>
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,
>
next prev parent reply other threads:[~2020-06-22 14:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 22:05 UEFI support in ARM DomUs Roman Shaposhnik
2020-05-31 22:24 ` Julien Grall
2020-06-01 4:11 ` Roman Shaposhnik
2020-06-01 16:12 ` Stefano Stabellini
2020-06-02 22:50 ` Roman Shaposhnik
2020-06-04 16:58 ` George Dunlap
2020-06-03 10:16 ` Julien Grall
2020-06-04 1:57 ` Peng Fan
2020-06-04 15:26 ` Oleksandr Andrushchenko
2020-06-04 15:31 ` Stefano Stabellini
2020-06-04 16:50 ` Roman Shaposhnik
2020-06-15 1:58 ` Peng Fan
2020-06-18 5:22 ` Oleksandr Andrushchenko
2020-06-18 14:50 ` Julien Grall
2020-06-18 22:00 ` Stefano Stabellini
2020-06-18 22:49 ` Julien Grall
2020-06-19 12:32 ` Oleksandr Andrushchenko
2020-06-19 12:47 ` Julien Grall
2020-06-19 12:51 ` Oleksandr Andrushchenko
2020-06-19 12:59 ` Julien Grall
2020-06-19 13:06 ` Oleksandr Andrushchenko
2020-06-19 13:15 ` Julien Grall
2020-06-19 13:29 ` Oleksandr Andrushchenko
2020-06-22 13:56 ` Oleksandr Andrushchenko
2020-06-22 14:23 ` Julien Grall
2020-06-19 13:16 ` Peng Fan
2020-06-19 13:31 ` Oleksandr Andrushchenko
2020-06-19 20:02 ` Stefano Stabellini
2020-06-22 14:04 ` Oleksandr Andrushchenko
2020-06-22 14:27 ` Julien Grall
2020-06-22 14:33 ` Oleksandr Andrushchenko [this message]
2020-06-22 17:49 ` Julien Grall
2020-06-23 1:20 ` Stefano Stabellini
2020-06-23 5:31 ` Oleksandr Andrushchenko
2020-06-24 6:14 ` Oleksandr Andrushchenko
2020-06-24 7:07 ` Peng Fan
2020-06-24 7:17 ` Oleksandr Andrushchenko
2020-06-24 7:26 ` Peng Fan
2020-06-24 7:38 ` Oleksandr Andrushchenko
2020-06-24 17:05 ` Stefano Stabellini
2020-06-24 19:31 ` Oleksandr Andrushchenko
2020-06-24 19:47 ` Stefano Stabellini
2020-06-19 7:04 ` Oleksandr Andrushchenko
2020-06-04 15:38 ` Julien Grall
2020-06-04 16:27 ` Stefano Stabellini
2020-06-04 16:34 ` Julien Grall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ece84cf-dd68-6eb4-a0e2-e9008d264ba5@epam.com \
--to=oleksandr_andrushchenko@epam.com \
--cc=Anastasiia_Lukianenko@epam.com \
--cc=Bertrand.Marquis@arm.com \
--cc=andr2000@gmail.com \
--cc=jgross@suse.com \
--cc=julien.grall.oss@gmail.com \
--cc=julien@xen.org \
--cc=malus.brandywine@gmail.com \
--cc=peng.fan@nxp.com \
--cc=roman@zededa.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.