From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>
Subject: Re: [Qemu-devel] KVM call agenda for 2014-05-13
Date: Tue, 13 May 2014 12:21:34 +0200
Message-ID: <5371F22E.6050005@suse.de>
References: <87vbtb9xb2.fsf@elfo.mitica>	<CAFEAcA_UQsEJURQazx0Xv4v3d7ZgO0WGs5XBfcgc_sugJ6OmKA@mail.gmail.com>	<CAEgOgz49P-3Ru_+-BD3Mo8Y_ftnhZBUpMa9OE+5vEqFUW2ohjA@mail.gmail.com> <CAFEAcA9zMYTd5noO68ofbLe70sMGxcMgAC8jvyw0WFByrkJASA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: qemu list <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	Juan Quintela <quintela@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Kirill Batuzov <batuzovk@ispras.ru>,
	Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from cantor2.suse.de ([195.135.220.15]:50947 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1759756AbaEMKVh (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 13 May 2014 06:21:37 -0400
In-Reply-To: <CAFEAcA9zMYTd5noO68ofbLe70sMGxcMgAC8jvyw0WFByrkJASA@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Am 12.05.2014 13:09, schrieb Peter Maydell:
> On 12 May 2014 11:30, Peter Crosthwaite <peter.crosthwaite@xilinx.com=
> wrote:
>> On Mon, May 12, 2014 at 7:44 PM, Peter Maydell <peter.maydell@linaro=
=2Eorg> wrote:
>>> On 12 May 2014 10:10, Juan Quintela <quintela@redhat.com> wrote:
>>>> Please, send any topic that you are interested in covering.
>>>>
>>>> - QOMifying both Memory regions and GPIOs and attaching them via Q=
OM
>>>>   links (Peter Crosthwaite)
>>>
>>> Is there some further useful material on-list on this subject, or
>>> are we just going to have a rerun of the discussions on the
>>> last two calls?
>=20
>> I have any ugly work-in-progress series. TBH I was going to wait for
>> discussion outcomes. Want me to RFC it?
>=20
> I don't think you necessarily need to post code, but maybe a writeup
> of current status/options would be useful to try to make the on-call
> discussion productive?

Here's my WIP qemu_irq conversion, so that we don't discuss IRQs for th=
e
third time in a row without results:

https://github.com/afaerber/qemu-cpu/commits/qom-irq

make check passes, not further tested yet.
As a side effect, cleaning up the leaks turned out rather easy.

The only remaining users of qemu_free_irqs() are serial-pci.c and
ipack.c. If we can get rid of it altogether, the hacks for freeing the
memory chunk could be avoided.

Regards,
Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=
=BCrnberg