lguest uses tasks to control its running behaviour (like sending
breaks, controlling halted state, etc). In a per-vcpu environment,
each vcpu will have its own underlying task. So this patch
makes the infrastructure for that possible
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
lguest uses tasks to control its running behaviour (like sending
breaks, controlling halted state, etc). In a per-vcpu environment,
each vcpu will have its own underlying task. So this patch
makes the infrastructure for that possible
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
On Friday 21 December 2007 00:33:53 Glauber de Oliveira Costa wrote:
> @@ -114,6 +116,19 @@ static int vcpu_start(struct lguest_vcpu *vcpu, int
> vcpu_id, * address. */
> lguest_arch_setup_regs(vcpu, start_ip);
>
> + /* Initialize the queue for the waker to wait on */
> +
On Friday 21 December 2007 00:33:53 Glauber de Oliveira Costa wrote:
@@ -114,6 +116,19 @@ static int vcpu_start(struct lguest_vcpu *vcpu, int
vcpu_id, * address. */
lguest_arch_setup_regs(vcpu, start_ip);
+ /* Initialize the queue for the waker to wait on */
+
lguest uses tasks to control its running behaviour (like sending
breaks, controlling halted state, etc). In a per-vcpu environment,
each vcpu will have its own underlying task. So this patch
makes the infrastructure for that possible
Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
lguest uses tasks to control its running behaviour (like sending
breaks, controlling halted state, etc). In a per-vcpu environment,
each vcpu will have its own underlying task. So this patch
makes the infrastructure for that possible
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
6 matches
Mail list logo
