From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] some core Xen updates
Date: Mon, 09 Feb 2009 11:35:45 -0800 [thread overview]
Message-ID: <49908591.5020406@goop.org> (raw)
Hi Ingo,
Here's some core Xen changes: bug fixes, debuggability improvements and cleanups.
These are based on tip/x86/xen, but I've merged in tip/master to bring it up to date
before adding my changes.
BTW, I killed off all the jsgf/* branches in xen.git, but I think you've either
already picked up all the push requests, or I'll resend anything missing.
Thanks,
J
The following changes since commit a1c51abb06bf03bef6ff973e43cf20a0fa48384f:
Ingo Molnar (1):
Merge branch 'x86/urgent'
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/core
Ian Campbell (2):
Fix xen_flush_tlb_others
xen: record and display initiator of each multicall when debugging
Jeremy Fitzhardinge (5):
Merge remote branch 'tip/master' into tip/fixups
xen: short-circuit tests for dom0
xen: degrade BUG to WARN when multicall fails
xen: do multicall callbacks with interrupts disabled
Merge branch 'tip/fixups' into xen/core
arch/x86/include/asm/xen/hypervisor.h | 28 ++++++++++++++++++----------
arch/x86/xen/mmu.c | 3 ---
arch/x86/xen/multicalls.c | 15 ++++++++++-----
3 files changed, 28 insertions(+), 18 deletions(-)
next reply other threads:[~2009-02-09 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 19:35 Jeremy Fitzhardinge [this message]
2009-02-14 8:26 ` [GIT PULL] some core Xen updates Jeremy Fitzhardinge
2009-02-16 7:57 ` Ingo Molnar
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=49908591.5020406@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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 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.