From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=49231 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OIOFP-0003Tk-UC for qemu-devel@nongnu.org; Sat, 29 May 2010 11:46:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OIJRV-00011c-5X for qemu-devel@nongnu.org; Sat, 29 May 2010 06:39:02 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:58345) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OIJRU-00011B-Q3 for qemu-devel@nongnu.org; Sat, 29 May 2010 06:39:01 -0400 Message-ID: <4C00EEBA.7060100@web.de> Date: Sat, 29 May 2010 12:38:50 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [RFT][PATCH 07/15] qemu_irq: Add IRQ handlers with delivery feedback References: <4BFC3028.6030303@codemonkey.ws> <4BFC44D2.2090608@web.de> <4BFD8010.3010001@web.de> <20100527061335.GE5474@redhat.com> <20100528073135.GC17805@redhat.com> <20100528204746.GC3604@redhat.com> <4C00C921.2060809@web.de> <4C00E257.8070409@web.de> <4C00E96D.2060908@web.de> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig53251088B76FC0450F406FD3" Sender: jan.kiszka@web.de List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org, Gleb Natapov , Juan Quintela This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig53251088B76FC0450F406FD3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Blue Swirl wrote: > On Sat, May 29, 2010 at 10:16 AM, Jan Kiszka wrote:= >> Blue Swirl wrote: >>>>>> This is - according to my current understanding - the proposed >>>>>> alternative architecture: >>>>>> >>>>>> .---------------. >>>>>> | de-coalescing | >>>>>> | logic | >>>>>> '---------------' >>>>>> ^ | >>>>>> period,| |IRQ >>>>>> coalesced| |(or tuned VM c= lock) >>>>>> (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. T= here >>>> is no tag attached explaining the timer subsystem or anyone else the= >>>> reason behind this programming. >>> 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 li= ke? >=20 > How about icount_adjust()? I would suggest that you implement your ideas now. Please keep us informed about the progress as this series (and more) depends on a decisi= on. Jan --------------enig53251088B76FC0450F406FD3 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 iEYEARECAAYFAkwA7sAACgkQitSsb3rl5xS3AwCfYXIImmzGFyT/lPeBvKPaomvw NAcAn38qzryCK3r11rJpa52nYff44sif =//0D -----END PGP SIGNATURE----- --------------enig53251088B76FC0450F406FD3--