From: "Jan Beulich" <jbeulich@suse.com>
To: andrew.cooper3@citrix.com, george.dunlap@eu.citrix.com,
dongxiao.xu@intel.com
Cc: will.auld@intel.com, Ian.Campbell@citrix.com,
jun.nakajima@intel.com, xen-devel@lists.xen.org
Subject: Re: Xen Platform QoS design discussion
Date: Fri, 30 May 2014 12:15:11 +0100 [thread overview]
Message-ID: <5388764F02000078000B53FA@mail.emea.novell.com> (raw)
In-Reply-To: <40776A41FC278F40B59438AD47D147A911A2121E@SHSMSX104.ccr.corp.intel.com>
>>> "Xu, Dongxiao" <dongxiao.xu@intel.com> 05/30/14 9:52 AM >>>
> From: Jan Beulich [mailto:jbeulich@suse.com]
>> Question is whether this mechanism (which I'd like to be done so it can also
>> later get added support for e.g. port I/O: see Linux'es dcdbas_smi_request()
>> for where this might be useful) should become a sysctl op or - to be
>> easily usable by the kernel too - a platform one.
>
>For CQM, this MSR access hypercall may be somewhat specific, because it
>requires one MSR write and one MSR read, which cannot be split into two
>separate hypercalls to avoid preemption in the middle.
Sure - you'd need a flag to suppress preemption between two specific (batched)
operations.
Jan
next prev parent reply other threads:[~2014-05-30 11:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 16:47 Xen Platform QoS design discussion Xu, Dongxiao
2014-04-30 17:02 ` Ian Campbell
2014-05-01 0:56 ` Xu, Dongxiao
2014-05-02 9:23 ` Jan Beulich
2014-05-02 12:30 ` Xu, Dongxiao
2014-05-02 12:40 ` Jan Beulich
2014-05-04 0:46 ` Xu, Dongxiao
2014-05-06 9:10 ` Ian Campbell
2014-05-06 1:40 ` Xu, Dongxiao
2014-05-06 7:55 ` Jan Beulich
2014-05-06 10:06 ` Andrew Cooper
2014-05-07 2:08 ` Xu, Dongxiao
2014-05-07 9:10 ` Ian Campbell
2014-05-07 13:26 ` George Dunlap
2014-05-07 21:18 ` Andrew Cooper
2014-05-08 5:21 ` Xu, Dongxiao
2014-05-08 11:25 ` Andrew Cooper
2014-05-09 2:41 ` Xu, Dongxiao
2014-05-13 1:53 ` Xu, Dongxiao
2014-05-16 5:11 ` Xu, Dongxiao
2014-05-19 11:28 ` George Dunlap
2014-05-19 11:45 ` Jan Beulich
2014-05-19 12:13 ` George Dunlap
2014-05-19 12:41 ` Jan Beulich
2014-05-22 8:19 ` Xu, Dongxiao
2014-05-22 8:39 ` Jan Beulich
2014-05-22 9:27 ` George Dunlap
2014-05-26 0:51 ` Xu, Dongxiao
2014-05-29 0:45 ` Xu, Dongxiao
2014-05-29 7:01 ` Jan Beulich
2014-05-29 7:31 ` Xu, Dongxiao
2014-05-29 9:11 ` Jan Beulich
2014-05-30 9:10 ` Ian Campbell
2014-05-30 11:17 ` Jan Beulich
2014-05-30 12:33 ` Ian Campbell
2014-06-05 0:48 ` Xu, Dongxiao
2014-06-05 10:43 ` George Dunlap
2014-05-29 9:13 ` Andrew Cooper
2014-05-30 1:07 ` Xu, Dongxiao
2014-05-30 6:23 ` Jan Beulich
2014-05-30 7:51 ` Xu, Dongxiao
2014-05-30 11:15 ` Jan Beulich [this message]
2014-05-02 12:50 ` Andrew Cooper
2014-05-04 2:34 ` Xu, Dongxiao
2014-05-06 9:12 ` Ian Campbell
2014-05-06 10:00 ` Andrew Cooper
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=5388764F02000078000B53FA@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dongxiao.xu@intel.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jun.nakajima@intel.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.