From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= Subject: Re: [PATCH RFC v2 1/3] xen/pvh: enable mmu_update hypercall Date: Thu, 2 Apr 2015 13:37:26 +0200 Message-ID: <551D29F6.5090702@citrix.com> References: <1427970395-16203-1-git-send-email-roger.pau@citrix.com> <1427970395-16203-2-git-send-email-roger.pau@citrix.com> <1427971327.4037.40.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YddRE-0001hi-1M for xen-devel@lists.xenproject.org; Thu, 02 Apr 2015 11:37:32 +0000 In-Reply-To: <1427971327.4037.40.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel@lists.xenproject.org, Tim Deegan , Jan Beulich , Andrew Cooper List-Id: xen-devel@lists.xenproject.org El 02/04/15 a les 12.42, Ian Campbell ha escrit: > On Thu, 2015-04-02 at 12:26 +0200, Roger Pau Monne wrote: >> This is needed for performing save/restore of PV guests. > > It's quite a big interface though, isn't it? AFAICT it contains MMU_NORMAL_PT_UPDATE, MMU_PT_UPDATE_PRESERVE_AD and MMU_MACHPHYS_UPDATE. > Could we restrict it to a subset of the operations perhaps? Or at least > justify here how it has been audited and found to be safe to allow an > HVM guest this access. XSA-109 should have fixed all issues with this operations. IIRC only MMU_MACHPHYS_UPDATE is needed for save/restore of PV guests, but I will have to check. If that's the case, I could restrict PVH domains to only have access to that operation. Roger.