Memory API code review

Memory API code review

[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 the schedule.

It would be great if people from the wider qemu community be present, 
rather than the usual "x86 is everything" crowd (+Jan) that usually 
participates in the kvm weekly call.

Juan, Chris, can we dedicate next week's call to this?

We'll also need a way to disseminate a few slides and an editor session 
for showing the code.  We have an elluminate account that can be used 
for this, but usually this has a 50% failure rate on Linux.  Anthony, 
perhaps we can set up a view-only vnc reflector on qemu.org?

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

[Qemu-devel] Memory API code review

[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 the schedule.

It would be great if people from the wider qemu community be present, 
rather than the usual "x86 is everything" crowd (+Jan) that usually 
participates in the kvm weekly call.

Juan, Chris, can we dedicate next week's call to this?

We'll also need a way to disseminate a few slides and an editor session 
for showing the code.  We have an elluminate account that can be used 
for this, but usually this has a 50% failure rate on Linux.  Anthony, 
perhaps we can set up a view-only vnc reflector on qemu.org?

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

Re: [Qemu-devel] Memory API code review

[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 many people already have it
> reserved in the schedule.
>
> It would be great if people from the wider qemu community be present,
> rather than the usual "x86 is everything" crowd (+Jan) that usually
> participates in the kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?
>
> We'll also need a way to disseminate a few slides and an editor session
> for showing the code. We have an elluminate account that can be used for
> this, but usually this has a 50% failure rate on Linux. Anthony, perhaps
> we can set up a view-only vnc reflector on qemu.org?

Absolutely.  I'll set something up and then get with you for the details 
of access.

Regards,

Anthony Liguori

>

Re: [Qemu-devel] Memory API code review

[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 many people already have it
> reserved in the schedule.
>
> It would be great if people from the wider qemu community be present,
> rather than the usual "x86 is everything" crowd (+Jan) that usually
> participates in the kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?
>
> We'll also need a way to disseminate a few slides and an editor session
> for showing the code. We have an elluminate account that can be used for
> this, but usually this has a 50% failure rate on Linux. Anthony, perhaps
> we can set up a view-only vnc reflector on qemu.org?

Absolutely.  I'll set something up and then get with you for the details 
of access.

Regards,

Anthony Liguori

>

Re: Memory API code review

[Chris Wright]

* Avi Kivity (avi@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) since many people already have it reserved in the
> schedule.
> 
> It would be great if people from the wider qemu community be present, rather
> than the usual "x86 is everything" crowd (+Jan) that usually participates in
> the kvm weekly call.
> 
> Juan, Chris, can we dedicate next week's call to this?

Yup, sounds like a good idea.

Re: [Qemu-devel] Memory API code review

[Chris Wright]

* Avi Kivity (avi@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) since many people already have it reserved in the
> schedule.
> 
> It would be great if people from the wider qemu community be present, rather
> than the usual "x86 is everything" crowd (+Jan) that usually participates in
> the kvm weekly call.
> 
> Juan, Chris, can we dedicate next week's call to this?

Yup, sounds like a good idea.

Re: Memory API code review

[Juan Quintela]

Avi Kivity <avi@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) since many people
> already have it reserved in the schedule.
>
> It would be great if people from the wider qemu community be present,
> rather than the usual "x86 is everything" crowd (+Jan) that usually
> participates in the kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?

I think so.

Later, Juan.

> We'll also need a way to disseminate a few slides and an editor
> session for showing the code.  We have an elluminate account that can
> be used for this, but usually this has a 50% failure rate on Linux.
> Anthony, perhaps we can set up a view-only vnc reflector on qemu.org?

Re: [Qemu-devel] Memory API code review

[Juan Quintela]

Avi Kivity <avi@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) since many people
> already have it reserved in the schedule.
>
> It would be great if people from the wider qemu community be present,
> rather than the usual "x86 is everything" crowd (+Jan) that usually
> participates in the kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?

I think so.

Later, Juan.

> We'll also need a way to disseminate a few slides and an editor
> session for showing the code.  We have an elluminate account that can
> be used for this, but usually this has a 50% failure rate on Linux.
> Anthony, perhaps we can set up a view-only vnc reflector on qemu.org?

Re: Memory API code review

[Peter Maydell]

On 14 September 2011 16:07, Avi Kivity <avi@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) since many people already have it reserved in the
> schedule.
>
> It would be great if people from the wider qemu community be present, rather
> than the usual "x86 is everything" crowd (+Jan) that usually participates in
> the kvm weekly call.

I can dial in if that's useful -- are the dialin details available somewhere?

thanks
-- PMM

Re: [Qemu-devel] Memory API code review

[Peter Maydell]

On 14 September 2011 16:07, Avi Kivity <avi@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) since many people already have it reserved in the
> schedule.
>
> It would be great if people from the wider qemu community be present, rather
> than the usual "x86 is everything" crowd (+Jan) that usually participates in
> the kvm weekly call.

I can dial in if that's useful -- are the dialin details available somewhere?

thanks
-- PMM

Re: [Qemu-devel] Memory API code review

[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 many people already have it reserved in the schedule.
>
> It would be great if people from the wider qemu community be present, rather
> than the usual "x86 is everything" crowd (+Jan) that usually participates in the
> kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?
>
> We'll also need a way to disseminate a few slides and an editor session for
> showing the code. We have an elluminate account that can be used for this, but
> usually this has a 50% failure rate on Linux. Anthony, perhaps we can set up a
> view-only vnc reflector on qemu.org?
>

The reflector is at:

qemu.osuosl.org:0

Regards,

Anthony Liguori

Re: [Qemu-devel] Memory API code review

[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 many people already have it reserved in the schedule.
>
> It would be great if people from the wider qemu community be present, rather
> than the usual "x86 is everything" crowd (+Jan) that usually participates in the
> kvm weekly call.
>
> Juan, Chris, can we dedicate next week's call to this?
>
> We'll also need a way to disseminate a few slides and an editor session for
> showing the code. We have an elluminate account that can be used for this, but
> usually this has a 50% failure rate on Linux. Anthony, perhaps we can set up a
> view-only vnc reflector on qemu.org?
>

The reflector is at:

qemu.osuosl.org:0

Regards,

Anthony Liguori