 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] CPU and scheduler init, Part 2
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
|---|---|
| Subject: | [Xen-devel] CPU and scheduler init, Part 2 |
| From: | George Dunlap <dunlapg@xxxxxxxxx> |
| Date: | Thu, 9 Dec 2010 12:49:27 +0000 |
| Cc: | |
| Delivery-date: | Thu, 09 Dec 2010 04:57:01 -0800 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=xwe4x40m2TY4x3JZpAP2uyt1n7JT64WLQh3j/g4BjX0=; b=GJPJHBhp/qxn8wCWkuh0FK0Fsrsg7XWD5ykDLxRhv6lOXDA0zMQSfJCQqR1j8/UzBT SvnJ0AGoXEUzuFd5Fn611kWP97sY0xY2ScTWArqgkwEGlA1aDxPcUyA5cMEWX9ezelGq CrpyNCc7ho5oJXZjPD9pp4cm0zy5tSAxdXkO0= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=SxFjlNu0OhZPSxkwuE8LkqAHGmmR9BHFUWp/go65YcTYbYeKsjG60aF00P6CNQolNT jd0D/EETAX3ZI+8sZPC5u7Kh7xCRhTvT9d/M1WI4O0rtqoL7bbG6kx3SMawJF9/bY3zG YERtZwQZqybC/79BPy1YQDms1cmj0mpiKpQLM= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| 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> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Keir, I made a cpu status notifier for sched_credit2() to actually read an arrange the runqueue information, and found the next niggle: the callbacks are not guaranteed to finish before the cpu tried to go through the scheduler. The callback notifiers are handled on the cpu that issues the boot command (i.e., cpu 0 during boot), and there's no interlock to prevent the booted cpu from continuing until the notifiers have completed execution. Making a simple interlock (similar to the one in __cpu_up()) allows the system to boot properly. Another possibility would be to run the notifiers on the freshly booted cpu before calling into the scheduler, rather than on the cpu that issued the cpu boot sequence. Thoughts? -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH 5 of 5] Support new xl command cpupool-numa-split, Juergen Gross |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH 1 of 5] Support getting topology info in libxl, Gianni Tedesco |
| Previous by Thread: | [Xen-devel] How is foreign map invalidated in dom0?, liuw@xxxxxxxxx |
| Next by Thread: | Re: [Xen-devel] CPU and scheduler init, Part 2, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
