All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit
Date: Tue, 04 May 2010 16:08:23 +0000	[thread overview]
Message-ID: <4BE04677.4060608@redhat.com> (raw)
In-Reply-To: <20100504220500.7695cd66.takuya.yoshikawa@gmail.com>

On 05/04/2010 06:03 PM, Arnd Bergmann wrote:
> On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
>    
>> Although we can use *_le_bit() helpers to treat bitmaps le arranged,
>> having le bit offset calculation as a seperate macro gives us more freedom.
>>
>> For example, KVM has le arranged dirty bitmaps for VGA, live-migration
>> and they are used in user space too. To avoid bitmap copies between kernel
>> and user space, we want to update the bitmaps in user space directly.
>> To achive this, le bit offset with *_user() functions help us a lot.
>>
>> So let us use the le bit offset calculation part by defining it as a new
>> macro: generic_le_bit_offset() .
>>      
> Does this work correctly if your user space is 32 bits (i.e. unsigned long
> is different size in user space and kernel) in both big- and little-endian
> systems?
>
> I'm not sure about all the details, but I think you cannot in general share
> bitmaps between user space and kernel because of this.
>    

That's why the bitmaps are defined as little endian u64 aligned, even on 
big endian 32-bit systems.  Little endian bitmaps are wordsize agnostic, 
and u64 alignment ensures we can use long-sized bitops on mixed size 
systems.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>,
	mtosatti@redhat.com, agraf@suse.de,
	yoshikawa.takuya@oss.ntt.co.jp, fernando@oss.ntt.co.jp,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	kvm-ia64@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, benh@kernel.crashing.org,
	paulus@samba.org, linuxppc-dev@ozlabs.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit
Date: Tue, 04 May 2010 16:08:23 +0000	[thread overview]
Message-ID: <4BE04677.4060608@redhat.com> (raw)
In-Reply-To: <201005041703.00549.arnd@arndb.de>

On 05/04/2010 06:03 PM, Arnd Bergmann wrote:
> On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
>    
>> Although we can use *_le_bit() helpers to treat bitmaps le arranged,
>> having le bit offset calculation as a seperate macro gives us more freedom.
>>
>> For example, KVM has le arranged dirty bitmaps for VGA, live-migration
>> and they are used in user space too. To avoid bitmap copies between kernel
>> and user space, we want to update the bitmaps in user space directly.
>> To achive this, le bit offset with *_user() functions help us a lot.
>>
>> So let us use the le bit offset calculation part by defining it as a new
>> macro: generic_le_bit_offset() .
>>      
> Does this work correctly if your user space is 32 bits (i.e. unsigned long
> is different size in user space and kernel) in both big- and little-endian
> systems?
>
> I'm not sure about all the details, but I think you cannot in general share
> bitmaps between user space and kernel because of this.
>    

