From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ross McIlroy <ross.mcilroy@gmail.com>
Subject: Re: Status of sedf?
Date: Thu, 18 Aug 2005 22:23:57 +0100
Message-ID: <7f4e21e305081814239a71d66@mail.gmail.com>
References: <6.1.2.0.2.20050806131339.054a8e40@secure.hitx.net>
	<6.1.2.0.2.20050817125001.0468f220@secure.hitx.net>
	<6.1.2.0.2.20050817193518.03091c30@secure.hitx.net>
	<200508181533.36009.sd386@cam.ac.uk>
	<6.1.2.0.2.20050818101008.083586e0@secure.hitx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <6.1.2.0.2.20050818101008.083586e0@secure.hitx.net>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Andy Lee <andylee@hitx.net>
Cc: Stephan Diestelhorst <sd386@cam.ac.uk>, xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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:
>=20
> >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 type=
s 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 n=
aming
> >scheme.
> >
> >Attached is the patch, this time WITH sched_sedf.c
>=20
> 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!!!  :-)
>=20
> It compiles, but I encountered this problem:
>=20
> (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
>=20
> # xm sedf 1 0 0 0 1 128
> Error: (22, 'Invalid argument')
>=20
> Last night, I also compiled xen-unstable to see how sedf works:
>=20
> (Xen-unstable)
> # xm sedf 1 0 0 0 1 128
> Unexpected error: exceptions.TypeError
>=20
> 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 =3D 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)
>=20
>=20
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>