Re: [Xen-devel] [PATCH v1 1/4] xen: add real time scheduler rt

[Meng Xu <xumengpanda@xxxxxxxxx>]

Hi George and Dario,

2014-09-04 9:03 GMT-04:00 George Dunlap <George.Dunlap@xxxxxxxxxxxxx>:

On Thu, Sep 4, 2014 at 3:11 AM, Meng Xu <xumengpanda@xxxxxxxxx> wrote:
>
> What do you guys think about the approach of setting/getting vcpus? which
> approach do you prefer? Can we vote for it? (or maybe there exist some other
> ways to reach agreement? :-))

Well, the standard thing is for us to try to reach a consensus if
possible. If there's not a consensus, I as the scheduler maintainer
would get to / have to decide; Keir or Jan might overrule me if they
thought I was being completely unreasonable, but that would be a
pretty exceptional case. :-)

âI see. This is also a great idea! :-) Next time when I encounter such issues, I will summarize the strength and weakness of each approach and let you guys decide. :-)â

Â

On Thu, Sep 4, 2014 at 12:00 PM, Dario Faggioli
<dario.faggioli@xxxxxxxxxx> wrote:
> It's hard to be sure, but I'm leaning toward the full array (so 1, in
> Meng's list in that email). In fact, I expect parameters to be set for
> all the vcpus at, or immediately after, domain creation and, if
> something has to change at some point, it's quite likely that it will
> involve most (if not all) the vcpus (possibly, to different params, of
> course). I also do not expect for that to happen too frequently.

That would have been my guess -- that "set up once and don't change"
was the common case.

So let's go with #1:
* Always pass an array of all vcpus
* But have some magic values which mean "don't change this one".

âGreat! I will do that! :-)

âMengâ

-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel