public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, Allen Martin <AMartin@nvidia.com>
Subject: Re: IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5
Date: 21 Apr 2004 18:00:16 -0400	[thread overview]
Message-ID: <1082584816.16333.113.camel@dhcppc4> (raw)
In-Reply-To: <m3k70gx2k3.fsf@averell.firstfloor.org>

On Thu, 2004-04-15 at 19:07, Andi Kleen wrote:
> Len Brown <len.brown@intel.com> writes:
> 
> > While I don't want to get into the business of maintaining
> > a dmi_scan entry for every system with this issue, I think
> > it might be a good idea to add a couple of example entries
> > for high volume systems for which there is no BIOS fix available.
> 
> Or do a generic fix: check for the PCI-ID of the Nforce2 and when
> it is true and the timer is wrong just correct it. That's ugly,
> but it's probably the best solution for such a common issue
> (and the IO-APIC code is already filled with workarounds anyways)

IMO the fact that the IOAPIC code is full of workarounds is a reason NOT
to add another one.

> One problem is that this likely must happen before the PCI quirks
> run. In the x86-64 code I have special "early PCI scanning" code 
> for this that could be copied. I don't have a Nforce2, but when
> someone is willing to test I can do a patch for this.

If this issue had no other fix, I'd agree that the complexity is worth
it.  But a BIOS upgrade fixes this -- so I think dmi-scan simplicity
is the way to go.

-Len



  reply	other threads:[~2004-04-21 22:01 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1KkKQ-2v9-9@gated-at.bofh.it>
     [not found] ` <1Kqdx-6E1-5@gated-at.bofh.it>
     [not found]   ` <1KH4I-3W9-11@gated-at.bofh.it>
     [not found]     ` <1LgOQ-7px-3@gated-at.bofh.it>
     [not found]       ` <1LlEY-36q-11@gated-at.bofh.it>
2004-04-15 23:07         ` IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 Andi Kleen
2004-04-21 22:00           ` Len Brown [this message]
2004-05-04 20:38 Jesse Allen
2004-05-04 21:14 ` Craig Bradney
  -- strict thread matches above, loose matches on Subject: below --
2004-05-03 22:09 Allen Martin
2004-05-03 23:11 ` Bartlomiej Zolnierkiewicz
2004-05-04  8:28   ` Prakash K. Cheemplavam
2004-05-04 21:10   ` Jeff Garzik
2004-05-04 21:29     ` Bartlomiej Zolnierkiewicz
2004-05-05 12:14   ` Ross Dickson
2004-05-05 12:27     ` Ian Kumlien
2004-05-05 13:12       ` Ross Dickson
2004-05-05 13:23         ` Ian Kumlien
2004-05-05 12:58     ` Maciej W. Rozycki
2004-05-05 12:48   ` Patrick Dreker
2004-05-05 13:34     ` Patrick Dreker
2004-05-05 11:24 ` Ross Dickson
2004-05-05 12:18   ` Ian Kumlien
2004-05-05 12:52     ` Ross Dickson
2004-05-05 13:08       ` Ian Kumlien
2004-05-06  1:50         ` Jesse Allen
2004-05-03  8:08 Allen Martin
2004-04-23  1:30 Jesse Allen
2004-05-07  4:47 ` Richard James
2004-05-07  7:13   ` Craig Bradney
2004-05-08  5:33   ` Richard James
2004-04-13  1:17 IO-APIC on nforce2 Ross Dickson
2004-04-13  7:03 ` Ross Dickson
2004-04-14  1:02   ` IO-APIC on nforce2 [PATCH] Len Brown
2004-04-15 15:10     ` IO-APIC on nforce2 [PATCH] + [PATCH] for nmi_debug=1 + [PATCH] for idle=C1halt, 2.6.5 Ross Dickson
2004-04-15 20:17       ` Len Brown
2004-04-15 21:04         ` Craig Bradney
2004-04-21 20:22           ` Len Brown
2004-04-21 20:33             ` Ian Kumlien
2004-04-21 20:45             ` Craig Bradney
2004-04-21 21:28             ` Prakash K. Cheemplavam
2004-04-21 22:41               ` Len Brown
2004-04-22  7:26                 ` Prakash K. Cheemplavam
2004-04-22 14:58                   ` Len Brown
2004-04-22  8:45                 ` Craig Bradney
2004-04-22 15:03                   ` Len Brown
2004-04-22 20:50                     ` Craig Bradney
2004-04-22  8:50                 ` Arjen Verweij
2004-04-22 16:39                 ` Jesse Allen
2004-04-22 17:21                   ` Len Brown
2004-04-22 21:29                     ` Len Brown
2004-04-23  8:48                       ` Prakash K. Cheemplavam
2004-04-23  9:01                         ` Arjen Verweij
2004-04-23  9:08                           ` Prakash K. Cheemplavam
2004-04-23  9:11                           ` Prakash K. Cheemplavam
2004-04-23 12:18                       ` Maciej W. Rozycki
2004-04-26 11:41                     ` Ross Dickson
2004-04-27 17:02                       ` Arjen Verweij
2004-04-27 17:35                         ` Ian Kumlien
2004-04-27 18:00                         ` Len Brown
2004-04-27 18:24                           ` Arjen Verweij
2004-04-27 18:51                           ` Jussi Laako
2004-04-28 11:33                           ` Ross Dickson
2004-04-28 20:59                             ` Jesse Allen
2004-04-29 11:44                               ` Ross Dickson
2004-04-29 11:54                                 ` Maciej W. Rozycki
2004-04-29 12:00                                   ` Jamie Lokier
2004-04-29 12:26                                     ` Maciej W. Rozycki
2004-04-29 11:57                                 ` Jamie Lokier
2004-04-29 12:16                                 ` Craig Bradney
2004-04-29 20:24                                 ` Jesse Allen
2004-04-29 20:31                                   ` Prakash K. Cheemplavam
2004-05-03 20:45                                     ` Jesse Allen
2004-05-17 15:26                                       ` Prakash K. Cheemplavam
2004-05-17 19:32                                         ` Craig Bradney
2004-05-17 19:37                                           ` Prakash K. Cheemplavam
2004-05-17 19:57                                             ` Craig Bradney
2004-04-27 21:31                       ` Prakash K. Cheemplavam
2004-04-28 11:26                         ` Prakash K. Cheemplavam
2004-05-01  6:51                 ` Prakash K. Cheemplavam
2004-04-15 21:56         ` Arjen Verweij

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=1082584816.16333.113.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=AMartin@nvidia.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox