Re: [Qemu-devel] Memory API code review

2011-09-20 Thread Anthony Liguori
On 09/14/2011 10:07 AM, Avi Kivity wrote: I would like to carry out an online code review of the memory API so that more people are familiar with the internals, and perhaps even to catch some bugs or deficiency. I'd like to use the next kvm conference call slot for this (Tuesday 1400 UTC) since m

Re: [Qemu-devel] Memory API code review

2011-09-19 Thread Peter Maydell
On 14 September 2011 16:07, Avi Kivity wrote: > I would like to carry out an online code review of the memory API so that > more people are familiar with the internals, and perhaps even to catch some > bugs or deficiency.  I'd like to use the next kvm conference call slot for > this (Tuesday 1400

Re: [Qemu-devel] Memory API code review

2011-09-15 Thread Juan Quintela
Avi Kivity wrote: > I would like to carry out an online code review of the memory API so > that more people are familiar with the internals, and perhaps even to > catch some bugs or deficiency. I'd like to use the next kvm > conference call slot for this (Tuesday 1400 UTC) since many people > alr

Re: [Qemu-devel] Memory API code review

2011-09-14 Thread Chris Wright
* Avi Kivity (a...@redhat.com) wrote: > I would like to carry out an online code review of the memory API so that > more people are familiar with the internals, and perhaps even to catch some > bugs or deficiency. I'd like to use the next kvm conference call slot for > this (Tuesday 1400 UTC) sinc

Re: [Qemu-devel] Memory API code review

2011-09-14 Thread Anthony Liguori
On 09/14/2011 10:07 AM, Avi Kivity wrote: I would like to carry out an online code review of the memory API so that more people are familiar with the internals, and perhaps even to catch some bugs or deficiency. I'd like to use the next kvm conference call slot for this (Tuesday 1400 UTC) since m

[Qemu-devel] Memory API code review

2011-09-14 Thread Avi Kivity
I would like to carry out an online code review of the memory API so that more people are familiar with the internals, and perhaps even to catch some bugs or deficiency. I'd like to use the next kvm conference call slot for this (Tuesday 1400 UTC) since many people already have it reserved in