From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Stable Kernel <stable@kernel.org>
Subject: [GIT PULL] A couple of Xen bugfixes
Date: Wed, 04 Nov 2009 15:44:27 -0800 [thread overview]
Message-ID: <4AF211DB.605@goop.org> (raw)
Hi Linus,
Here's a couple of Xen bugfixes:
* Suppress the extended topology leaf in cpuid; such details are
meaningless in a virtual cpu
* Make hvc_xen poll when the output buffer is full rather than
depend on a workqueue to do it. Otherwise we can lose oops info
on crashes when scheduling has been disabled.
Thanks,
J
The following changes since commit 973df35ed9ff7806403e793a2ad7e9bd4c2fd2a9:
Jeremy Fitzhardinge (1):
xen: set up mmu_ops before trying to set any ptes
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git bugfix
Jeremy Fitzhardinge (2):
xen/hvc: make sure console output is always emitted, with explicit polling
xen: mask extended topology info in cpuid
arch/x86/xen/enlighten.c | 11 ++++++++++-
drivers/char/hvc_xen.c | 25 ++++++++++++++++++++++++-
2 files changed, 34 insertions(+), 2 deletions(-)
reply other threads:[~2009-11-04 23:44 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=4AF211DB.605@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--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