CC'ing Julien.
On Wed, 1 Mar 2017, Dario Faggioli wrote:
> On Wed, 2017-03-01 at 02:05 +0200, Anastassios Nanos wrote:
> > On Wed, Dec 7, 2016 at 8:29 PM, Dario Faggioli
> > wrote:
> > >
> > > % Heterogeneous Multi Processing Support in Xen
> > > % Revision 1
> > >
> > > [...]
> > Hi all,
> >
On Wed, 2017-03-01 at 02:05 +0200, Anastassios Nanos wrote:
> On Wed, Dec 7, 2016 at 8:29 PM, Dario Faggioli
> wrote:
> >
> > % Heterogeneous Multi Processing Support in Xen
> > % Revision 1
> >
> > [...]
> Hi all,
>
Hello,
> We are sending a branch[1] for comments on an initial implementation
On Wed, Dec 7, 2016 at 8:29 PM, Dario Faggioli
wrote:
> % Heterogeneous Multi Processing Support in Xen
> % Revision 1
>
> \clearpage
>
> # Basics
>
>
> Status: **Design Document**
>
> Architecture(s): x86, arm
>
>Component(s): Hypervisor and
> On Dec 16, 2016, at 4:05 PM, George Dunlap wrote:
>
>
>> On Dec 8, 2016, at 2:29 AM, Dario Faggioli wrote:
>
>> For the vCPUs for which no class is specified, default behavior applies.
>>
>> **TODO:** note that I think it must be possible to associate more than
>> one class to a vCPU. This
> On Dec 8, 2016, at 2:29 AM, Dario Faggioli wrote:
> For the vCPUs for which no class is specified, default behavior applies.
>
> **TODO:** note that I think it must be possible to associate more than
> one class to a vCPU. This is expressed in the example above, and assumed
> to be true throu
> On Dec 9, 2016, at 5:09 PM, Jan Beulich wrote:
>
On 09.12.16 at 09:29, wrote:
>> On Fri, 2016-12-09 at 01:13 -0700, Jan Beulich wrote:
>> On 08.12.16 at 22:54, wrote:
Yeah, that was what was puzzling me too. Keeping them ordered has
the
nice property that if a user sa
On 15/12/16 19:41, Dario Faggioli wrote:
> On Thu, 2016-12-08 at 11:38 +0100, Juergen Gross wrote:
>> So you really solved the following problem in credit2?
>>
>> You have three domains with 2 vcpus each and different weights. Run
>> them
>> on 3 physical cpus with following pinning:
>>
>> dom1: pc
On Thu, 2016-12-08 at 11:38 +0100, Juergen Gross wrote:
> So you really solved the following problem in credit2?
>
> You have three domains with 2 vcpus each and different weights. Run
> them
> on 3 physical cpus with following pinning:
>
> dom1: pcpu 1 and 2
> dom2: pcpu 2 and 3
> dom3: pcpu 1 a
On Fri, 9 Dec 2016, Jan Beulich wrote:
> >>> On 09.12.16 at 09:29, wrote:
> > On Fri, 2016-12-09 at 01:13 -0700, Jan Beulich wrote:
> >> > > > On 08.12.16 at 22:54, wrote:
> >> > Yeah, that was what was puzzling me too. Keeping them ordered has
> >> > the
> >> > nice property that if a user says
>>> On 09.12.16 at 09:29, wrote:
> On Fri, 2016-12-09 at 01:13 -0700, Jan Beulich wrote:
>> > > > On 08.12.16 at 22:54, wrote:
>> > Yeah, that was what was puzzling me too. Keeping them ordered has
>> > the
>> > nice property that if a user says the following in a config file:
>> >
>> > vcpucla
On Fri, 2016-12-09 at 01:13 -0700, Jan Beulich wrote:
> > > > On 08.12.16 at 22:54, wrote:
> > Yeah, that was what was puzzling me too. Keeping them ordered has
> > the
> > nice property that if a user says the following in a config file:
> >
> > vcpuclass=["0-3:class0", "4-7:class1"]
> >
> > (
>>> On 08.12.16 at 22:54, wrote:
> On Thu, 2016-12-08 at 03:14 -0700, Jan Beulich wrote:
>> > > > On 07.12.16 at 19:29, wrote:
>> > The list of classes is kept ordered from the more powerful to the
>> > less
>> > powerful.
>> > **TODO:** this has been [proposed by
>> > George](https://lists.xenp
On Thu, 2016-12-08 at 03:14 -0700, Jan Beulich wrote:
> > > > On 07.12.16 at 19:29, wrote:
> > The list of classes is kept ordered from the more powerful to the
> > less
> > powerful.
> > **TODO:** this has been [proposed by
> > George](https://lists.xenproject.org/archives/html/xen-devel/2016-0
On Thu, 2016-12-08 at 11:38 +0100, Juergen Gross wrote:
> On 08/12/16 11:27, Dario Faggioli wrote:
> > On Thu, 2016-12-08 at 07:12 +0100, Juergen Gross wrote:
> > > Any idea how to avoid problems in the schedulers related to vcpus
> > > with
> > > different weights?
> > >
> > Sure: use Credit2! :
On Thu, 8 Dec 2016, Jan Beulich wrote:
> >>> On 07.12.16 at 19:29, wrote:
> > ### x86
> >
> > There is no HMP platform of relevance, for now, in x86 world. Therefore,
> > only one class will exist, and all the CPUs will be set to belong to it.
> > **TODO X86:** is this correct?
>
> What about th
>>> On 08.12.16 at 11:23, wrote:
> On Thu, 2016-12-08 at 03:14 -0700, Jan Beulich wrote:
>> > > > On 07.12.16 at 19:29, wrote:
>> > ### x86
>> >
>> > There is no HMP platform of relevance, for now, in x86 world.
>> > Therefore,
>> > only one class will exist, and all the CPUs will be set to belo
On 08/12/16 11:27, Dario Faggioli wrote:
> On Thu, 2016-12-08 at 07:12 +0100, Juergen Gross wrote:
>> On 07/12/16 19:29, Dario Faggioli wrote:
>>> ### Phase 2
>>>
>>> Inside Xen, the various schedulers will be modified to deal
>>> internally with
>>> the fact that vCPUs can only run on pCPUs from t
On Thu, 2016-12-08 at 07:12 +0100, Juergen Gross wrote:
> 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
>
Oops,
On Thu, 2016-12-08 at 03:14 -0700, Jan Beulich wrote:
> > > > On 07.12.16 at 19:29, wrote:
> > ### x86
> >
> > There is no HMP platform of relevance, for now, in x86 world.
> > Therefore,
> > only one class will exist, and all the CPUs will be set to belong
> > to it.
> > **TODO X86:** is this co
>>> On 07.12.16 at 19:29, wrote:
> ### x86
>
> There is no HMP platform of relevance, for now, in x86 world. Therefore,
> only one class will exist, and all the CPUs will be set to belong to it.
> **TODO X86:** is this correct?
What about the original Xeon Phi (on a PCIe card)?
> ## Hypervisor
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 intern
% Heterogeneous Multi Processing Support in Xen
% Revision 1
\clearpage
# Basics
Status: **Design Document**
Architecture(s): x86, arm
Component(s): Hypervisor and toolstack
# Overview
HMP (Hetero
22 matches
Mail list logo
