From: Ian Campbell <Ian.Campbell@citrix.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: keir@xen.org, stefano.stabellini@eu.citrix.com,
andrew.cooper3@citrix.com, Ian.Jackson@eu.citrix.com,
xen-devel@lists.xen.org, will.auld@intel.com, JBeulich@suse.com,
wei.liu2@citrix.com
Subject: Re: [PATCH v8 2/5] tools: add routine to get CMT L3 event mask
Date: Wed, 28 Jan 2015 13:40:25 +0000 [thread overview]
Message-ID: <1422452425.14124.48.camel@citrix.com> (raw)
In-Reply-To: <1422432286-7276-3-git-send-email-chao.p.peng@linux.intel.com>
On Wed, 2015-01-28 at 16:04 +0800, Chao Peng wrote:
> This is the tools side wrapper for XEN_SYSCTL_PSR_CMT_get_l3_event_mask
> of XEN_SYSCTL_psr_cmt_op.
>
> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
> ---
> tools/libxc/include/xenctrl.h | 1 +
> tools/libxc/xc_psr.c | 17 +++++++++++++++++
> tools/libxl/libxl.h | 1 +
This needs a LIBXL_HAVE #define in libxl.h to advertise the new
functionality.
> +int xc_psr_cmt_get_l3_event_mask(xc_interface *xch, uint32_t *event_mask);
What are the possible values of the event mask? Is there a guarantee
from somewhere that 32-bits is always sufficient?
How can the libxl caller decode the meaning of the bits since they are
not defined in the libxl.h header?
Perhaps a struct of booleans would be a better interface at the libxl
level?
Or perhaps the interface should be more along the lines of "is psr
feature X available", like libxl_psr_..._feature_enabled(ctx,
SOME_SYMBOL)?
Or perhaps the function to actual access the info should have an
ERROR_PSR_FUNCTION NOT_SUPPORTED return?
Ian.
next prev parent reply other threads:[~2015-01-28 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 8:04 [PATCH v8 0/5] enable Memory Bandwidth Monitoring (MBM) for VMs Chao Peng
2015-01-28 8:04 ` [PATCH v8 1/5] x86: allow reading MSR_IA32_TSC with XENPF_resource_op Chao Peng
2015-01-28 15:42 ` Jan Beulich
2015-01-29 6:35 ` Chao Peng
2015-01-28 8:04 ` [PATCH v8 2/5] tools: add routine to get CMT L3 event mask Chao Peng
2015-01-28 13:40 ` Ian Campbell [this message]
2015-01-29 8:32 ` Chao Peng
2015-01-28 8:04 ` [PATCH v8 3/5] tools: correct coding style for psr Chao Peng
2015-01-28 8:04 ` [PATCH v8 4/5] tools: code refactoring for MBM Chao Peng
2015-01-28 8:04 ` [PATCH v8 5/5] tools, docs: add total/local memory bandwith monitoring Chao Peng
2015-01-28 14:04 ` Ian Campbell
2015-01-28 14:10 ` Ian Jackson
2015-01-28 14:12 ` Ian Campbell
2015-01-29 8:17 ` Chao Peng
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=1422452425.14124.48.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=will.auld@intel.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.