From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [RFC PATCH v2 5/7] Add cbs parameter support and removed sedf parameters with a LIBXL_API_VERSION gate from libxl. Date: Fri, 11 Jul 2014 01:02:15 +0200 Message-ID: <1405033335.29306.167.camel@Solace> References: <1404939348-4926-1-git-send-email-josh.whitehead@dornerworks.com> <1404939348-4926-6-git-send-email-josh.whitehead@dornerworks.com> <1405001385.24434.20.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5654468461228389280==" Return-path: In-Reply-To: <1405001385.24434.20.camel@kazak.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 Campbell Cc: Stefano Stabellini , George Dunlap , Ian Jackson , Robert VanVossen , Xen-devel , Nathan Studer , Josh Whitehead List-Id: xen-devel@lists.xenproject.org --===============5654468461228389280== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4PQHqjvbVMHouqJ3YmoY" --=-4PQHqjvbVMHouqJ3YmoY Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On gio, 2014-07-10 at 15:09 +0100, Ian Campbell wrote: > On Wed, 2014-07-09 at 16:55 -0400, Josh Whitehead wrote: > > From: Robbie VanVossen > >=20 > > We made an attempt at doing the versioning gate in this file. Please l= et us > > know if further changes are needed, and where they are needed to proper= ly guard > > the API. >=20 > I previously said that I thought it was fine to remove the obsolete SEDF > stuff from the libxl API. >=20 > However I mentioned this to the other maintainers and they disagreed > with me. The feeling is that an old application which used the old SEDF > parameters should continue to build but that trying to use those > parameters should result in an error. > Indeed. So, as far as this series is concerned, it looks like either the following solutions: - introduce a new scheduler, with a new name, and deprecate SEDF all=20 together - keep the name and the full existing interface, but warn the user when she touches one of the params that are no longer in use in the=20 implementation would be ok. Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-4PQHqjvbVMHouqJ3YmoY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlO/G3cACgkQk4XaBE3IOsTi7wCbBf9Sg6vh5mieqkmZh71vV03K o8sAn0qeQwR/P0RsoM8xJFFInNIvg5HE =xfgd -----END PGP SIGNATURE----- --=-4PQHqjvbVMHouqJ3YmoY-- --===============5654468461228389280== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============5654468461228389280==--