That's why the bitmaps are defined as little endian u64 aligned, even on 
big endian 32-bit systems.  Little endian bitmaps are wordsize agnostic, 
and u64 alignment ensures we can use long-sized bitops on mixed size 
systems.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, x86@kernel.org, kvm@vger.kernel.org,
	kvm-ia64@vger.kernel.org, fernando@oss.ntt.co.jp,
	mtosatti@redhat.com, agraf@suse.de, kvm-ppc@vger.kernel.org,
	linux-kernel@vger.kernel.org, yoshikawa.takuya@oss.ntt.co.jp,
	linuxppc-dev@ozlabs.org, mingo@redhat.com, paulus@samba.org,
	hpa@zytor.com, tglx@linutronix.de,
	Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Subject: Re: [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro
Date: Tue, 04 May 2010 19:08:23 +0300	[thread overview]
Message-ID: <4BE04677.4060608@redhat.com> (raw)
In-Reply-To: <201005041703.00549.arnd@arndb.de>

On 05/04/2010 06:03 PM, Arnd Bergmann wrote:
> On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
>    
>> Although we can use *_le_bit() helpers to treat bitmaps le arranged,
>> having le bit offset calculation as a seperate macro gives us more freedom.
>>
>> For example, KVM has le arranged dirty bitmaps for VGA, live-migration
>> and they are used in user space too. To avoid bitmap copies between kernel
>> and user space, we want to update the bitmaps in user space directly.
>> To achive this, le bit offset with *_user() functions help us a lot.
>>
>> So let us use the le bit offset calculation part by defining it as a new
>> macro: generic_le_bit_offset() .
>>      
> Does this work correctly if your user space is 32 bits (i.e. unsigned long
> is different size in user space and kernel) in both big- and little-endian
> systems?
>
> I'm not sure about all the details, but I think you cannot in general share
> bitmaps between user space and kernel because of this.
>    

That's why the bitmaps are defined as little endian u64 aligned, even on 
big endian 32-bit systems.  Little endian bitmaps are wordsize agnostic, 
and u64 alignment ensures we can use long-sized bitops on mixed size 
systems.

-- 
error compiling committee.c: too many arguments to function

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>,
	mtosatti@redhat.com, agraf@suse.de,
	yoshikawa.takuya@oss.ntt.co.jp, fernando@oss.ntt.co.jp,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
	kvm-ia64@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, benh@kernel.crashing.org,
	paulus@samba.org, linuxppc-dev@ozlabs.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro
Date: Tue, 04 May 2010 19:08:23 +0300	[thread overview]
Message-ID: <4BE04677.4060608@redhat.com> (raw)
Message-ID: <20100504160823.7H4UXZcZ3-cpV_J9LpkRxokzHXrbSfa9pd_pCh0PI5w@z> (raw)
In-Reply-To: <201005041703.00549.arnd@arndb.de>

On 05/04/2010 06:03 PM, Arnd Bergmann wrote:
> On Tuesday 04 May 2010, Takuya Yoshikawa wrote:
>    
>> Although we can use *_le_bit() helpers to treat bitmaps le arranged,
>> having le bit offset calculation as a seperate macro gives us more freedom.
>>
>> For example, KVM has le arranged dirty bitmaps for VGA, live-migration
>> and they are used in user space too. To avoid bitmap copies between kernel
>> and user space, we want to update the bitmaps in user space directly.
>> To achive this, le bit offset with *_user() functions help us a lot.
>>
>> So let us use the le bit offset calculation part by defining it as a new
>> macro: generic_le_bit_offset() .
>>      
> Does this work correctly if your user space is 32 bits (i.e. unsigned long
> is different size in user space and kernel) in both big- and little-endian
> systems?
>
> I'm not sure about all the details, but I think you cannot in general share
> bitmaps between user space and kernel because of this.
>    

That's why the bitmaps are defined as little endian u64 aligned, even on 
big endian 32-bit systems.  Little endian bitmaps are wordsize agnostic, 
and u64 alignment ensures we can use long-sized bitops on mixed size 
systems.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-05-04 16:08 UTC|newest]

