From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: [GIT PULL] Xen updates
Date: Mon, 22 Nov 2010 12:31:03 -0800 [thread overview]
Message-ID: <4CEAD307.50409@goop.org> (raw)
Hi Linus,
Some more Xen-related bugfixes, including:
* Xen evtchn driver fixes, including fixing some locking fixes, and
giving it a more standard name
* Xen xenfs updates, including removing a bogus address space (when
really we needed VM_PFNMAP) and fixing the prototype for mount
* fix 32-on-64 dom0 booting, and make sure IO port permissions are
enabled early to fix booting on AMD systems
* make sure the balloon driver only claims E820_RAM pages
Available at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/for-linus
Bastian Blank (1):
xen/evtchn: Fix name of Xen event-channel device
Ian Campbell (2):
xen: implement XENMEM_machphys_mapping
xen: make evtchn's name less generic
Jan Beulich (1):
xen/evtchn: clear secondary CPUs' cpu_evtchn_mask[] after restore
Jeremy Fitzhardinge (17):
xen/evtchn: track enabled state for each port
xen/evtchn: dynamically allocate port_user array
xen/evtchn: ports start enabled
xen/evtchn: remove spurious barrier
xen/evtchn: don't do unbind_from_irqhandler under spinlock
xen/evtchn: add missing static
Merge commit 'v2.6.37-rc2' into upstream/xenfs
xen/xenfs: update xenfs_mount for new prototype
xen/events: use locked set|clear_bit() for cpu_evtchn_mask
Revert "xen/privcmd: create address space to allow writable mmaps"
xen/evtchn: the evtchn device is non-seekable
Merge branch 'xen/dev-evtchn' into upstream/evtchn
xen: add extra pages to balloon
xen/balloon: the balloon_lock is useless
xen/balloon: make sure we only include remaining extra ram
xen: re-enable boot-time ballooning
Merge branches 'upstream/core', 'upstream/xenfs' and 'upstream/evtchn' into upstream/for-linus
Konrad Rzeszutek Wilk (2):
xen: set IO permission early (before early_cpu_init())
xen/events: Use PIRQ instead of GSI value when unmapping MSI/MSI-X irqs.
Randy Dunlap (1):
xen: fix header export to userspace
Stefano Stabellini (1):
xen: set vma flag VM_PFNMAP in the privcmd mmap file_op
Vasiliy Kulikov (1):
xen: xenfs: privcmd: check put_user() return code
arch/x86/include/asm/xen/interface.h | 6 +-
arch/x86/include/asm/xen/interface_32.h | 5 ++
arch/x86/include/asm/xen/interface_64.h | 13 +----
arch/x86/include/asm/xen/page.h | 7 +-
arch/x86/xen/enlighten.c | 19 ++++++-
arch/x86/xen/mmu.c | 17 +++++-
arch/x86/xen/setup.c | 11 +---
drivers/xen/Makefile | 5 +-
drivers/xen/balloon.c | 32 +++++-----
drivers/xen/events.c | 13 +++--
drivers/xen/evtchn.c | 100 +++++++++++++++++++++++-------
drivers/xen/xenfs/privcmd.c | 13 ++---
drivers/xen/xenfs/super.c | 46 ++------------
include/xen/interface/memory.h | 13 ++++
include/xen/page.h | 7 ++
include/xen/privcmd.h | 5 +-
16 files changed, 186 insertions(+), 126 deletions(-)
Thanks,
J
next reply other threads:[~2010-11-22 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 20:31 Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-26 23:45 [GIT PULL] Xen updates Jeremy Fitzhardinge
2010-08-04 22:15 Jeremy Fitzhardinge
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=4CEAD307.50409@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.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