From: Jes Sorensen <jes@sgi.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: EFI image - SAL_DESC_PLATFORM_FEATURE bits
Date: Wed, 28 Jan 2009 09:50:41 +0000 [thread overview]
Message-ID: <49802A71.7010802@sgi.com> (raw)
In-Reply-To: <497F2BDD.7030307@sgi.com>
Tristan Gingold wrote:
> On Tue, Jan 27, 2009 at 04:44:29PM +0100, Jes Sorensen wrote:
>> So my question is how your EFI image builds the sys_entry table? Is it
>> possible for KVM/Xen etc. to pass down information that the system clock
>> drifts or does it need to be hardcoded in the image? If the latter, do
>> you have any pointers to how one goes about rebuilding the image?
>
> The SAL system table is built in edk2-sparse/EdkXenPkg/Dxe/XenSal/XenSal.c.
> There is currently no platform features entry but it is easy to add one.
> I suppose this entry can be populated by using an hypercall.
>
> There is a README that explains how to build the firmware - it's tedious.
Hi Tristan,
Thanks for the info - where do I find the firmware? Is it in the Xen
hg repositories?
I was hoping it would be a walk in the park to build, but I kinda feared
you would say that. Do I need a special environment to build it, like a
special pre-historic version of GCC running on RHEL 3 or something like
that?
Cheers,
Jes
next prev parent reply other threads:[~2009-01-28 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 15:44 EFI image - SAL_DESC_PLATFORM_FEATURE bits Jes Sorensen
2009-01-28 9:19 ` Tristan Gingold
2009-01-28 9:50 ` Jes Sorensen [this message]
2009-01-28 10:14 ` Tristan Gingold
2009-01-28 10:22 ` Jes Sorensen
2009-01-28 10:33 ` Tristan Gingold
2009-01-28 14:28 ` Jes Sorensen
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=49802A71.7010802@sgi.com \
--to=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox