xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	xen-devel@lists.xenproject.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v2 1/7] libxl: get rid of the SEDF scheduler
Date: Fri, 3 Jul 2015 16:33:26 +0200	[thread overview]
Message-ID: <1435934006.14347.75.camel@citrix.com> (raw)
In-Reply-To: <1435933382.9447.127.camel@citrix.com>


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

On Fri, 2015-07-03 at 15:23 +0100, Ian Campbell wrote:
> On Fri, 2015-07-03 at 12:24 +0200, Dario Faggioli wrote:
> 
> > @@ -5932,7 +5865,8 @@ int libxl_domain_sched_params_set(libxl_ctx *ctx, uint32_t domid,
> >  
> >      switch (sched) {
> >      case LIBXL_SCHEDULER_SEDF:
> > -        ret=sched_sedf_domain_set(gc, domid, scinfo);
> > +        LOG(ERROR, "SEDF scheduler no longer available");
> > +        ret=ERROR_INVAL;
> 
> Should we have a specific error code for removed functionality?
> 
Good point: shall I introduce it? If yes, how should it be called?

ERROR_REMOVED
ERROR_DEPRECATED
ERROR_GONE

I think I'd go for _REMOVED, as deprecated suggests (to me at least)
that it's still there but nshould not be used.

Any other ideas?

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-07-03 14:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 10:24 [PATCH v2 0/7] get rid of the SEDF scheduler Dario Faggioli
2015-07-03 10:24 ` [PATCH v2 1/7] libxl: " Dario Faggioli
2015-07-03 14:23   ` Ian Campbell
2015-07-03 14:33     ` Dario Faggioli [this message]
2015-07-03 14:39       ` Ian Campbell
2015-07-03 14:50         ` Ian Jackson
2015-07-03 14:49     ` Ian Jackson
2015-07-03 10:24 ` [PATCH v2 2/7] tools: python: get rid of the SEDF scheduler bindings Dario Faggioli
2015-07-03 14:23   ` Ian Campbell
2015-07-03 10:24 ` [PATCH v2 3/7] libxc: get rid of the SEDF scheduler Dario Faggioli
2015-07-03 14:23   ` Ian Campbell
2015-07-03 10:25 ` [PATCH v2 4/7] xen: " Dario Faggioli
2015-07-03 10:30   ` Andrew Cooper
2015-07-03 13:26     ` Dario Faggioli
2015-07-03 10:25 ` [PATCH v2 5/7] xen: kill sched_sedf.c Dario Faggioli
2015-07-03 10:25 ` [PATCH v2 6/7] xl: get rid of the SEDF scheduler Dario Faggioli
2015-07-03 14:26   ` Ian Campbell
2015-07-03 14:36     ` Dario Faggioli
2015-07-03 14:42       ` Ian Campbell
2015-07-03 10:25 ` [PATCH v2 7/7] docs: " Dario Faggioli
2015-07-03 14:26   ` Ian Campbell

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=1435934006.14347.75.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).