From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=46219 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OIOG9-0001yn-2a
	for qemu-devel@nongnu.org; Sat, 29 May 2010 11:47:44 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jan.kiszka@web.de>) id 1OIJ5Z-0003vg-P0
	for qemu-devel@nongnu.org; Sat, 29 May 2010 06:16:22 -0400
Received: from fmmailgate02.web.de ([217.72.192.227]:40738)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jan.kiszka@web.de>) id 1OIJ5Z-0003vW-DA
	for qemu-devel@nongnu.org; Sat, 29 May 2010 06:16:21 -0400
Message-ID: <4C00E96D.2060908@web.de>
Date: Sat, 29 May 2010 12:16:13 +0200
From: Jan Kiszka <jan.kiszka@web.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [RFT][PATCH 07/15] qemu_irq: Add IRQ handlers
	with delivery feedback
References: <AANLkTinP2QheAYmPzPfIZ0qeOcyCv_L5CRoif4XXe5qt@mail.gmail.com>
	<4BFC3028.6030303@codemonkey.ws> <4BFC44D2.2090608@web.de>
	<AANLkTimP25BI3UI_5Zts3uZ4JUG2nq18R8ncOsTrj5v1@mail.gmail.com>
	<4BFD8010.3010001@web.de>
	<AANLkTim6zZYtkPkJxlZHbHKWhWXcU-RlpvgeyMUriBj1@mail.gmail.com>
	<20100527061335.GE5474@redhat.com>
	<AANLkTinwXJ1dwWoVZLTQOrK2byczn97TzHkh1wdjOGjQ@mail.gmail.com>
	<20100528073135.GC17805@redhat.com>
	<AANLkTin4ib3PmnKGHAVIwVpLeyPMz03xx-MVjOvlUba5@mail.gmail.com>
	<20100528204746.GC3604@redhat.com> <4C00C921.2060809@web.de>
	<AANLkTin5oH2PzY_4K6RnWFjcYyHlIFkTghTzgC-qpkix@mail.gmail.com>
	<4C00E257.8070409@web.de>
	<AANLkTinxv5qBTeWaG6KskESJwzDLxgbeRxOGgordnOd1@mail.gmail.com>
In-Reply-To: <AANLkTinxv5qBTeWaG6KskESJwzDLxgbeRxOGgordnOd1@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigA21AA0066488B81812C4F59B"
Sender: jan.kiszka@web.de
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>, Juan Quintela <quintela@redhat.com>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA21AA0066488B81812C4F59B
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Blue Swirl wrote:
>>>> This is - according to my current understanding - the proposed
>>>> alternative architecture:
>>>>
>>>>                                          .---------------.
>>>>                                          | de-coalescing |
>>>>                                          |     logic     |
>>>>                                          '---------------'
>>>>                                                ^   |
>>>>                                         period,|   |IRQ
>>>>                                       coalesced|   |(or tuned VM clo=
ck)
>>>>                                        (yes/no)|   v
>>>> .-------.              .--------.             .-------.
>>>> |  RTC  |-----IRQ----->| router |-----IRQ---->| APIC  |
>>>> '-------'              '--------'             '-------'
>>>>    |                    ^    |                   ^
>>>>    |                    |    |                   |
>>>>    '-------period-------'    '------period-------'
>>> The period information is already known by the higher level clock
>>> management,
>> The timer device models program the next event of some qemu-timer. The=
re
>> is no tag attached explaining the timer subsystem or anyone else the
>> reason behind this programming.
>=20
> Yes, but why would we care? All timers in the system besides RTC
> should be affected likewise, this would in fact be the benefit from
> handling the problem at higher level.

And how does your equation for calculating the clock slow-down look like?=


Jan


--------------enigA21AA0066488B81812C4F59B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkwA6XEACgkQitSsb3rl5xQFjACg5zqsr+TmGHXt/FnUWYE7A1XR
Hl0AmwSe75dW13Px22svKUKB75A1St83
=HHg3
-----END PGP SIGNATURE-----

--------------enigA21AA0066488B81812C4F59B--