From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Stop testing SEDF almost at all (at least until Xen 4.2) [was: Re: [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS] Date: Mon, 29 Jun 2015 12:07:49 +0100 Message-ID: <55912705.6070202@eu.citrix.com> References: <1435316331.25170.191.camel@citrix.com> <21901.16190.81742.872136@mariner.uk.xensource.com> <1435326209.25170.220.camel@citrix.com> <21901.28322.907293.881746@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z9Wup-0000Op-Cp for xen-devel@lists.xenproject.org; Mon, 29 Jun 2015 11:07:55 +0000 In-Reply-To: <21901.28322.907293.881746@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson , Dario Faggioli Cc: "xen-devel@lists.xenproject.org" , Meng Xu , Wei Liu , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 06/26/2015 04:24 PM, Ian Jackson wrote: > Dario Faggioli writes ("Stop testing SEDF almost at all (at least until Xen 4.2) [was: Re: [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS]"): >> However, I honestly think that testing SEDF for earlier versions than >> xen-unstable (at least until 4.2) is also just a waste of test >> resources. > ... >> Therefore, I'd argue for the attached patch, [...] > > With my osstest maintainer hat on the aim of this patch is fine by me. > But it seems that sedf is not coming back, so if we are going to do > this to osstest we should probably rip the code out. So I would > welcome a followup which got rid of all the leftover traces in > make-flight and allow.all. (`git-grep -i sedf'.) > > As to the substance, I would like to take advice from the relevant HV > maintainers about this change. I agree with Dario that there's no point in testing it, and with you that we might as well rip the code out of osstest. > With my tools maintainer hat on, we should consider removing the > sedf-specific code from libxl. With the obvious caveat that old code with SEDF macros and such still needs to compile but return a runtime error if people try to use it. -George