Le Lundi 03 Juillet 2006 06:22, Isaku Yamahata a écrit :
This patch allows vcpu to move between pcpus.
I couldn't boot domU on credit scheduler without this patch.
This patch is only for correctness. This patch isn't efficient.
2 comments:
The obvious question is why not using _dirty_cpumask;
On Mon, 2006-07-03 at 13:22 +0900, Isaku Yamahata wrote:
This patch allows vcpu to move between pcpus.
I couldn't boot domU on credit scheduler without this patch.
This patch is only for correctness. This patch isn't efficient.
Applied.
--
Alex Williamson HP
From: Isaku Yamahata
Sent: 2006年7月3日 12:22
Maybe a consideration on VHPT per pcpu is needed.
- allocation of region id per domain.
Should rid region be allocated per vcpu?
If guest allocates RID globally like Linux, per vcpu rid region is difficult
to work. If the higher 6 bit is used as
This patch allows vcpu to move between pcpus.
I couldn't boot domU on credit scheduler without this patch.
This patch is only for correctness. This patch isn't efficient.
Maybe a consideration on VHPT per pcpu is needed.
- allocation of region id per domain.
Should rid region be allocated per
From: Isaku Yamahata
Sent: 2006?7?3? 12:22
To: Tristan Gingold
Cc: xen-ia64-devel@lists.xensource.com
Subject: [PATCH] allow vcpu to move between pcpus (was Re:
[Xen-ia64-devel]credit sched on ia64)
This patch allows vcpu to move between pcpus.
I couldn't boot domU on credit scheduler without
Hi, Tristan,
We(Tazaki and Sakai) are doing vcpu migration test.
Luckily, it works fine Xen/Linux on nonVTI and VTI machine.
Our testing is doing as follows.
1) add TRACE on (insert the TRACE_4D on cshed_runq_steal to check the vcpu
migration)
2) Create 2 domains(U or VTI). We call domain as
Hi
I am maybe late on this issue but has anyone tried credit scheduler on
xen/ia64 ?
I suppose it doesn't work well because we don't support vcpu migration yet.
Tristan.
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
