Why was XENMEM_translate_gpfn_list removed in Xen 4.0. How to achieve similar purpose in HVM? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2010-Aug-26 07:28 UTC
Re: [Xen-devel] why was XENMEM_translate_gpfn_list removed
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_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Maybe Matching Threads
- [PATCH 4/5] xen: arm: implement remap interfaces needed for privcmd mappings.
- do_* declarations (was: Re: [Xen-ia64-devel] [PATCH] added multicall)
- Multivariate regression with constraints
- Multivariate Regression with Weights
- Resend: setting breakpoints around hypercalls in a domU causes dom0 to lockup