From: Andi Kleen <ak@suse.de>
To: David Lang <david.lang@digitalinsight.com>
Cc: Andi Kleen <ak@suse.de>,
zach@vmware.com, akpm@osdl.org, chrisw@osdl.org,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [PATCH 0/6] i386 virtualization patches, Set 3
Date: Tue, 16 Aug 2005 01:35:30 +0200 [thread overview]
Message-ID: <20050815233529.GG20749@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0508151626290.24315@qynat.qvtvafvgr.pbz>
> you are forgetting about the embedded market, there 386 cpu (or things
> that look like 386 cpu's) are still available.
They cannot use it much though because the code is obviously in so
bad shape. Perhaps they have all FPUs ? Ok given LDT usage
is rare, but still there are probably lots of other bugs
in that unmaintained code too.
-Andi
next prev parent reply other threads:[~2005-08-15 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 22:58 [PATCH 0/6] i386 virtualization patches, Set 3 zach
2005-08-15 23:24 ` Andi Kleen
2005-08-15 23:27 ` David Lang
2005-08-15 23:35 ` Andi Kleen [this message]
2005-08-16 3:08 ` Brian Gerst
2005-08-16 3:33 ` Zachary Amsden
2005-08-16 7:44 ` Chris Wright
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=20050815233529.GG20749@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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