LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Prakash Punnoor <prakash@punnoor.de>
Cc: Andi Kleen <andi@firstfloor.org>,
mingo@elte.hu, tglx@linutronix.de, lenb@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace nvidia timer override quirk with pci id list
Date: Fri, 8 Feb 2008 20:01:43 +0100 [thread overview]
Message-ID: <20080208190143.GB11573@one.firstfloor.org> (raw)
In-Reply-To: <200802081839.18267.prakash@punnoor.de>
On Fri, Feb 08, 2008 at 06:39:17PM +0100, Prakash Punnoor wrote:
> On the day of Friday 08 February 2008 Andi Kleen hast written:
> > On Fri, Feb 08, 2008 at 04:13:35PM +0100, Prakash Punnoor wrote:
>
> > > Sorry, I meant the opposite. I needed the acpi_skip_timer_override kernel
> > > parameter for nforce2, thus no override. So this chipset is missing here.
> > > At least I remember that my nforce2 needed the skipping,
> >
> > I hope you remember correctly and mean it this time. It would be better
> > if you could double check.
>
> Yes, confirmed. timer w/o the skipping stays XT-PIC on nforce2.
Confirmed what? Did you test my patch on both machines?
What was the result?
> lspci -n:
Please always send lspci without -n too; I hate looking up hex codes
by hand when a computer can do that for me.
> 02:00.0 0300: 10de:0281 (rev a1)
>
> > I'm a little sceptical because we had this patch in OpenSUSE 10.3
> > and I didn't think there were complaints from NF2 users.
> > With the changes you're requesting it turns from something
> > very well tested into something experimental.
>
> Well, even w/o the skipping my nforce2 system wasn't unstable, AFAIK. So I
> don't think just because of the XT-PIC entry people would complain.
Timer override only does something in APIC mode and when you see XT-PIC
in /proc/interrupts then you're not in APIC mode. All these patches
are a no-op in this state.
> See why I don't want the quirk to be applied more than needed? *NOT* applying
> the quirk on nforce2 didn't cause any obvious side effects. APPLYING to mcp51
> causes hard lock-ups.
Can you please just test the patches instead of speculating what they
might do or not do?
-Andi
next prev parent reply other threads:[~2008-02-08 18:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 19:55 Andi Kleen
2008-02-07 21:21 ` Prakash Punnoor
2008-02-08 11:36 ` Andi Kleen
2008-02-08 15:13 ` Prakash Punnoor
2008-02-08 15:18 ` Prakash Punnoor
2008-02-08 16:09 ` Andi Kleen
2008-02-08 17:39 ` Prakash Punnoor
2008-02-08 19:01 ` Andi Kleen [this message]
2008-02-08 19:00 ` Prakash Punnoor
2008-02-08 21:02 ` Andi Kleen
2008-02-08 23:08 ` Prakash Punnoor
2008-02-09 11:06 ` Thomas Gleixner
2008-02-09 12:18 ` Prakash Punnoor
2008-02-09 11:59 ` Andi Kleen
2008-02-09 11:53 ` Prakash Punnoor
2008-02-09 14:31 ` Andi Kleen
2008-02-09 15:51 ` Prakash Punnoor
2008-02-09 16:56 ` Andi Kleen
2008-02-09 17:30 ` Prakash Punnoor
2008-02-09 12:17 ` [PATCH] Replace nvidia timer override quirk with pci id list II Andi Kleen
2010-01-29 8:32 ` [PATCH] Replace nvidia timer override quirk with pci id list Yuhong Bao
2008-02-09 12:46 ` Gene Heskett
2008-02-09 14:18 ` Andi Kleen
2008-02-09 14:03 ` Alan Cox
2008-02-09 18:02 ` Gene Heskett
2008-02-09 18:11 ` Prakash Punnoor
2008-02-09 20:05 ` Gene Heskett
2008-02-09 21:13 ` Prakash Punnoor
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=20080208190143.GB11573@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prakash@punnoor.de \
--cc=tglx@linutronix.de \
--subject='Re: [PATCH] Replace nvidia timer override quirk with pci id list' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).