From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vasily Khoruzhick Subject: Re: Interrupt latency on some 945GM platforms Date: Tue, 14 Sep 2010 11:09:36 +0300 Message-ID: <201009141109.41596.anarsoul@gmail.com> References: <201009132336.17310.anarsoul@gmail.com> <201009140104.03135.anarsoul@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0081250010==" Return-path: Received: from mail-ew0-f49.google.com (mail-ew0-f49.google.com [209.85.215.49]) by gabe.freedesktop.org (Postfix) with ESMTP id 3962B9E7EF for ; Tue, 14 Sep 2010 01:10:41 -0700 (PDT) Received: by ewy9 with SMTP id 9so3493563ewy.36 for ; Tue, 14 Sep 2010 01:10:40 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Venkatesh Pallipadi Cc: intel-gfx@lists.freedesktop.org, Thomas Gleixner , linux-kernel@vger.kernel.org List-Id: intel-gfx@lists.freedesktop.org --===============0081250010== Content-Type: multipart/signed; boundary="nextPart18620413.uCaTN5nVUu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart18620413.uCaTN5nVUu Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable =D0=92 =D1=81=D0=BE=D0=BE=D0=B1=D1=89=D0=B5=D0=BD=D0=B8=D0=B8 =D0=BE=D1=82 = 14 of September 2010 03:55:32 =D0=B0=D0=B2=D1=82=D0=BE=D1=80 Venkatesh Pall= ipadi=20 =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > Whats the clockevent in this case ("Tick Device" section of > /proc/timer_list). clocksource=3D option only changes the clocksource used > to maintain > timeofday. But, timer interrupt (clockevent) source will not change. > Wondering how just the clocksource change is making the diff here.. >=20 > Also, if clocksource tsc has a higher rating than HPET. The reason > HPET is getting used as clocksource in the first place seems to be due > to TSC is not a dependable clocksource on this platform (may be it > stops in C3). So, I am not sure forcing it to tsc will be a good > thing. May be clocksource=3Dacpi_pm is a better thing to try. >=20 > Thanks, > Venki I investigated it a bit and found out that single nohz=3Doff option helps. = Just=20 changing clocksource doesn't help, but it works smoothly with any clocksour= ce=20 with nohz=3Doff. So, it seems that something wrong with intel driver while= =20 system is in tickless mode.=20 Regards Vasily --nextPart18620413.uCaTN5nVUu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAkyPLcUACgkQRM6pQpltKE7B1gCfTr8l8V7ZHlxVy/yvVeIbq4Rw 0ZcAoLn83BiqtHbUBQy5hkRpr1ZfGedh =0Rlc -----END PGP SIGNATURE----- --nextPart18620413.uCaTN5nVUu-- --===============0081250010== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============0081250010==--