Thread overview: 175+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 13:05 [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
2010-05-04 13:05 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Takuya Yoshikawa
2010-05-04 13:05 ` Takuya Yoshikawa
2010-05-04 13:05 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
2010-05-04 15:03 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Arnd Bergmann
2010-05-04 15:03   ` Arnd Bergmann
2010-05-04 15:03   ` Arnd Bergmann
2010-05-04 15:03   ` Arnd Bergmann
2010-05-04 16:08 ` Avi Kivity [this message]
2010-05-04 16:08   ` Avi Kivity
2010-05-04 16:08   ` Avi Kivity
2010-05-04 16:08   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Avi Kivity
2010-05-05  2:59 ` Takuya Yoshikawa
2010-05-05  2:59   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Takuya Yoshikawa
2010-05-05  2:59   ` Takuya Yoshikawa
2010-05-05  2:59   ` Takuya Yoshikawa
2010-05-05  2:59   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
2010-05-06 13:38 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Arnd Bergmann
2010-05-06 13:38   ` Arnd Bergmann
2010-05-06 13:38   ` Arnd Bergmann
2010-05-06 13:38   ` Arnd Bergmann
2010-05-06 13:38   ` Arnd Bergmann
2010-05-10 11:46 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
2010-05-10 11:46   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Takuya Yoshikawa
2010-05-10 11:46   ` Takuya Yoshikawa
2010-05-10 11:46   ` Takuya Yoshikawa
2010-05-10 11:46   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
2010-05-10 12:01 ` Avi Kivity
2010-05-10 12:01   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Avi Kivity
2010-05-10 12:01   ` Avi Kivity
2010-05-10 12:01   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Avi Kivity
2010-05-10 12:01 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Arnd Bergmann
2010-05-10 12:01   ` Arnd Bergmann
2010-05-10 12:01   ` Arnd Bergmann
2010-05-10 12:01   ` Arnd Bergmann
2010-05-10 12:01   ` Arnd Bergmann
2010-05-10 12:09 ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
2010-05-10 12:09   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit offset macro Takuya Yoshikawa
2010-05-10 12:09   ` Takuya Yoshikawa
2010-05-10 12:09   ` Takuya Yoshikawa
2010-05-10 12:09   ` [RFC][PATCH resend 8/12] asm-generic: bitops: introduce le bit Takuya Yoshikawa
  -- strict thread matches above, loose matches on Subject: below --
2010-05-24  7:05 Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving Takuya Yoshikawa
2010-05-24  7:05 ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-05-24  7:05 ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving Takuya Yoshikawa
2010-06-01 10:55 ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: Marcelo Tosatti
2010-06-01 10:55   ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Marcelo Tosatti
2010-06-01 10:55   ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: Marcelo Tosatti
2010-06-01 12:05 ` Takuya Yoshikawa
2010-06-01 12:05   ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-06-01 12:05   ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: Takuya Yoshikawa
2010-06-01 12:54 ` Marcelo Tosatti
2010-06-01 12:54   ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Marcelo Tosatti
2010-06-01 12:54   ` Any comments? Re: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: Marcelo Tosatti
2010-05-04 13:11 [RFC][PATCH 12/12 sample] qemu-kvm: use new API for Takuya Yoshikawa
2010-05-04 13:11 ` [RFC][PATCH 12/12 sample] qemu-kvm: use new API for getting/switching dirty bitmaps Takuya Yoshikawa
2010-05-04 13:11 ` Takuya Yoshikawa
2010-05-04 13:11 ` [RFC][PATCH 12/12 sample] qemu-kvm: use new API for Takuya Yoshikawa
2010-05-04 13:08 [RFC][PATCH 11/12] KVM: introduce new API for getting/switching Takuya Yoshikawa
2010-05-04 13:08 ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching dirty bitmaps Takuya Yoshikawa
2010-05-04 13:08 ` Takuya Yoshikawa
2010-05-04 13:08 ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching Takuya Yoshikawa
2010-05-11  3:43 ` Marcelo Tosatti
2010-05-11  3:43   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching dirty bitmaps Marcelo Tosatti
2010-05-11  3:43   ` Marcelo Tosatti
2010-05-11  3:43   ` Marcelo Tosatti
2010-05-11  3:43   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching Marcelo Tosatti
2010-05-11  5:53 ` Takuya Yoshikawa
2010-05-11  5:53   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching dirty bitmaps Takuya Yoshikawa
2010-05-11  5:53   ` Takuya Yoshikawa
2010-05-11  5:53   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching Takuya Yoshikawa
2010-05-11 14:07 ` Marcelo Tosatti
2010-05-11 14:07   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching dirty bitmaps Marcelo Tosatti
2010-05-11 14:07   ` Marcelo Tosatti
2010-05-11 14:07   ` Marcelo Tosatti
2010-05-11 14:07   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching Marcelo Tosatti
2010-05-12  5:59 ` Takuya Yoshikawa
2010-05-12  6:03   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching dirty bitmaps Takuya Yoshikawa
2010-05-12  6:03   ` Takuya Yoshikawa
2010-05-12  6:03   ` [RFC][PATCH 11/12] KVM: introduce new API for getting/switching Takuya Yoshikawa
2010-05-04 13:07 [RFC][PATCH RFC 10/12] KVM: move dirty bitmaps to user space Takuya Yoshikawa
2010-05-04 13:07 ` Takuya Yoshikawa
2010-05-04 13:07 ` Takuya Yoshikawa
2010-05-04 13:07 ` Takuya Yoshikawa
2010-05-11  3:28 ` Marcelo Tosatti
2010-05-11  3:28   ` Marcelo Tosatti
2010-05-11  3:28   ` Marcelo Tosatti
2010-05-11  3:28   ` Marcelo Tosatti
2010-05-11  3:28   ` Marcelo Tosatti
2010-05-12  6:27 ` Takuya Yoshikawa
2010-05-12  6:27   ` Takuya Yoshikawa
2010-05-12  6:27   ` Takuya Yoshikawa
2010-05-12  6:27   ` Takuya Yoshikawa
2010-05-13 11:05 ` Takuya Yoshikawa
2010-05-13 11:05   ` Takuya Yoshikawa
2010-05-13 11:05   ` Takuya Yoshikawa
2010-05-04 13:06 [RFC][PATCH 9/12] KVM: introduce a wrapper function of Takuya Yoshikawa
2010-05-04 13:06 ` [RFC][PATCH 9/12] KVM: introduce a wrapper function of set_bit_user_non_atomic() Takuya Yoshikawa
2010-05-04 13:06 ` Takuya Yoshikawa
2010-05-04 13:06 ` Takuya Yoshikawa
2010-05-04 13:06 ` [RFC][PATCH 9/12] KVM: introduce a wrapper function of Takuya Yoshikawa
2010-05-04 13:04 [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like Takuya Yoshikawa
2010-05-04 13:04 ` [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like function for bitmaps in user space Takuya Yoshikawa
2010-05-04 13:04 ` Takuya Yoshikawa
2010-05-04 13:04 ` Takuya Yoshikawa
2010-05-04 13:04 ` [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like Takuya Yoshikawa
2010-05-11 16:00 ` Alexander Graf
2010-05-11 16:00   ` [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like function for bitmaps in user space Alexander Graf
2010-05-11 16:00   ` Alexander Graf
2010-05-11 16:00   ` Alexander Graf
2010-05-11 16:00   ` [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like Alexander Graf
2010-05-12  9:25 ` Takuya Yoshikawa
2010-05-12  9:25   ` [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like function for bitmaps in user space Takuya Yoshikawa
2010-05-12  9:25   ` Takuya Yoshikawa
2010-05-12  9:25   ` [RFC][PATCH 7/12 not tested yet] PPC: introduce __set_bit() like Takuya Yoshikawa
2010-05-04 13:03 [RFC][PATCH 6/12 not tested yet] PPC: introduce copy_in_user() for Takuya Yoshikawa
2010-05-04 13:03 ` [RFC][PATCH 6/12 not tested yet] PPC: introduce copy_in_user() for 32-bit Takuya Yoshikawa
2010-05-04 13:03 ` Takuya Yoshikawa
2010-05-04 13:03 ` [RFC][PATCH 6/12 not tested yet] PPC: introduce copy_in_user() for Takuya Yoshikawa
2010-05-04 13:02 [RFC][PATCH 5/12] x86: introduce __set_bit() like function for Takuya Yoshikawa
2010-05-04 13:02 ` [RFC][PATCH 5/12] x86: introduce __set_bit() like function for bitmaps in user space Takuya Yoshikawa
2010-05-04 13:02 ` Takuya Yoshikawa
2010-05-04 13:02 ` [RFC][PATCH 5/12] x86: introduce __set_bit() like function for Takuya Yoshikawa
2010-05-04 13:02 [RFC][PATCH 4/12] x86: introduce copy_in_user() for 32-bit Takuya Yoshikawa
2010-05-04 13:02 ` Takuya Yoshikawa
2010-05-04 13:02 ` Takuya Yoshikawa
2010-05-04 13:02 ` Takuya Yoshikawa
2010-05-04 13:01 [RFC][PATCH 3/12] KVM: introduce wrapper functions to create and Takuya Yoshikawa
2010-05-04 13:01 ` [RFC][PATCH 3/12] KVM: introduce wrapper functions to create and destroy dirty bitmaps Takuya Yoshikawa
2010-05-04 13:01 ` Takuya Yoshikawa
2010-05-04 13:01 ` Takuya Yoshikawa
2010-05-04 13:01 ` [RFC][PATCH 3/12] KVM: introduce wrapper functions to create and Takuya Yoshikawa
2010-05-04 13:00 [RFC][PATCH 2/12] KVM: introduce slot level dirty state management Takuya Yoshikawa
2010-05-04 13:00 ` Takuya Yoshikawa
2010-05-04 13:00 ` Takuya Yoshikawa
2010-05-04 13:00 ` Takuya Yoshikawa
2010-05-04 13:00 ` Takuya Yoshikawa
2010-05-04 12:58 [RFC][PATCH 1/12 applied today] KVM: x86: avoid unnecessary bitmap Takuya Yoshikawa
2010-05-04 12:58 ` [RFC][PATCH 1/12 applied today] KVM: x86: avoid unnecessary bitmap allocation when memslot is clean Takuya Yoshikawa
2010-05-04 12:58 ` Takuya Yoshikawa
2010-05-04 12:58 ` [RFC][PATCH 1/12 applied today] KVM: x86: avoid unnecessary bitmap Takuya Yoshikawa
2010-05-04 12:56 [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Takuya Yoshikawa
2010-05-04 12:56 ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-05-04 12:56 ` Takuya Yoshikawa
2010-05-04 12:56 ` Takuya Yoshikawa
2010-05-04 12:56 ` Takuya Yoshikawa
2010-05-04 12:56 ` Takuya Yoshikawa
2010-05-04 12:56 ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Takuya Yoshikawa
2010-05-10 12:06 ` Avi Kivity
2010-05-10 12:06   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Avi Kivity
2010-05-10 12:06   ` Avi Kivity
2010-05-10 12:06   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Avi Kivity
2010-05-10 12:26 ` Takuya Yoshikawa
2010-05-10 12:26   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-05-10 12:26   ` Takuya Yoshikawa
2010-05-10 12:26   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Takuya Yoshikawa
2010-05-11 10:11 ` Takuya Yoshikawa
2010-05-11 10:11   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-05-11 10:11   ` Takuya Yoshikawa
2010-05-11 10:11   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Takuya Yoshikawa
2010-05-11 15:55 ` Alexander Graf
2010-05-11 15:55   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Alexander Graf
2010-05-11 15:55   ` Alexander Graf
2010-05-11 15:55   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Alexander Graf
2010-05-12  9:19 ` Takuya Yoshikawa
2010-05-12  9:19   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-05-12  9:19   ` Takuya Yoshikawa
2010-05-12  9:19   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Takuya Yoshikawa
2010-05-13 11:47 ` Avi Kivity
2010-05-13 11:47   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Avi Kivity
2010-05-13 11:47   ` Avi Kivity
2010-05-13 11:47   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps Avi Kivity
2010-05-17  9:06 ` Takuya Yoshikawa
2010-05-17  9:06   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space Takuya Yoshikawa
2010-05-17  9:06   ` Takuya Yoshikawa
2010-05-17  9:06   ` [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps 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=4BE04677.4060608@redhat.com \
    --to=avi@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.