From: Con Kolivas <kernel@kolivas.org>
To: vatsa@in.ibm.com
Cc: 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: Tue, 16 Aug 2005 02:30:51 +1000 [thread overview]
Message-ID: <200508160230.52860.kernel@kolivas.org> (raw)
In-Reply-To: <20050815153541.GA4731@in.ibm.com>
On Tue, 16 Aug 2005 01:35, Srivatsa Vaddagiri wrote:
> 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?
yes I already said I tried apic mode, that's the one that works "best" but I
suspect that's reflecting the fact that I hardly ever go below 300Hz on this
machine except in init 1. Time definitely was lost the longer the machine was
running.
> What does
> /sys/.../dyn_tick0/state show when my patch is working (in APIC mode for
> you)?
suitable: 1
enabled: 1
apic suitable: 1
using APIC: 1
(remember I wrote the sysfs portion ;) )
> Can you disable CONFIG_DYN_TICK_USE_APIC with my patch and check if
> it works?
You mean disable it at runtime or not compile it in at all? Disabling it at
runtime caused what I described to you as PIT mode (long stalls etc).
> Also can you send me 'dmesg | grep APIC' (want to know if your
> hardware has local APIC that is enabled by the kernel).
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Enabling APIC mode: Flat. Using 1 I/O APICs
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
ENABLING IO-APIC IRQs
ACPI: Using IOAPIC for interrupt routing
Cheers,
Con
next prev parent reply other threads:[~2005-08-15 16:31 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
2005-08-15 16:30 ` Con Kolivas [this message]
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=200508160230.52860.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=tuukka.tikkanen@elektrobit.com \
--cc=vatsa@in.ibm.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.