From: "H. Peter Anvin" <hpa@zytor.com>
To: Matias <linux@sundmangroup.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Intel x86 Dual Core & Linux AMP
Date: Tue, 13 Jan 2009 10:29:54 -0800 [thread overview]
Message-ID: <496CDDA2.8080206@zytor.com> (raw)
In-Reply-To: <496C8A98.90309@sundmangroup.com>
Matias wrote:
> Is there a way to boot a normal standard home x86 dual core PC with two
> different Linux Kernels without a hypervisor?
> The idea is of course to give the Kernels their own address space and
> their own rootfile systems, the devices would be unique for each kernel
> etc.
>
> Can this be done with a standard BIOS and GRUB/LILO?
No. There are way too many shared resources, such as address space and
interrupt system. You need a central resource to arbitrate those
resources, i.e. a hypervisor.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-01-13 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 12:35 Intel x86 Dual Core & Linux AMP Matias
2009-01-13 18:29 ` H. Peter Anvin [this message]
2009-01-13 18:48 ` Matias
2009-01-13 23:04 ` H. Peter Anvin
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=496CDDA2.8080206@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sundmangroup.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