From: Felipe Alfaro Solana <felipe.alfaro@gmail.com>
To: Linda Luu <linda.luu@comcast.net>
Cc: linux-kernel@vger.kernel.org, "Nguyen,
Nguyen (Home)" <ndnguyen3@comcast.net>
Subject: Re: Multi-core, Vanderpool support?
Date: Tue, 19 Apr 2005 12:13:19 +0200 [thread overview]
Message-ID: <6f6293f105041903134025da80@mail.gmail.com> (raw)
In-Reply-To: <004901c541d9$16b18ad0$6501a8c0@Jaguar>
On 4/15/05, Linda Luu <linda.luu@comcast.net> wrote:
> Hello,
>
> Does anyone happen to know how the upcoming multi-core CPU will be handled
> by the kernel? Does it see each core as a physical or logical CPU or ?
Can't answer this, but I guess each core will be seen as a physical
CPU as they are real CPU cores, not just logical CPUs as with
multithreading.
> Vanderpool is a hardware support for OS virtualization (running multiple OS
> "at the same time"), how does Linux kernel make use of this, particularly
> which part of the kernel code?
At least, Xen will make great use of Vanderpool (VT) for
virtualization purpouses.
prev parent reply other threads:[~2005-04-19 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 16:35 Multi-core, Vanderpool support? Linda Luu
2005-04-15 18:00 ` Chris Wright
2005-04-19 10:13 ` Felipe Alfaro Solana [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=6f6293f105041903134025da80@mail.gmail.com \
--to=felipe.alfaro@gmail.com \
--cc=linda.luu@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ndnguyen3@comcast.net \
/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