linux-mips
[Top] [All Lists]

Re: Tickless/dyntick kernel, highres timer and general time crapectomy

To: "Sergei Shtylyov" <sshtylyov@ru.mvista.com>
Subject: Re: Tickless/dyntick kernel, highres timer and general time crapectomy
From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
Date: Thu, 7 Jun 2007 16:44:11 +0200
Cc: "Ralf Baechle" <ralf@linux-mips.org>, linux-mips@linux-mips.org
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=B3Y9WFujKMzKjyfnQ5jL0ZazMAZyaffUlmQt37EzPlJW5xqhYfuqTNh127n/S7PAJm/jqFonexLNbNgvjMBycpAVIjvofUA7C/QDMX9JRW2Rjrq/D0MmxPO+zbrl9LCuFRT6I8hdArCRfSFnIPe3jQuFH5s+dB69pxTFngvRbOg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IHjAgE1br5Ce4U3NzGfCFGSv+ApiXYiH6h0spFlqHDmanV86Fe+wz9Xmdp4EXZ/MruKQ2EGRDAdD/C/RtNip1AdTye0rFeABLZ+oeqv10XE2svxCdbvvJamZHNQaT2kKaPF298mBbtmfFTsA1zR+fjgagbeP97qOxqSyV+P2WjU=
In-reply-to: <46680B75.5040809@ru.mvista.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20070606185450.GA10511@linux-mips.org> <cda58cb80706070059k3765cbf6w7e8907a2f0d83e1d@mail.gmail.com> <20070607113032.GA26047@linux-mips.org> <cda58cb80706070611t3083f026p769e3e1beee1f11e@mail.gmail.com> <46680B75.5040809@ru.mvista.com>
Sender: linux-mips-bounce@linux-mips.org
Hi,

[ weird, Gmail thought you were a spamer... ]

Sergei Shtylyov wrote:

   No, it doesn't. Even on dyntick kernels, interrupts do happen several
times a second. Dynticks have nothing to do with disabling timer
interrupts...


That's true however if your system has 2 clock devices. One is the r4k-hpt
and the other one soemthing else with a higher rating. If you don't stop
r4k-hpt interrupts, how does it work ?

--
              Franck

<Prev in Thread] Current Thread [Next in Thread>