From: Juergen Gross <jgross@suse.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
Xen Devel <xen-devel@lists.xen.org>
Cc: Peng Fan <peng.fan@nxp.com>,
Stefano Stabellini <sstabellini@kernel.org>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
anastassios.nanos@onapp.com, Jan Beulich <jbeulich@suse.com>,
Peng Fan <van.freenix@gmail.com>
Subject: Re: [DOC RFC] Heterogeneous Multi Processing Support in Xen
Date: Thu, 8 Dec 2016 07:12:13 +0100 [thread overview]
Message-ID: <3f9a7da1-7c05-e082-99d2-302dbeee61b9@suse.com> (raw)
In-Reply-To: <1481135379.3445.142.camel@citrix.com>
On 07/12/16 19:29, Dario Faggioli wrote:
> Setting and getting the CPU class of a vCPU will happen via two new
> hypercalls:
>
> * `XEN_DOMCTL_setvcpuclass`
> * `XEN_DOMCTL_setvcpuclass`
XEN_DOMCTL_getvcpuclass
> ### Phase 2
>
> Inside Xen, the various schedulers will be modified to deal internally with
> the fact that vCPUs can only run on pCPUs from the class(es) they are
> associated with. This allows for more efficient implementation, and paves
> the way for enabling more intelligent logic (e.g., for minimizing power
> consumption) in *phase 3*.
>
> Calling `libxl_set_vcpuaffinity()` from `xl` / libxl is therefore no longer
> necessary and will be avoided (i.e., only `libxl_set_vcpuclass()` will be
> called).
Any idea how to avoid problems in the schedulers related to vcpus with
different weights? Remember, weights and pinning don't go well together,
that was the main reason for inventing cpupools. You should at least
name that problem. In case of vcpus being capable to run on pcpus of
more than one class this problem might surface again.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-08 6:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 18:29 [DOC RFC] Heterogeneous Multi Processing Support in Xen Dario Faggioli
2016-12-08 6:12 ` Juergen Gross [this message]
2016-12-08 10:27 ` Dario Faggioli
2016-12-08 10:38 ` Juergen Gross
2016-12-08 21:45 ` Dario Faggioli
2016-12-15 18:41 ` Dario Faggioli
2016-12-16 7:44 ` Juergen Gross
2016-12-08 10:14 ` Jan Beulich
2016-12-08 10:23 ` Dario Faggioli
2016-12-08 10:41 ` Jan Beulich
2016-12-08 19:09 ` Stefano Stabellini
2016-12-08 21:54 ` Dario Faggioli
2016-12-09 8:13 ` Jan Beulich
2016-12-09 8:29 ` Dario Faggioli
2016-12-09 9:09 ` Jan Beulich
2016-12-09 19:20 ` Stefano Stabellini
2016-12-16 8:00 ` George Dunlap
2016-12-16 8:05 ` George Dunlap
2016-12-16 8:07 ` George Dunlap
2017-03-01 0:05 ` Anastassios Nanos
2017-03-01 17:38 ` Dario Faggioli
2017-03-01 18:58 ` Stefano Stabellini
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=3f9a7da1-7c05-e082-99d2-302dbeee61b9@suse.com \
--to=jgross@suse.com \
--cc=anastassios.nanos@onapp.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=peng.fan@nxp.com \
--cc=sstabellini@kernel.org \
--cc=van.freenix@gmail.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 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).