From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH v2 10/13] x86/PMU: Add support for PMU registes handling on PV guests Date: Wed, 25 Sep 2013 11:03:21 -0400 Message-ID: <5242FB39.6010907@oracle.com> References: <1379670132-1748-1-git-send-email-boris.ostrovsky@oracle.com> <1379670132-1748-11-git-send-email-boris.ostrovsky@oracle.com> <52430E1702000078000F64F1@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VOqac-0007Na-Ea for xen-devel@lists.xenproject.org; Wed, 25 Sep 2013 15:01:18 +0000 In-Reply-To: <52430E1702000078000F64F1@nat28.tlf.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: suravee.suthikulpanit@amd.com, George.Dunlap@eu.citrix.com, jacob.shin@amd.com, eddie.dong@intel.com, dietmar.hahn@ts.fujitsu.com, jun.nakajima@intel.com, xen-devel List-Id: xen-devel@lists.xenproject.org On 09/25/2013 10:23 AM, Jan Beulich wrote: >>>> On 20.09.13 at 11:42, Boris Ostrovsky wrote: >> Intercept accesses to PMU MSRs and LVTPC APIC vector (only >> APIC_LVT_MASKED bit is processed) and process them in VPMU >> module. > Having scrolled through this more than once, I still can't see where > any APIC interception is happening here. It's not. This commit message is a a leftover from pre-v1 implementation. LVTPC is now updated via an explicit hypercall. >> @@ -2574,6 +2587,24 @@ static int emulate_privileged_op(struct cpu_user_regs *regs) >> regs->eax = (uint32_t)msr_content; >> regs->edx = (uint32_t)(msr_content >> 32); >> break; >> + case MSR_IA32_PERF_CAPABILITIES: >> + if ( rdmsr_safe(regs->ecx, msr_content) ) >> + goto fail; >> + /* Full-Width Writes not supported */ >> + regs->eax = (uint32_t)msr_content & ~(1 << 13); >> + regs->edx = (uint32_t)(msr_content >> 32); > Rather than black listing, please white list know good features > here. This 'case' is gone after I rebased to latest sources (we implement full-width writes now). -boris