From: Zachary Amsden <zach@vmware.com>
To: Christoph Hellwig <hch@infradead.org>,
Zachary Amsden <zach@vmware.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Andrew Morton <akpm@osdl.org>, Dan Hecht <dhecht@vmware.com>,
Dan Arai <arai@vmware.com>, Anne Holler <anne@vmware.com>,
Pratap Subrahmanyam <pratap@vmware.com>,
Christopher Li <chrisl@vmware.com>,
Joshua LeVasseur <jtl@ira.uka.de>, Chris Wright <chrisw@osdl.org>,
Rik Van Riel <riel@redhat.com>, Jyothy Reddy <jreddy@vmware.com>,
Jack Lo <jlo@vmware.com>, Kip Macy <kmacy@fsmware.com>,
Jan Beulich <jbeulich@novell.com>,
Ky Srinivasan <ksrinivasan@novell.com>,
Wim Coekaerts <wim.coekaerts@oracle.com>,
Leendert van Doorn <leendert@watson.ibm.com>
Subject: Re: [RFC, PATCH 2/24] i386 Vmi config
Date: Tue, 14 Mar 2006 07:55:03 -0800 [thread overview]
Message-ID: <4416E757.9040208@vmware.com> (raw)
In-Reply-To: <20060314152350.GB16921@infradead.org>
Christoph Hellwig wrote:
> On Mon, Mar 13, 2006 at 10:00:27AM -0800, Zachary Amsden wrote:
>
>> Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only
>> are designed to run on modern hardware platforms. As such, they require a
>> working APIC, and do not support some legacy functionality, including APM BIOS,
>> ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of
>> dropping ISA support). They also require a P6 series CPU.
>>
>
> That's pretty bad because distributors need another kernel still. At least
> a working APIC isn't quite as common today as it should.
>
It doesn't need to be a fully functional APIC. It just needs to not
have one particular bug - Pentium processor erratum 11AP. There is no
reason that most of these requirements can't be dropped. We used to
have a lot more functionality and legacy support turned off, and we
gradually turned it back on. Turning on the BIOS interfaces will cause
complications for a VMI kernel running in a hypervisor - since it can't
invoke non-virtualized BIOS code. So it does require a bit of
conditional logic, which is pretty easy, but we haven't got around to
doing yet.
Zach
next prev parent reply other threads:[~2006-03-14 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 18:00 [RFC, PATCH 2/24] i386 Vmi config Zachary Amsden
2006-03-13 18:00 ` Zachary Amsden
2006-03-13 20:23 ` Sam Vilain
2006-03-14 15:23 ` Christoph Hellwig
2006-03-14 15:55 ` Zachary Amsden [this message]
2006-03-16 19:04 ` Jan Engelhardt
2006-03-16 21:45 ` Zachary Amsden
2006-03-15 22:39 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 18:41 Zachary Amsden
2006-03-13 18:41 ` Zachary Amsden
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=4416E757.9040208@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=anne@vmware.com \
--cc=arai@vmware.com \
--cc=chrisl@vmware.com \
--cc=chrisw@osdl.org \
--cc=dhecht@vmware.com \
--cc=hch@infradead.org \
--cc=jbeulich@novell.com \
--cc=jlo@vmware.com \
--cc=jreddy@vmware.com \
--cc=jtl@ira.uka.de \
--cc=kmacy@fsmware.com \
--cc=ksrinivasan@novell.com \
--cc=leendert@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pratap@vmware.com \
--cc=riel@redhat.com \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=wim.coekaerts@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.