All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Meng Xu <xumengpanda@gmail.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Wei Liu <Wei.Liu2@citrix.com>
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 15:31:30 +0200	[thread overview]
Message-ID: <1435584690.25170.243.camel@citrix.com> (raw)
In-Reply-To: <55912705.6070202@eu.citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1833 bytes --]

On Mon, 2015-06-29 at 12:07 +0100, George Dunlap wrote:
> 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.
> 
Ok then, even better. Another patch to OSSTest to that effect will come
shortly.

> > 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.
> 
Yep, that's, in fact, what I think I've done in my 'get rid of SEDF'
series, that I sent Friday afternoon.

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2015-06-29 13:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 10:58 [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS Dario Faggioli
2015-06-26 11:08 ` Ian Campbell
2015-06-26 11:11   ` Dario Faggioli
2015-06-26 12:02 ` Ian Jackson
2015-06-26 13:43   ` Stop testing SEDF almost at all (at least until Xen 4.2) [was: Re: [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS] Dario Faggioli
2015-06-26 15:24     ` Ian Jackson
2015-06-26 16:09       ` Dario Faggioli
2015-06-26 16:14         ` Ian Campbell
2015-06-29 11:07       ` George Dunlap
2015-06-29 13:31         ` Dario Faggioli [this message]
2015-06-27 19:05 ` [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS Meng Xu
2015-06-29  8:53   ` Ian Campbell
2015-06-29  9:33     ` Dario Faggioli
2015-06-30  4:29       ` Meng Xu
2015-06-30  9:11         ` Ian Jackson
2015-06-30  9:20           ` Ian Campbell
2015-06-30  9:41             ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1435584690.25170.243.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xumengpanda@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.