From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ed White Subject: Re: [PATCH 09/11] x86/altp2m: define and implement alternate p2m HVMOP types. Date: Thu, 15 Jan 2015 12:43:17 -0800 Message-ID: <54B82665.5030205@intel.com> References: <1420838801-11704-1-git-send-email-edmund.h.white@intel.com> <1420838801-11704-10-git-send-email-edmund.h.white@intel.com> <20150115170951.GH57240@deinos.phlegethon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150115170951.GH57240@deinos.phlegethon.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tim Deegan Cc: keir@xen.org, ian.jackson@eu.citrix.com, ian.campbell@citrix.com, jbeulich@suse.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 01/15/2015 09:09 AM, Tim Deegan wrote: > Hi, > > These _definitely_ need XSM checks, otherwise any domain can call them > on any other! I think you can probably copy the other p2m-munging > operations to see how to make a sensible default policy. Understood. I'll look at this subject again, but it's an area where I could really use some help. There aren't any similar hypercalls that I could find where the target domain and source domain may or may not be the same, and the processing required varies depending on which is the case. Ed