Kvm-ia64 Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH RFC v2 0/6] KVM: moving dirty gitmaps to user space!
Date: Tue, 20 Apr 2010 11:13:28 +0000	[thread overview]
Message-ID: <4BCD8C58.5070503@oss.ntt.co.jp> (raw)
In-Reply-To: <20100420195349.dab60b1d.yoshikawa.takuya@oss.ntt.co.jp>

(2010/04/20 19:54), Alexander Graf wrote:
>
> On 20.04.2010, at 12:53, Takuya Yoshikawa wrote:
>
>> Hi, this is the v2 of the "moving dirty gitmaps to user space!"
>>
>> By this patch, I think everything we need becomes clear.
>> So we want to step forward to be ready for the final version in the
>> near future: of course, this is dependent on x86 and ppc asm issues.
>>
>> BTW, by whom I can get ACK for ppc and ia64? I want to add to the Cc
>> list if possible, thank you.
>
> You'd get the ACK for ppc from me.

Thank you, then I will add you to Cc next time!

>
> Do you have a PowerPC box around to test things on? By now it should work on any desktop/server PowerPC system you can find.

Sorry, I have no ppc box here. So at this stage, I am sometimes using cross
compilers to check this can build or not: not enough test now.

And this patch needs arch specific(assembly level) optimization in the future.
So I want to make this development as open as possible.

>
> Also the only differences on PPC are that we are big endian and usually run 32 bit userspace on 64 bit kernels. So playing with longs is a bad idea :).

OK, I'll keep in mind!

>
> Alex
>

   Takuya

  parent reply	other threads:[~2010-04-20 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 10:53 [PATCH RFC v2 0/6] KVM: moving dirty gitmaps to user space! Takuya Yoshikawa
2010-04-20 10:54 ` Alexander Graf
2010-04-20 11:13 ` Takuya Yoshikawa [this message]
2010-04-20 12:05 ` Takuya Yoshikawa

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=4BCD8C58.5070503@oss.ntt.co.jp \
    --to=yoshikawa.takuya@oss.ntt.co.jp \
    --cc=kvm-ia64@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