From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Add KVM support for Book3s_64 (PPC64) hosts v3
Date: Sun, 26 Jul 2009 22:11:07 +0000 [thread overview]
Message-ID: <1248646267.28464.12.camel@pasglop> (raw)
In-Reply-To: <1248453028-49627-1-git-send-email-agraf@suse.de>
On Sun, 2009-07-26 at 22:47 +0200, Alexander Graf wrote:
> When we just interpret the bitmap as u64* do we break 32 on 64 x86? If
> not, that makes it work for 32 on 64 ppc, because the kernel is always
> 64.
It just a matter of having the bits in the right place. The kernel will
not always be 64-bit though, for example it's no for kvm/e500 or kvm/440
and there's no reason those could get gfx at some stage.
Now, the kernel -does- provide _le variants of the bitops, and those
have the side advantage of being agnostic to 32 vs. 64 bit so maybe that
what we should use everywhere ?
Look at ppc's bitops.h, it has nice descriptions of the format.
Cheers,
Ben.
next prev parent reply other threads:[~2009-07-26 22:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 16:30 [GIT PULL] Add KVM support for Book3s_64 (PPC64) hosts v3 Alexander Graf
2009-07-26 11:52 ` Avi Kivity
2009-07-26 11:55 ` Alexander Graf
2009-07-26 12:10 ` Avi Kivity
2009-07-26 12:26 ` Alexander Graf
2009-07-26 12:46 ` Avi Kivity
2009-07-26 12:46 ` Alexander Graf
2009-07-26 12:54 ` Alexander Graf
2009-07-26 12:56 ` Avi Kivity
2009-07-26 17:25 ` Alexander Graf
2009-07-26 17:53 ` Avi Kivity
2009-07-26 20:47 ` Alexander Graf
2009-07-26 22:04 ` Benjamin Herrenschmidt
2009-07-26 22:05 ` Benjamin Herrenschmidt
2009-07-26 22:06 ` Benjamin Herrenschmidt
2009-07-26 22:11 ` Benjamin Herrenschmidt [this message]
2009-07-27 19:04 ` Hollis Blanchard
2009-07-27 23:43 ` Benjamin Herrenschmidt
2009-07-29 10:14 ` Avi Kivity
2009-07-29 10:15 ` Avi Kivity
2009-09-02 5:40 ` Benjamin Herrenschmidt
2009-09-02 6:16 ` Alexander Graf
2009-09-02 6:23 ` Benjamin Herrenschmidt
2009-09-02 6:34 ` Alexander Graf
2009-09-02 6:52 ` Benjamin Herrenschmidt
2009-09-02 15:21 ` Hollis Blanchard
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=1248646267.28464.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.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