From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "yzhang.unc@gmail.com" <yzhang.unc@gmail.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: why was XENMEM_translate_gpfn_list removed
Date: Thu, 26 Aug 2010 08:28:14 +0100 [thread overview]
Message-ID: <C89BD61E.1F321%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1282780763.26987.3.camel@Workstation>
On 26/08/2010 00:59, "Ian Zhang" <yzhang.unc@gmail.com> wrote:
> Why was XENMEM_translate_gpfn_list removed in Xen 4.0. How to achieve
> similar purpose in HVM?
It's not needed, since all hypercalls on an HVM guest refer to guest
pseudo-physical addresses. Keeping translate_gpfn_list just encouraged lazy
programmers to design bad hypervisor interfaces.
-- Keir
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-08-26 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 23:59 why was XENMEM_translate_gpfn_list removed Ian Zhang
2010-08-26 7:28 ` Keir Fraser [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=C89BD61E.1F321%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=yzhang.unc@gmail.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).