From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH v2 for Xen 4.6 3/4] libxl: enabling XL to
 set per-VCPU parameters of a domain for RTDS scheduler
Date: Wed, 17 Jun 2015 13:14:34 +0100
Message-ID: <1434543274.13744.353.camel@citrix.com>
References: <1432598984-20914-1-git-send-email-chong.li@wustl.edu>
	<1433504253.7108.231.camel@citrix.com>
	<1433778984.2403.27.camel@citrix.com>
	<CAGHO-ipLRv9FCu234oO3jVeyj0PCchvfmeGTgqS-71m_DNut2w@mail.gmail.com>
	<1433866738.2403.181.camel@citrix.com>
	<CAGHO-ioSLV4JigxLgdB4+xbsbxYPU7JpJ5TzmsCeAD-ZW4-22w@mail.gmail.com>
	<1434363154.2375.50.camel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1434363154.2375.50.camel@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Chong Li <chong.li@wustl.edu>, Wei Liu <wei.liu2@citrix.com>, Sisu Xi <xisisu@gmail.com>, George Dunlap <george.dunlap@eu.citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel <xen-devel@lists.xen.org>, Meng Xu <mengxu@cis.upenn.edu>, Chong Li <lichong659@gmail.com>, Dagaen Golomb <dgolomb@seas.upenn.edu>
List-Id: xen-devel@lists.xenproject.org

On Mon, 2015-06-15 at 12:12 +0200, Dario Faggioli wrote:
> A parameter is either per-domain or per-vcpu, no matter how the user try
> to set or get it. In RTDS, all parameters are per-domain now and, with
> your work, all of them are becoming per-vcpu, and that's ok. But then,
> per-dom parameters should just no longer exist.

Are you saying there is going to be no domain wide default for a given
per-vcpu parameter? 

if that is the case then what happens if I hotplug a new VCPU without
settings its per-vcpu properties?

I expected something like.

domain_params_set (weight=10)
add vcpu0 (weight will be 10)
add vcpu1 (weight will be 10)
vcpu_params_set(0, weight=20)
add vcpu2 (weight will be 10, from domain wide default)

If not that then what weight should vcpu2 have at this point?

Ian.