From: Zachary Amsden <zach@vmware.com>
To: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zachary Amsden <zach@vmware.com>
Subject: [PATCH 0/10] i386, VMI, BusLogic, Timer fixes for -mm
Date: Mon, 9 Apr 2007 17:05:43 -0700 [thread overview]
Message-ID: <200704100005.l3A05hpp020590@zach-dev.vmware.com> (raw)
Latest cleanups and junk from Zach's tree. All for -mm tree.
Based off Jeremy's latest known applied patches. If the
paravirt or VMI patches reject let me know; we are cleaning up
tree and will redo.
Otherwise, I have 4 fixes for i386; a warning fix in sysenter
which is quite serious; some less important warning removals,
and a bug with pgd locking during root creation.
Next, I tidy up the kmap_atomic_pte code, since it makes no
sense to leave it around under !HIGHMEM and being forced to
define it introduces conflicts with where things get defined
that just is ugly.
Some VMI fixes; we support COMPAT_VDSO now that the relocation
code is there, re-add the lazy MMU fix now that Jeremy's cleanups
have been applied to -mm, implement kmap_atomic_pte.
Next, re-implement the VMI timer, dropping all the NO_IDLE_HZ
code, making it dependent on NO_HZ and using the proper clockevents
infrastructure. I am looking for feedback on this, but it works
and applies as is, and is certainly better and cleaner than the
existing code. Hopefully I have taken as many fingers out of the
APIC pie as possible.
Finally, fix the BusLogic driver to use request_range properly.
Zach
reply other threads:[~2007-04-10 0:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200704100005.l3A05hpp020590@zach-dev.vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).