All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: ck@vds.kolivas.org, tony@atomide.com,
	tuukka.tikkanen@elektrobit.com, akpm@osdl.org,
	johnstul@us.ibm.com, linux-kernel@vger.kernel.org, ak@muc.de,
	george@mvista.com
Subject: Re: [ck] [PATCH] dynamic-tick patch modified for SMP
Date: Mon, 15 Aug 2005 21:05:41 +0530	[thread overview]
Message-ID: <20050815153541.GA4731@in.ibm.com> (raw)
In-Reply-To: <200508141018.29668.kernel@kolivas.org>

On Sun, Aug 14, 2005 at 10:18:28AM +1000, Con Kolivas wrote:
> timers that made no progress until interrupts drove the timers on again. I 
> built in both PIT and APIC dyntick mode into the kernel and the default in 
> the way I modified the patch is for APIC mode to be used if it's built in. 
> After that I modified the values using the sysfs interface at
> /sys/devices/system/dyn_tick/dyn_tick0/. In APIC mode it seems to run close to 

Con,
	I am observing the reverse problem - my patch does not work in APIC
mode. I am thinking it has to do something with disabling PIT interrupts.

Have you enabled CONFIG_DYN_TICK_USE_APIC in my patch? What does
/sys/.../dyn_tick0/state show when my patch is working (in APIC mode for you)?
Can you disable CONFIG_DYN_TICK_USE_APIC with my patch and check if it
works? Also can you send me 'dmesg | grep APIC' (want to know if your
hardware has local APIC that is enabled by the kernel).



-- 


Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017

  parent reply	other threads:[~2005-08-15 16:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 20:19 [PATCH] dynamic-tick patch modified for SMP Srivatsa Vaddagiri
2005-08-13  1:35 ` [ck] " Con Kolivas
2005-08-13  6:51   ` Con Kolivas
2005-08-13 11:37     ` Srivatsa Vaddagiri
2005-08-13 14:53       ` Con Kolivas
2005-08-13 16:46         ` Srivatsa Vaddagiri
2005-08-14  0:18           ` Con Kolivas
2005-08-14  4:15             ` Kyle Moffett
2005-08-15 15:47               ` Srivatsa Vaddagiri
2005-08-15 16:39                 ` john stultz
2005-08-16  2:11                   ` Srivatsa Vaddagiri
2005-08-15 15:35             ` Srivatsa Vaddagiri [this message]
2005-08-15 16:30               ` Con Kolivas
2005-08-16 13:19                 ` Srivatsa Vaddagiri
2005-08-16 13:23                   ` Con Kolivas
2005-08-17  7:53                     ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050815153541.GA4731@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=tuukka.tikkanen@elektrobit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.