From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] Xen internal cleanup stuff
Date: Thu, 26 May 2011 14:36:25 -0700 [thread overview]
Message-ID: <4DDEC7D9.1090604@goop.org> (raw)
Hi Linus,
Please pull:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/tidy-xen-mmu-2.6.39
Jeremy Fitzhardinge (10):
xen: drop all the special iomap pte paths.
xen: use mmu_update for xen_set_pte_at()
xen: condense everything onto xen_set_pte
vmalloc: remove vmalloc_sync_all() from alloc_vm_area()
xen: make a pile of mmu pvop functions static
xen: use normal virt_to_machine for ptes
xen/mmu: remove all ad-hoc stats stuff
Use arbitrary_virt_to_machine() to deal with ioremapped pmd updates.
Use arbitrary_virt_to_machine() to deal with ioremapped pud updates.
xen: fix compile without CONFIG_XEN_DEBUG_FS
arch/x86/xen/mmu.c | 284 +++++++++------------------------------------------
arch/x86/xen/mmu.h | 37 -------
mm/vmalloc.c | 4 -
3 files changed, 50 insertions(+), 275 deletions(-)
This is all Xen-internal cleanup stuff. The change to mm/vmalloc.c is
to remove a pointless vmalloc_sync_all() from alloc_vm_area().
alloc_vm_area() is only called by Xen code, though there's nothing
Xen-specific about it.
Thanks,
J
reply other threads:[~2011-05-26 21:36 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=4DDEC7D9.1090604@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=akpm@linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).