From: Avi Kivity <avi@redhat.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Add KVM support for Book3s_64 (PPC64) hosts v3
Date: Sun, 26 Jul 2009 17:53:22 +0000 [thread overview]
Message-ID: <4A6C9812.4060306@redhat.com> (raw)
In-Reply-To: <1248453028-49627-1-git-send-email-agraf@suse.de>
On 07/26/2009 08:25 PM, Alexander Graf wrote:
>>>
>>>>> Perhaps we can get away with disabling 32-on-64 for the
>>>>> configurations that break to start with.
>>>>
>>>> 32-on-64 only breaks for big endian which nobody except for this
>>>> target implements. Since my PPC enabling patches for qemu change
>>>> the type to uint64_t always, nobody is broken right now.
>>>>
>>>
>>> That assumes you implement set_bit_u64(), no?
>>
>> No, little endian works as-is :-).
>
>
> Let me rephrase: It shouldn't if I understand little endian correctly :).
>
> I haven't actually verified that 32 on 64 doesn't break. But then
> again that's a rather uncommon configuration for x86 anyways, but
> really common on ppc.
I meant disable 32-on-64 ppc. 32-on-64 x86 is supported and works
(though it is rare).
Given that you say 32-on-64 ppc is common, it could only be a short term
fix until we implemlement u64 bitops. Alternatively we can mangle the
bitmap when copying it to userspace.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-07-26 17:53 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 [this message]
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
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=4A6C9812.4060306@redhat.com \
--to=avi@redhat.com \
--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