All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross McIlroy <ross.mcilroy@gmail.com>
To: Andy Lee <andylee@hitx.net>
Cc: Stephan Diestelhorst <sd386@cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Status of sedf?
Date: Thu, 18 Aug 2005 22:23:57 +0100	[thread overview]
Message-ID: <7f4e21e305081814239a71d66@mail.gmail.com> (raw)
In-Reply-To: <6.1.2.0.2.20050818101008.083586e0@secure.hitx.net>

That sounds like a problem I was getting in Xen-unstable.  The patch I
submitted a day or two ago should fix it, but it might be different in
Xen-testing.  The patch is on the message:

http://lists.xensource.com/archives/html/xen-tools/2005-08/msg00094.html

Cheers

Ross


On 8/18/05, Andy Lee <andylee@hitx.net> wrote:
> At 07:33 AM 8/18/2005, Stephan Diestelhorst wrote:
> 
> >On Thursday 18 August 2005 03:36, Andy Lee wrote:
> > > At 03:11 PM 8/17/2005, I wrote:
> > > >Sorry to report that the patch didn't work.  I applied the patch to my
> > > >Xen-2.0-testing tree and copied xen/common/sched_sedf.c from
> > > >Xen-unstable.  When compiling xen, sched_sedf.c generated these types of
> > > >errors:
> >
> >Outch. Now I see... For some reason (forgot to do 'hg add' ) sched_sedf.c
> >wasn't included. You can't use the unstable one, as it has a different naming
> >scheme.
> >
> >Attached is the patch, this time WITH sched_sedf.c
> 
> Also missing is xen-2.0-testing.hg/tools/libxc/xc_sedf.c - but this time, I
> was able to use the xc_sedf.c from the unstable tree!!!  :-)
> 
> It compiles, but I encountered this problem:
> 
> (Xen-2.0-testing)
> # xm list
> Name              Id  Mem(MB)  CPU  State  Time(s)  Console
> Domain-0           0      251    0  r----     14.1
> Sarge              1      127    0  -b---      3.1    9601
> 
> # xm sedf 1 0 0 0 1 128
> Error: (22, 'Invalid argument')
> 
> Last night, I also compiled xen-unstable to see how sedf works:
> 
> (Xen-unstable)
> # xm sedf 1 0 0 0 1 128
> Unexpected error: exceptions.TypeError
> 
> Please report to xen-devel@lists.xensource.com
> Traceback (most recent call last):
>    File "/usr/sbin/xm", line 10, in ?
>      main.main(sys.argv)
>    File "/usr/lib/python/xen/xm/main.py", line 646, in main
>      rc = cmd(args)
>    File "/usr/lib/python/xen/xm/main.py", line 435, in xm_sedf
>      server.xend_domain_cpu_sedf_set(dom, *v)
> TypeError: xend_domain_cpu_sedf_set() takes exactly 7 arguments (6 given)
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

  reply	other threads:[~2005-08-18 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06 20:20 Status of sedf? Andy Lee
2005-08-07  1:47 ` Mark Williamson
2005-08-07  6:12   ` Stephan Diestelhorst
2005-08-07 14:02     ` Mark Williamson
2005-08-07 17:43     ` Andy Lee
2005-08-09 21:42       ` Stephan Diestelhorst
2005-08-10  2:38         ` Stephan Diestelhorst
2005-08-17 22:11           ` Andy Lee
2005-08-18  2:36             ` Andy Lee
2005-08-18 14:33               ` Stephan Diestelhorst
2005-08-18 17:50                 ` Andy Lee
2005-08-18 21:23                   ` Ross McIlroy [this message]
2005-08-19  7:31                   ` Andy Lee

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=7f4e21e305081814239a71d66@mail.gmail.com \
    --to=ross.mcilroy@gmail.com \
    --cc=andylee@hitx.net \
    --cc=sd386@cam.ac.uk \
    --cc=xen-devel@lists.xensource.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.