From: David Vrabel <david.vrabel@citrix.com>
To: Daniel Kiper <daniel.kiper@oracle.com>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>, <xen-devel@lists.xenproject.org>
Cc: <boris.ostrovsky@oracle.com>, <eshelton@pobox.com>,
<hpa@zytor.com>, <ian.campbell@citrix.com>, <jbeulich@suse.com>,
<jeremy@goop.org>, <konrad.wilk@oracle.com>,
<matt.fleming@intel.com>, <mingo@redhat.com>,
<mjg59@srcf.ucam.org>, <stefano.stabellini@eu.citrix.com>,
<tglx@linutronix.de>
Subject: Re: [PATCH v4 0/5] xen: Add EFI support
Date: Mon, 19 May 2014 16:53:28 +0100 [thread overview]
Message-ID: <537A28F8.4030707@citrix.com> (raw)
In-Reply-To: <1400272904-31121-1-git-send-email-daniel.kiper@oracle.com>
On 16/05/14 21:41, Daniel Kiper wrote:
> Hey,
>
> This patch series adds EFI support for Xen dom0 guests.
> It is based on Jan Beulich and Tang Liang work. I was
> trying to take into account all previous comments,
> however, if I missed something sorry for that.
There needs to be a better description of this series. In particular, a
description of why Xen PV guests are different and the overall design used.
> I am still not sure what to do with /sys/firmware/efi/config_table,
> /sys/firmware/efi/{fw_vendor,runtime,systab} files. On bare metal
> they contain physical addresses of relevant structures. However,
> in Xen case they does not make sens. So maybe they should contain
> invalid values (e.g. 0) or should not appear at all on Xen (I prefer
> last one). What do you think about that?
Generally, dom0 has provided access to BIOS provided data structures. I
think you should do the same here. They may be useful for diagnostics
if nothing else.
David
prev parent reply other threads:[~2014-05-19 15:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 20:41 [PATCH v4 0/5] xen: Add EFI support Daniel Kiper
2014-05-16 20:41 ` [PATCH v4 1/5] efi: Introduce EFI_DIRECT flag Daniel Kiper
2014-05-19 13:30 ` Jan Beulich
2014-05-19 20:46 ` Daniel Kiper
2014-05-20 6:16 ` Jan Beulich
2014-05-19 15:58 ` David Vrabel
2014-05-19 21:02 ` Daniel Kiper
2014-05-22 7:26 ` Matt Fleming
2014-05-16 20:41 ` [PATCH v4 2/5] xen: Define EFI related stuff Daniel Kiper
2014-05-19 16:00 ` David Vrabel
2014-05-16 20:41 ` [PATCH v4 3/5] xen: Put EFI machinery in place Daniel Kiper
2014-05-19 13:39 ` [Xen-devel] " Andrew Cooper
2014-05-19 13:47 ` Jan Beulich
2014-05-19 13:43 ` Jan Beulich
2014-05-20 9:47 ` David Vrabel
2014-05-20 11:29 ` Daniel Kiper
2014-05-20 11:58 ` Jan Beulich
2014-05-20 12:10 ` David Vrabel
2014-05-16 20:41 ` [PATCH v4 4/5] arch/x86: Replace plain strings with constants Daniel Kiper
2014-05-22 7:56 ` Matt Fleming
2014-05-16 20:41 ` [PATCH v4 5/5] arch/x86: Remove redundant set_bit() call Daniel Kiper
2014-05-22 7:59 ` Matt Fleming
2014-05-19 15:53 ` David Vrabel [this message]
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=537A28F8.4030707@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=eshelton@pobox.com \
--cc=hpa@zytor.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox