From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Meng Xu <xumengpanda@gmail.com>, Wei Liu <Wei.Liu2@citrix.com>,
Ian Campbell <ian.campbell@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: Fri, 26 Jun 2015 18:09:13 +0200 [thread overview]
Message-ID: <1435334953.25170.230.camel@citrix.com> (raw)
In-Reply-To: <21901.28322.907293.881746@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1976 bytes --]
On Fri, 2015-06-26 at 16:24 +0100, 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.
>
Great! :-)
> 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'.)
>
Ok, I'm fine with this. Looking at make-flight, we seem to want to be
able to run tests on Xen 3.*, 4.0, 4.1. As I said in my email, I can't
speak for these. I honestly think that SEDF was already broken, so I
personally would be more than glad to send a patch that gets rid of it
all the way, but that does not count much, I guess, as I wasn't here!
As soon as you (and others) will let me know what's best, I'll do it.
> As to the substance, I would like to take advice from the relevant HV
> maintainers about this change.
>
Sure.
> With my tools maintainer hat on, we should consider removing the
> sedf-specific code from libxl.
>
Patch coming. I'm not removing the interfaces and the symbols, to allow
backword build-time compatibility to be retained, but yes, I'm removing
it from everywhere, and "neutralizing it" (just in case!) in libxl...
You shall see! :-P
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
next prev parent reply other threads:[~2015-06-26 16:09 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 [this message]
2015-06-26 16:14 ` Ian Campbell
2015-06-29 11:07 ` George Dunlap
2015-06-29 13:31 ` Dario Faggioli
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=1435334953.25170.230.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Wei.Liu2@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.