From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH v3 1/7] libxl: get rid of the SEDF scheduler Date: Mon, 6 Jul 2015 16:40:40 +0100 Message-ID: <559AA178.5030600@eu.citrix.com> References: <20150706152620.12310.7021.stgit@Solace.station> <20150706153043.12310.43382.stgit@Solace.station> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZC8WI-0004QC-He for xen-devel@lists.xenproject.org; Mon, 06 Jul 2015 15:41:22 +0000 In-Reply-To: <20150706153043.12310.43382.stgit@Solace.station> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dario Faggioli , xen-devel@lists.xenproject.org Cc: Wei Liu , Ian Jackson , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 07/06/2015 04:30 PM, Dario Faggioli wrote: > only the interface is left in place, for backward > compile-time compatibility, but every attempt to > use it would throw an error. > > Signed-off-by: Dario Faggioli > Reviewed-by: George Dunlap This probably should have been dropped... > Chenges from v2: > - introduce and use ERROR_FEATURE_REMOVED, as requested > during review; > - mark the SEDF only parameter as deprecated in libxl_types.idl, > as requested during review. ...given these. One question: > @@ -356,9 +357,13 @@ libxl_domain_sched_params = Struct("domain_sched_params",[ > ("weight", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_WEIGHT_DEFAULT'}), > ("cap", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_CAP_DEFAULT'}), > ("period", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_PERIOD_DEFAULT'}), > - ("slice", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_SLICE_DEFAULT'}), > - ("latency", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_LATENCY_DEFAULT'}), > - ("extratime", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_EXTRATIME_DEFAULT'}), > + # The following three parameters ('slice', 'latency' and 'extratime') are deprecated, > + # and will have no effect if used, since the SEDF scheduler has been removed. > + # Note that 'period' was an SDF parameter too, but it is still effective as it is > + # now used (together with 'budget') by the RTDS scheduler. > + ("slice", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_SLICE_DEFAULT'}), # deprecated > + ("latency", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_LATENCY_DEFAULT'}), # deprecated > + ("extratime", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_EXTRATIME_DEFAULT'}), # deprecated > ("budget", integer, {'init_val': 'LIBXL_DOMAIN_SCHED_PARAM_BUDGET_DEFAULT'}), Since we're aiming for API compatibility rather than ABI compatibility, is it allowable to move 'budget' up above the comment, so that it's more obvious that it hasn't been deprecated? -George