From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: [PATCH v1] Various bug-fixes for v3.6.
Date: Wed, 10 Oct 2012 13:40:46 -0400 [thread overview]
Message-ID: <1349890849-17471-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey,
Three patches that were discovered with v3.6. The first one:
[PATCH 1/3] xen/pv-on-hvm kexec: add quirk for Xen 3.4 and shutdown
should have been found earlier, but it seems there is only a small selection
of provides run Xen 3.4 and without the 23839:42a45baf037d in xen-unstable.hg fix.
It is easy to reproduce with OVM 2.2 product.
The other two are a bit embarrassing. We had a similar issue with rdmsr_safe
pvops call in v3.5 where it was not implemented for Xen PV (but rdmsr was).
The fix was to make rdmsr_safe a macro around rdmsr and a lookout for other
calls that were not implemented. Well, v3.6 has gone by and now I find three other
culprits:
[PATCH 2/3] xen/bootup: allow {read|write}_cr8 pvops call.
[PATCH 3/3] xen/bootup: allow read_tscp call for Xen PV guests.
next reply other threads:[~2012-10-10 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 17:40 Konrad Rzeszutek Wilk [this message]
2012-10-10 17:40 ` [PATCH 1/3] xen/pv-on-hvm kexec: add quirk for Xen 3.4 and shutdown watches Konrad Rzeszutek Wilk
2012-10-10 18:09 ` Olaf Hering
2012-10-15 16:05 ` [Xen-devel] " Ian Campbell
2012-10-15 16:14 ` Ian Campbell
2012-10-15 16:09 ` Konrad Rzeszutek Wilk
2012-10-10 17:40 ` [PATCH 2/3] xen/bootup: allow {read|write}_cr8 pvops call Konrad Rzeszutek Wilk
2012-10-10 17:40 ` [PATCH 3/3] xen/bootup: allow read_tscp call for Xen PV guests Konrad Rzeszutek Wilk
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=1349890849-17471-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®