public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Olaf Zaplinski <o.zaplinski@mediascape.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.11-pre4
Date: Fri, 5 Oct 2001 22:33:54 +0200	[thread overview]
Message-ID: <20011005203328Z272074-760+21278@vger.kernel.org> (raw)
In-Reply-To: <1551862685.1002279242@mbligh.des.sequent.com>
In-Reply-To: <1551862685.1002279242@mbligh.des.sequent.com>

Am Freitag, 5. Oktober 2001 19:54 schrieb Martin J. Bligh:
> > Odd. Compiles for me with and without SMP support turned on.
>
> My fault. I'd tested this on SMP and Uniproc, but not uniproc with
> IO apic support. Try this patch:

1. OK, it fixes the UP UP_IOAPIC compilation problem.
System (with preempt-patch) up and runnig.

2. Woohu. I have 8 CPUs, now...;-)
--- /proc is somewhat broken

[-]
processor       : 7
vendor_id       : 9—U0D'À
cpu family      : 1
model           : 0
model name      : 0D'À
stepping        : unknown
cache size      : 0 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : -1071168528
wp              : yes
flags           : fpu syscall mmxext lm 3dnowext 3dnow cxmmx
bogomips        : 0.00
[-]

3. OOmem deak look.

4. Back in disk stress mode...again.

-Dieter

> --- smp.h.old	Fri Oct  5 10:46:40 2001
> +++ smp.h	Fri Oct  5 10:48:37 2001
> @@ -31,9 +31,20 @@
>  #  define INT_DELIVERY_MODE 1     /* logical delivery broadcast to all
> procs */ # endif
>  #else
> +# define INT_DELIVERY_MODE 0     /* physical delivery on LOCAL quad */
>  # define TARGET_CPUS 0x01
>  #endif
>
> +#ifndef clustered_apic_mode
> + #ifdef CONFIG_MULTIQUAD
> +  #define clustered_apic_mode (1)
> +  #define esr_disable (1)
> + #else /* !CONFIG_MULTIQUAD */
> +  #define clustered_apic_mode (0)
> +  #define esr_disable (0)
> + #endif /* CONFIG_MULTIQUAD */
> +#endif
> +
>  #ifdef CONFIG_SMP
>  #ifndef ASSEMBLY
>
> @@ -76,16 +87,6 @@
>  extern volatile int physical_apicid_to_cpu[MAX_APICID];
>  extern volatile int cpu_to_logical_apicid[NR_CPUS];
>  extern volatile int logical_apicid_to_cpu[MAX_APICID];
> -
> -#ifndef clustered_apic_mode
> - #ifdef CONFIG_MULTIQUAD
> -  #define clustered_apic_mode (1)
> -  #define esr_disable (1)
> - #else /* !CONFIG_MULTIQUAD */
> -  #define clustered_apic_mode (0)
> -  #define esr_disable (0)
> - #endif /* CONFIG_MULTIQUAD */
> -#endif
>
>  /*
>   * General functions that each host system must provide.

  parent reply	other threads:[~2001-10-05 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05  4:38 Linux 2.4.11-pre4 Dieter Nützel
2001-10-05 16:25 ` Martin J. Bligh
2001-10-05 17:54   ` Martin J. Bligh
2001-10-05 18:15     ` Dieter Nützel
2001-10-05 20:33     ` Dieter Nützel [this message]
2001-10-05 18:11   ` Dieter Nützel
     [not found] <200110052031.QAA23072@e34.esmtp.ibm.com>
2001-10-05 21:35 ` Martin J. Bligh
2001-10-06 20:42   ` Dieter Nützel
  -- strict thread matches above, loose matches on Subject: below --
2001-10-05  3:47 Linus Torvalds

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=20011005203328Z272074-760+21278@vger.kernel.org \
    --to=dieter.nuetzel@hamburg.de \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o.zaplinski@mediascape.de \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox