[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4727D926.6050004@sina.com.cn>
Date: Wed, 31 Oct 2007 09:23:50 +0800
From: tgh <wwwwww4187@...a.com.cn>
To: Jeremy Fitzhardinge <jeremy@...p.org>
CC: Xen-devel <xen-devel@...ts.xensource.com>,
Jeremy Fitzhardinge <jeremy@...source.com>,
lkml <linux-kernel@...r.kernel.org>, Andi Kleen <ak@...e.de>,
Chris Wright <chrisw@...s-sol.org>,
Andrew Morton <akpm@...ux-foundation.com>
Subject: Re: [Xen-devel] [patch 30/44] xen: Add support for preemption
Thank for your reply
and I still have several questions
> Yes, that's the normal mode of operation. The hypervisor will timeslice
> multiple vcpus onto a single vcpu.
>
that is ,the VM could be preempted by xen,and could xen hypervisor also
be preempted to reschedule other vm or xen kernel thread?and are there
the counterpart abstractions in xen for kernel thread in linux?
> This patch doesn't relate to that; it's whether a Xen Linux guest's
> kernel can be preempted to reschedule processes while running under Xen.
>
that is ,the patch makes the guest's kernel, rather than xen, be able to
be preempted ,is it right?
Thanks in advance
> The normal xen-unstable or vendor Xen kernels don't support this, but
> the mainline kernel with paravirt_ops/xen support does.
>
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@...ts.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists