From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: What do we need to do to hit 2.6.19?
Date: Fri, 04 Aug 2006 18:45:07 -0700 [thread overview]
Message-ID: <44D3F823.8000004@goop.org> (raw)
In-Reply-To: <20060804235004.GQ2654@sequoia.sous-sol.org>
Chris Wright wrote:
> I believe this is fixed now, at least it's booting fine on my smp box now.
>
> #define wrmsr_safe(msr,a,b) ({ \
> - u64 _l = ((u64)(a) << 32) | (b); \
> + u64 _l = ((u64)(b) << 32) | (a); \
> paravirt_ops.write_msr((msr),_l); \
> })
>
But, but 'a' is obviously the msw ;-).
Neato. I'll give it a spin later this evening.
J
prev parent reply other threads:[~2006-08-05 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D39351.9070405@goop.org>
2006-08-04 22:14 ` What do we need to do to hit 2.6.19? Andi Kleen
2006-08-04 22:21 ` Chris Wright
2006-08-04 22:38 ` Andi Kleen
2006-08-04 23:50 ` Chris Wright
2006-08-05 1:45 ` Jeremy Fitzhardinge [this message]
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=44D3F823.8000004@goop.org \
--to=jeremy@goop.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).