From: Matthew Garrett <mjg59@srcf.ucam.org>
To: liang tang <liang.tang@oracle.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, konrad.wilk@oracle.com
Subject: Re: [PATCH 3/5] EFI: add efi driver for Xen efi
Date: Fri, 10 Feb 2012 13:45:26 +0000 [thread overview]
Message-ID: <20120210134525.GA29662@srcf.ucam.org> (raw)
In-Reply-To: <4F34C622.3060905@oracle.com>
On Fri, Feb 10, 2012 at 03:24:18PM +0800, liang tang wrote:
> Hi,Matthew
> the xen efi call need to use hypercall. that is different from the
> generic efi code. do you any idea about that. thanks!
Right, but 32-bit EFI needs to make different calls to 64-bit EFI
anyway. It would be good if the abstraction could be done at this level
instead of duplicating the code.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-02-10 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 3:30 [PATCH 0/5] xen: patches for supporting efi Tang Liang
2012-02-09 3:32 ` [PATCH 1/5] EFI: Provide registration for efi_init.. etc efi public function Tang Liang
2012-02-09 16:01 ` Konrad Rzeszutek Wilk
2012-02-10 16:58 ` [Xen-devel] " Jan Beulich
2012-02-09 3:32 ` [PATCH 2/5] EFI: seperate get efi table info code to single function Tang Liang
2012-02-09 3:33 ` [PATCH 3/5] EFI: add efi driver for Xen efi Tang Liang
2012-02-09 19:47 ` Matthew Garrett
2012-02-10 7:24 ` liang tang
2012-02-10 13:45 ` Matthew Garrett [this message]
2012-02-10 15:49 ` [Xen-devel] " Jan Beulich
2012-02-09 3:33 ` [PATCH 4/5] Xen efi: Add xen efi enabled detect Tang Liang
2012-02-09 3:33 ` [PATCH 5/5] Xen vga: add the xen efi video mode support Tang Liang
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=20120210134525.GA29662@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=konrad.wilk@oracle.com \
--cc=liang.tang@oracle.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).