From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.com>
Cc: Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] xen: fixes for 2.6.30-rc4
Date: Thu, 07 May 2009 11:56:23 -0700 [thread overview]
Message-ID: <4A032ED7.1030800@goop.org> (raw)
Hi Linus,
This series of patches are bugfixes for Xen for 2.6.30. They are:
xen/x86-64: fix breakpoints and hardware watchpoints
xen/x86-64: clean up warnings about IST-using traps
xen: deal with NMI's use of IST too
Fix breakpoints and watchpoints on x86-64. When running native,
breakpoints and watchpoints use the IST mechanism to run on a
separate interrupt stack. Xen doesn't support this, and just delivers
the interrupts normally. These patches special-case the IST-using
interrupts we care about under Xen to use a separate trap gate which
expects a standard stack layout. The second patch prints warnings if
any other IST-using traps arise in the future.
xen/i386: reserve Xen pagetables
xen: reserve Xen start_info rather than e820 reserving
Reserve the Xen-provided pagetables on i386. Previously this was
done implicitly because they happened to be in the memory range
reserved by something else, but that was cleaned up so we need to
do it explicitly. Also, use reserve_early() rather than an e820
reserved region, so there's some documentation in the kernel boot
log.
diff stat:
arch/x86/include/asm/traps.h | 2 ++
arch/x86/kernel/entry_64.S | 4 ++++
arch/x86/xen/enlighten.c | 36 +++++++++++++++++++++++++++++++++++-
arch/x86/xen/mmu.c | 5 +++++
arch/x86/xen/setup.c | 6 +++---
5 files changed, 49 insertions(+), 4 deletions(-)
Thanks,
J
reply other threads:[~2009-05-07 18:57 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=4A032ED7.1030800@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox