From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
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 <xen-devel@lists.xenproject.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v1 06/13] x86/PMU: Add public xenpmu.h
Date: Wed, 11 Sep 2013 10:03:00 -0400 [thread overview]
Message-ID: <52307814.9000109@oracle.com> (raw)
In-Reply-To: <5230424502000078000F24BC@nat28.tlf.novell.com>
On 09/11/2013 04:13 AM, Jan Beulich wrote:
>> --- /dev/null
>> +++ b/xen/include/public/xenpmu.h
> This new file is completely unacceptable as a public header.
Is this the same comment as IanC made? Mark up public interfaces for
doc generation?
Or something else?
>
>> @@ -0,0 +1,101 @@
>> +#ifndef __XEN_PUBLIC_XENPMU_H__
>> +#define __XEN_PUBLIC_XENPMU_H__
>> +
>> +#include <asm/msr.h>
> This is a no-go.
>
>> +
>> +#include "xen.h"
>> +
>> +#define XENPMU_VER_MAJ 0
>> +#define XENPMU_VER_MIN 0
>> +
>> +/* VPMU modes */
>> +#define VPMU_MODE_MASK 0xff
> All of these defines would need XEN_ prefixes (and types would
> similarly need xen_). And there ought to be some association in the
> comment to the field(s) that these constants would actually go into:
> From a cursory look I can't see this.
>
>> +#define VPMU_OFF 0
>> +/* guests can profile themselves, (dom0 profiles itself and Xen) */
> Comment style.
>
>> +#define VPMU_ON (1<<0)
>> +/*
>> + * Only dom0 has access to VPMU and it profiles everyone: itself,
>> + * the hypervisor and the guests.
>> + */
>> +#define VPMU_PRIV (1<<1)
>> +
>> +/* VPMU flags */
>> +#define VPMU_FLAGS_MASK ((uint32_t)(~VPMU_MODE_MASK))
>> +#define VPMU_INTEL_BTS (1<<8) /* Ignored on AMD */
>> +
>> +
>> +/* AMD PMU registers and structures */
>> +#define F10H_NUM_COUNTERS 4
>> +#define F15H_NUM_COUNTERS 6
>> +/* To accommodate more counters in the future (e.g. NB counters) */
>> +#define MAX_NUM_COUNTERS 16
> Perhaps better to have the number of counters in the structure?
>
>> +struct amd_vpmu_context {
>> + uint64_t counters[MAX_NUM_COUNTERS];
>> + uint64_t ctrls[MAX_NUM_COUNTERS];
>> + uint8_t msr_bitmap_set;
>> +};
>> +
>> +
>> +/* Intel PMU registers and structures */
>> +static const uint32_t core2_fix_counters_msr[] = {
> You're kidding, aren't you?
This was moved from vpmu.h. I will change it to enum (or remove altogether).
-boris
next prev parent reply other threads:[~2013-09-11 14:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 15:20 [PATCH v1 00/13] x86/PMU: Xen PMU PV support Boris Ostrovsky
2013-09-10 15:20 ` [PATCH v1 01/13] Export hypervisor symbols Boris Ostrovsky
2013-09-11 7:51 ` Jan Beulich
2013-09-11 13:55 ` Boris Ostrovsky
2013-09-11 14:12 ` Jan Beulich
2013-09-11 14:57 ` Boris Ostrovsky
2013-09-11 16:01 ` Jan Beulich
2013-09-10 15:20 ` [PATCH v1 02/13] Set VCPU's is_running flag closer to when the VCPU is dispatched Boris Ostrovsky
2013-09-11 7:58 ` Jan Beulich
2013-09-10 15:21 ` [PATCH v1 03/13] x86/PMU: Stop AMD counters when called from vpmu_save_force() Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 04/13] x86/VPMU: Minor VPMU cleanup Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 05/13] intel/VPMU: Clean up Intel VPMU code Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 06/13] x86/PMU: Add public xenpmu.h Boris Ostrovsky
2013-09-11 8:13 ` Jan Beulich
2013-09-11 14:03 ` Boris Ostrovsky [this message]
2013-09-11 14:16 ` Jan Beulich
2013-09-11 8:37 ` Ian Campbell
2013-09-10 15:21 ` [PATCH v1 07/13] x86/PMU: Make vpmu not HVM-specific Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 08/13] x86/PMU: Interface for setting PMU mode and flags Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 09/13] x86/PMU: Initialize PMU for PV guests Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 10/13] x86/PMU: Add support for PMU registes handling on " Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 11/13] x86/PMU: Handle PMU interrupts for " Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 12/13] x86/PMU: Save VPMU state for PV guests during context switch Boris Ostrovsky
2013-09-10 15:21 ` [PATCH v1 13/13] x86/PMU: Move vpmu files up from hvm directory Boris Ostrovsky
2013-09-10 15:34 ` [PATCH v1 00/13] x86/PMU: Xen PMU PV support Jan Beulich
2013-09-10 15:47 ` Boris Ostrovsky
2013-09-11 17:01 ` George Dunlap
2013-09-11 18:22 ` Boris Ostrovsky
2013-09-12 9:39 ` George Dunlap
2013-09-12 14:58 ` Boris Ostrovsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52307814.9000109@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=eddie.dong@intel.com \
--cc=jacob.shin@amd.com \
--cc=jun.nakajima@intel.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).