This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Fwd: Next vcpu in queue

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Fwd: Next vcpu in queue
From: Ananth <cbananth@xxxxxxxxx>
Date: Fri, 24 Apr 2009 09:59:07 +0530
Delivery-date: Thu, 23 Apr 2009 21:29:33 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=aDriS0tTCMVxESt+i8CAtS+hFTb0NCqFXs6BS4z8Auk=; b=qYyy8NXWnn4FtJ6wbEPUD8SJFI8EJHHprwPWDYqxUjVn5w/cEisfaWCz8eegtmyDrR rmMbWDb7i9oI4rfQCsxzACWK394KaiK887U9ek8Arqr7u4ockjWKVKZEh0R/mhqov2CA 0EsZejn+KKCrcxht1wp46Fc8N1BqCaiwa1GjI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=GCtKQfbZf/+OT0eAZZI/oC0pjbZr0ZfiroxNTkF8zbRWhug528nYV8ZBO+1u7+JzCP sSxio9aL18H9xwBeomx6f//b/CUGqIlmbkMWIgg7hmGdI54+kUts+ZWNjq8WoF4d7jg9 snt1GZIlDZ1dxOEemOEeuvf/4XQQkfSJgqo88=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bdf293de0904232105o2535565t3abfa446320d7ccf@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <bdf293de0904232105o2535565t3abfa446320d7ccf@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

In connection with my previous mail, I have attached a file. This file has source code picked up from the book, 'The definitive guide to Xen hypervisor', for adding a simple scheduler to xen.

In the functions, rrobin_vcpu_init and rrobin_vcpu_destroy, the book uses  (probably a macro call) VCPU_NEXT(struct vcpu). But there is no definition given for that function. It would be great if you can point to an existing function from xen 3.3.1 source code can be used.

Also, in the function rrobin_schedule (s_time_t ), the function __get_per_cpu is used (line no. 82) , which is not existing in 3.3.1 code.
I want to return an idle task. Could you guide me as to which function in the 3.3.1 source code would be appropriate for the same?

Thank you very much.


---------- Forwarded message ----------
From: Ananth <cbananth@xxxxxxxxx>
Date: Fri, Apr 24, 2009 at 9:35 AM
Subject: Next vcpu in queue
To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>

I am using xen 3.3.1 I want to destroy the head element of that list and assign the next in line vcpu as the head.
I have declared a pointer struct vcpu * vcpu_list_head.
I would like to assign vpu_list_head = ' get the next vcpu in queue which can be scheduled'. I am not sure if there is a already a function available which can do this.
Please guide.

Thank you

Attachment: sched_rrobin.txt
Description: Text document

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>