From mboxrd@z Thu Jan  1 00:00:00 1970
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v12 for-xen-4.5 16/20] x86/VPMU: Handle PMU
 interrupts for PV guests
Date: Thu, 02 Oct 2014 09:53:09 -0400
Message-ID: <542D58C5.8030707@oracle.com>
References: <1411673336-32736-1-git-send-email-boris.ostrovsky@oracle.com>
	<1411673336-32736-17-git-send-email-boris.ostrovsky@oracle.com>
	<542A81B6020000780003ADD4@mail.emea.novell.com>
	<542AC71C.6020804@oracle.com>
	<542AEC00020000780003B224@mail.emea.novell.com>
	<542ADC57.1070708@oracle.com>
	<542BC00A020000780003B510@mail.emea.novell.com>
	<542BF93E.7040505@oracle.com>
	<542C1B30020000780003B901@mail.emea.novell.com>
	<542C0AE0.9080203@oracle.com>
	<542C2B4C020000780003B9C2@mail.emea.novell.com>
	<542C42BA.4050700@oracle.com>
	<542D1327020000780003BCA9@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <542D1327020000780003BCA9@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, keir@xen.org, suravee.suthikulpanit@amd.com, andrew.cooper3@citrix.com, tim@xen.org, dietmar.hahn@ts.fujitsu.com, xen-devel@lists.xen.org, Aravind.Gopalakrishnan@amd.com, jun.nakajima@intel.com, dgdegra@tycho.nsa.gov
List-Id: xen-devel@lists.xenproject.org

On 10/02/2014 02:56 AM, Jan Beulich wrote:
>
> And in the end, considering that a model where there's both a
> local and a global profiler active, one sample referring to
> hypervisor context could easily result in two events: One
> (with the hypervisor register state) to the global profiled, and
> a second (with the surrounding guest register state) to the
> guest one. But iiuc your current implementation doesn't allow
> that (yet).

Right, it doesn't.

And I don't think this will work since PMU registers need to be 
controlled by one domain only (either dom0 or the guest) for each 
profiling session. If we send the interrupt to both one of them will 
likely get confused about why it is getting the interrupt that it didn't 
request.

-boris