From: Jeremy Fitzhardinge <jeremy@goop.org>
To: tgh <wwwwww4187@sina.com.cn>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Andi Kleen <ak@suse.de>, lkml <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [Xen-devel] [patch 30/44] xen: Add support for preemption
Date: Wed, 31 Oct 2007 08:07:43 -0700 [thread overview]
Message-ID: <47289A3F.4040608@goop.org> (raw)
In-Reply-To: <47281C75.4040106@sina.com.cn>
tgh wrote:
> Thank you for your reply
> and what about the kernel thread in the xen hypervisor,are there some
> instance of kernel threads running in the hypervisor?
> I am not sure ,but somewhere I read that there is no kernel thread in
> the xen hypervisor ,is it true or what about it?
>
No, there are no linux kernel threads in the hypervisor. The only
thread-like thing Xen has is a virtual CPU, and they're always guest
domain vcpus.
J
prev parent reply other threads:[~2007-10-31 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070716231536.937393000@xensource.com>
[not found] ` <20070716232912.409821000@xensource.com>
2007-07-17 0:41 ` [Xen-devel] [patch 03/44] usermodehelper: split setup from execution Rusty Russell
2007-07-17 0:57 ` Jeremy Fitzhardinge
[not found] ` <20070716232914.029797000@xensource.com>
2007-07-17 0:45 ` [Xen-devel] [patch 17/44] Add nosegneg capability to the vsyscall page notes Rusty Russell
2007-07-17 1:04 ` Jeremy Fitzhardinge
[not found] ` <20070716232916.472694000@xensource.com>
2007-07-17 1:07 ` [patch 37/44] xen: add virtual network device driver Jeff Garzik
2007-07-17 8:45 ` Stephen Hemminger
2007-07-17 14:28 ` Jeremy Fitzhardinge
2007-07-17 23:45 ` Rusty Russell
2007-07-18 0:40 ` Jeremy Fitzhardinge
[not found] ` <20070716232915.672717000@xensource.com>
2007-10-30 9:10 ` [Xen-devel] [patch 30/44] xen: Add support for preemption tgh
2007-10-30 17:25 ` Jeremy Fitzhardinge
2007-10-31 1:23 ` tgh
2007-10-31 1:38 ` Jeremy Fitzhardinge
2007-10-31 6:11 ` tgh
2007-10-31 15:07 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47289A3F.4040608@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wwwwww4187@sina.com.cn \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox