public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
	David Howells <dhowells@redhat.com>,
	Neil Brown <neilb@cse.unsw.edu.au>,
	"bugme-daemon@kernel-bugs.osdl.org" 
	<bugme-daemon@bugzilla.kernel.org>,
	linux-kernel@vger.kernel.org, alex@hausnet.ru, mingo@redhat.com
Subject: Re: [Bugme-new] [Bug 7495] New: Kernel periodically hangs.
Date: Sun, 12 Nov 2006 16:21:54 +0100	[thread overview]
Message-ID: <20061112152154.GA3382@stusta.de> (raw)
In-Reply-To: <1163340998.3293.131.camel@laptopd505.fenrus.org>

On Sun, Nov 12, 2006 at 03:16:38PM +0100, Arjan van de Ven wrote:
> 
> > > We KNOW it can't work on a sizable amount of machines.  This is why it
> > > is a config option; you can enable it if YOUR machine is KNOWN to work,
> > > and you get some gains. But it's also understood that it often it won't
> > > work. So any sensible distro (since they have to aim for a wide
> > > audience) disables this option ...
> > 
> > Nowadays, many distributions only ship CONFIG_SMP=y kernels...
> 
> that's a calculated risk on their side (and they know that); they're
> balancing not functioning on a set of machines off against needing more
> kernels.

This might soon affect the majority of Linux users, so it's a case that 
has to be handled...

> > You miss my point.
> > 
> > You said you'd suspect it to be turned off automatic most of the time, 
> > and that's the point I think you might be wrong at.
> 
> it won't be turned off on machines that support dual core processors
> etc, since those DO get validated and designed for APIC use.. even if
> you only stick a single core processor in. So yes you're right, that
> nowadays is a pretty large group. But it's the safe group I guess:)

But if APIC is even used on my more than 1 year old 40 Euro Socket A 
board (AFAIK there have never been dual core Socket A processors, there 
were no Socket A hyperthreading CPUs, it's not an SMP board, and the
VIA KT600 is not an SMP chipset) it's not in what you call "safe group",
and I don't see any reason why my board should behave different in this 
respect from all of the millions of other UP Socket A boards.

Googling show that it could be that your claim "APIC on true UP (no 
Hyperthreading/Dualcore) is a thing no hardware vendor tests (Microsoft 
doesn't use it)" earlier in this thread was wrong. Looking at e.g. [1], 
it seems Windows does use the APIC even on UP.

cu
Adrian

[1] http://www.microsoft.com/whdc/system/sysperf/IO-APIC.mspx

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-11-12 15:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611111129.kABBTWgp014081@fire-2.osdl.org>
2006-11-11 18:00 ` [Bugme-new] [Bug 7495] New: Kernel periodically hangs Andrew Morton
2006-11-11 18:10   ` Arjan van de Ven
2006-11-11 18:19     ` Andrew Morton
2006-11-12 11:50       ` Arjan van de Ven
2006-11-12 12:53         ` Adrian Bunk
2006-11-12 13:16           ` Arjan van de Ven
2006-11-12 13:37             ` Adrian Bunk
2006-11-12 13:57               ` Arjan van de Ven
2006-11-12 14:10                 ` Adrian Bunk
2006-11-12 14:16                   ` Arjan van de Ven
2006-11-12 15:21                     ` Adrian Bunk [this message]
2006-11-12 15:50                       ` Arjan van de Ven
2006-11-12 15:59                       ` Patrick McFarland
2006-11-12 16:07                         ` Arjan van de Ven
2006-11-12 16:47                         ` Adrian Bunk
2006-11-12 21:45                     ` Dave Jones
2006-11-13  2:07                       ` Andi Kleen
2006-11-12 19:18             ` Ingo Oeser
2006-11-12 19:34               ` Andrew Morton
2006-11-12 20:32               ` Arjan van de Ven
2006-11-13  6:42   ` Neil Brown
2006-11-13 11:22     ` David Howells

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=20061112152154.GA3382@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=alex@hausnet.ru \
    --cc=arjan@infradead.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@cse.unsw.edu.au \
    /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