From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH for-xen-4.5] x86/pvh/vpmu: Disable VPMU for PVH guests Date: Tue, 25 Nov 2014 11:19:11 -0500 Message-ID: <5474ABFF.1030306@oracle.com> References: <1416858554-1817-1-git-send-email-boris.ostrovsky@oracle.com> <54744FB2020000780004A935@mail.emea.novell.com> <54749466.1020907@oracle.com> <5474A666020000780004AB9C@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5474A666020000780004AB9C@mail.emea.novell.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: Jan Beulich Cc: keir@xen.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 11/25/2014 09:55 AM, Jan Beulich wrote: > >> Regardless, do you think that disabling VPMU for PVH is worth anyway? > That depends on what (bad) consequences not doing so has. I haven't seen anything (besides VAPIC accesses) but I think it would be prudent to prevent any VPMU activity from happening. I can see, for example MSRs and APIC vector being written. All of which look benign on the first sight but who knows... -boris