From: zach@vmware.com
To: akpm@osdl.org, chrisw@osdl.org, linux-kernel@vger.kernel.org,
virtualization@lists.osdl.org, zach@vmware.com
Subject: [PATCH 0/6] i386 virtualization patches, Set 3
Date: Mon, 15 Aug 2005 15:58:09 -0700 [thread overview]
Message-ID: <200508152258.j7FMw9p8005295@zach-dev.vmware.com> (raw)
This round attempts to conclude all of the LDT related cleanup with some
finally nice looking LDT code, fixes for the UML build, a bugfix for
really rather nasty kprobes problems, and the basic framework for an LDT
test suite. It is really rather unfortunate that this code is so
difficult to test, even with DOSemu and Wine, there are still very nasty
corner cases here - anyone want an iret to 16-bit stack test?.
I was going to attempt to clean up the math-emu code to make it use the
nice new segment and descriptor table accessors, but it quickly became
apparent that this would be a long, tedious, error prone process that
would eventually result in the death of a large section of my brain.
In addition, it is not very fun to test this on the actual hardware it
is designed to run on (although I did manage to track down a 386 with
detachable i387 coprocessor, the owner is not sure it still boots).
Someday it would be nice to have an audit of this code; it appears to
be riddled with bugs relating to segmentation, for example it assumes
LDT segments on overrides, does not use the mm->context semaphore to
protect LDT access, and generally looks scarily out of date in both
function and appearance.
I also have a makeover for the pgtable.h code. Splitting operations that
write hardware page tables into the sub-arch layer was very ugly,
hopefully this is a much cleaner approach. There really must be a way
for a paravirtualized hypervisor to hook the page table updates, and this
appears to be the cleanest solution so far.
This patch set is based on 2.6.13-rc6 -mm1 broken out series. It applies
and builds i386, x86_64, and um-i386 on 2.6.13-rc5. I've tested PAE and
non-PAE SMP kernels and am working on an LDT test suite. Depends on
the i386 cleanups, sub-arch movement, and LDT cleanups I've already sent
out.
--
Zachary Amsden <zach@vmware.com>
Whee! Actually deliver the signal.
next reply other threads:[~2005-08-15 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 22:58 zach [this message]
2005-08-15 23:24 ` [PATCH 0/6] i386 virtualization patches, Set 3 Andi Kleen
2005-08-15 23:27 ` David Lang
2005-08-15 23:35 ` Andi Kleen
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=200508152258.j7FMw9p8005295@zach-dev.vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
/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.