All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, George.Dunlap@eu.citrix.com,
	andrew.cooper3@citrix.com, Ian.Jackson@eu.citrix.com,
	xen-devel@lists.xen.org, Dongxiao Xu <dongxiao.xu@intel.com>,
	dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v11 3/9] tools: provide interface for generic MSR access
Date: Mon, 23 Jun 2014 09:29:18 -0400	[thread overview]
Message-ID: <20140623132918.GC9153@laptop.dumpdata.com> (raw)
In-Reply-To: <53A7EFA6020000780001C4AE@mail.emea.novell.com>

On Mon, Jun 23, 2014 at 08:13:10AM +0100, Jan Beulich wrote:
> >>> On 20.06.14 at 19:34, <konrad.wilk@oracle.com> wrote:
> > On Fri, Jun 20, 2014 at 10:31:44PM +0800, Dongxiao Xu wrote:
> >> Xen added a new sysctl hypercall for generic MSR access, and this is the
> >> tool side change to wrapper the hypercall into xc APIs.
> > 
> > I really like the idea that Jan surfaced. That is use an
> > cpu bitmap for the operation (see xc_tbuf.c as an example)
> > and my recent postings http://osdir.com/ml/general/2014-06/msg24386.html.
> > 
> > That way you can define exactly which CPUs you want to do it
> > at and you can do one nice hypercall that will do it all at
> > once for you.
> 
> CPU bitmap? Me? I don't think I ever suggested anything like that,
> not the least because it would become problematic where to store
> the data (would need to be either [potentially very] sparse arrays,
> or need a complicated [or at least ugly] mechanism for each CPU to
> find its slot).

I am sorry for the assumption. In that case lets drop that idea.

> 
> Jan
> 

  reply	other threads:[~2014-06-23 13:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 14:31 [PATCH v11 0/9] enable Cache QoS Monitoring (CQM) feature Dongxiao Xu
2014-06-20 14:31 ` [PATCH v11 1/9] x86: add generic MSR access hypercall Dongxiao Xu
2014-06-20 14:57   ` Andrew Cooper
2014-06-23  6:34     ` Xu, Dongxiao
2014-06-20 15:00   ` Jan Beulich
2014-06-23  6:27     ` Xu, Dongxiao
2014-06-23  6:45       ` Jan Beulich
2014-06-23  7:29         ` Xu, Dongxiao
2014-06-23  7:42           ` Jan Beulich
2014-06-23 13:32           ` Konrad Rzeszutek Wilk
2014-06-20 14:31 ` [PATCH v11 2/9] xsm: add MSR operation related xsm policy Dongxiao Xu
2014-06-24 19:20   ` Daniel De Graaf
2014-06-20 14:31 ` [PATCH v11 3/9] tools: provide interface for generic MSR access Dongxiao Xu
2014-06-20 17:34   ` Konrad Rzeszutek Wilk
2014-06-23  7:13     ` Jan Beulich
2014-06-23 13:29       ` Konrad Rzeszutek Wilk [this message]
2014-06-27 13:05   ` Ian Campbell
2014-06-20 14:31 ` [PATCH v11 4/9] x86: detect and initialize Platform QoS Monitoring feature Dongxiao Xu
2014-06-20 15:04   ` Jan Beulich
2014-06-23  6:38     ` Xu, Dongxiao
2014-06-23  6:50       ` Jan Beulich
2014-06-23  7:30         ` Xu, Dongxiao
2014-06-20 17:35   ` Konrad Rzeszutek Wilk
2014-06-20 14:31 ` [PATCH v11 5/9] x86: dynamically attach/detach QoS monitoring service for a guest Dongxiao Xu
2014-06-20 15:08   ` Jan Beulich
2014-06-23  6:43     ` Xu, Dongxiao
2014-06-20 14:31 ` [PATCH v11 6/9] x86: collect global QoS monitoring information Dongxiao Xu
2014-06-20 15:16   ` Jan Beulich
2014-06-23  6:55     ` Xu, Dongxiao
2014-06-23  7:06       ` Jan Beulich
2014-06-20 14:31 ` [PATCH v11 7/9] x86: enable QoS monitoring for each domain RMID Dongxiao Xu
2014-06-20 15:20   ` Jan Beulich
2014-06-23  6:55     ` Xu, Dongxiao
2014-06-20 14:31 ` [PATCH v11 8/9] xsm: add platform QoS related xsm policies Dongxiao Xu
2014-06-24 19:24   ` Daniel De Graaf
2014-06-20 14:31 ` [PATCH v11 9/9] tools: CMDs and APIs for Platform QoS Monitoring Dongxiao Xu
2014-06-23 15:22   ` Ian Jackson
2014-06-27  7:15     ` Xu, Dongxiao

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=20140623132918.GC9153@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=dongxiao.xu@intel.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.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.