public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Francis Galiegue <fg@mandrakesoft.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
Date: Sun, 25 Feb 2001 02:43:10 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005200@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005175@msgid-missing>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 574 bytes --]

On Sat, 24 Feb 2001, Joseph V Moss wrote:

> 
> You've got a small cut'n'paste error there:
>  

[...]
> > +  with a B1-step CPU.  You have a B0-step CPU if the "revision" field in
>                                      ^^

Oops! Corrected version attached. Thanks for noticing.

-- 
Francis Galiegue, fg@mandrakesoft.com - Normand et fier de l'être
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race"  -- R. Cook

[-- Attachment #2: Type: TEXT/PLAIN, Size: 3499 bytes --]

diff -urN linux-old/Documentation/Configure.help linux/Documentation/Configure.help
--- linux-old/Documentation/Configure.help	Sat Feb 24 08:29:45 2001
+++ linux/Documentation/Configure.help	Sat Feb 24 09:24:15 2001
@@ -17119,17 +17119,36 @@
   with a B0-step CPU.  You have a B0-step CPU if the "revision" field in
   /proc/cpuinfo is 1.
 
+Enable Itanium B1-step specific code
+CONFIG_ITANIUM_B1_SPECIFIC
+  Select this option to bild a kernel for an Itanium prototype system
+  with a B1-step CPU.  You have a B1-step CPU if the "revision" field in
+  /proc/cpuinfo is 2.
+
+Enable Itanium B2-step specific code
+CONFIG_ITANIUM_B2_SPECIFIC
+  Select this option to bild a kernel for an Itanium prototype system
+  with a B2-step CPU.  You have a B2-step CPU if the "revision" field in
+  /proc/cpuinfo is 3.
+
 Force interrupt redirection
 CONFIG_IA64_HAVE_IRQREDIR
   Select this option if you know that your system has the ability to
   redirect interrupts to different CPUs.  Select N here if you're
   unsure.
 
-Enable use of global TLB purge instruction (ptc.g)
+Enable use of global TLB purge instruction (ptc.g) (READ HELP!)
 CONFIG_ITANIUM_PTCG
-  Say Y here if you want the kernel to use the IA-64 "ptc.g"
-  instruction to flush the TLB on all CPUs.  Select N here if
-  you're unsure.
+  Saying Y here will allow the kernel to use the IA-64 "ptc.g"
+  instruction to flush the TLB on all CPUs.
+  
+  Say N here if the kernel will run on early B step CPUs (B0, B1 and B2). You
+  have such a CPU (or CPUs) if the revision field(s) in /proc/cpuinfo range(s)
+  from 1 to 3. In this case, you should also say Y to "Disable VHPT" (this is
+  in "Kernel hacking" section).
+
+  If you have a more recent CPU, however, you will have to do the opposite: say
+  Y here but N to "Disable VHPT".
 
 Enable SoftSDV hacks
 CONFIG_IA64_SOFTSDV_HACKS
@@ -17168,6 +17187,16 @@
 
   To use this option, you have to check that the "/proc file system
   support" (CONFIG_PROC_FS) is enabled, too.
+
+Disable VHPT (READ HELP!)
+CONFIG_DISABLE_VHPT
+  Say Y here if the kernel will run on early B step CPUs (B0, B1 and B2). You
+  have such a CPU (or CPUs) if the revision field(s) in /proc/cpuinfo range(s)
+  from 1 to 3. In this case, you should also say N to "Enable use of global TLB
+  purge instruction" (CONFIG_ITANIUM_PTCG) in the "General Setup" section.
+
+  If your CPU(s) is/are more recent, however, you will preferably do the
+  opposite: say N here, but say Y to CONFIG_ITANIUM_PTCG.
 
 #
 # A couple of things I keep forgetting:
diff -urN linux-old/arch/ia64/config.in linux/arch/ia64/config.in
--- linux-old/arch/ia64/config.in	Sat Feb 24 08:29:45 2001
+++ linux/arch/ia64/config.in	Sat Feb 24 09:26:27 2001
@@ -58,7 +58,7 @@
 	if [ "$CONFIG_ITANIUM_CSTEP_SPECIFIC" = "y" ]; then
 	  bool '   Enable Itanium C0-step specific code' CONFIG_ITANIUM_C0_SPECIFIC
 	fi
-	bool '  Enable use of global TLB purge instruction (ptc.g)' CONFIG_ITANIUM_PTCG
+	bool '  Enable use of global TLB purge instruction (ptc.g) (READ HELP!)' CONFIG_ITANIUM_PTCG
 fi
 
 if [ "$CONFIG_IA64_DIG" = "y" ]; then
@@ -259,6 +259,6 @@
 bool 'Turn on irq debug checks (slow!)' CONFIG_IA64_DEBUG_IRQ
 bool 'Print possible IA64 hazards to console' CONFIG_IA64_PRINT_HAZARDS
 bool 'Enable new unwind support' CONFIG_IA64_NEW_UNWIND
-bool 'Disable VHPT' CONFIG_DISABLE_VHPT
+bool 'Disable VHPT (READ HELP!)' CONFIG_DISABLE_VHPT
 
 endmenu

  parent reply	other threads:[~2001-02-25  2:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-21 16:05 [Linux-ia64] Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 17:16 ` Gerrit Huizenga
2001-02-21 17:57 ` David Mosberger
2001-02-21 18:58 ` Chris McDermott
2001-02-21 21:02 ` David Mosberger
2001-02-23 15:19 ` Jun Nakajima
2001-02-23 19:06 ` Seth, Rohit
2001-02-23 19:20 ` Michael Madore
2001-02-23 19:48 ` Seth, Rohit
2001-02-23 20:00 ` Jesse Barnes
2001-02-24 13:39 ` Francis Galiegue
2001-02-24 14:44 ` Francis Galiegue
2001-02-24 18:45 ` Michael Madore
2001-02-24 23:18 ` Joseph V Moss
2001-02-25  2:43 ` Francis Galiegue [this message]
2001-02-26 20:52 ` Jim Wilson
2001-03-07  3:51 ` [linux-ia64] " Tom King
2001-03-07 20:34 ` Jim Wilson
2001-03-08  3:45 ` Tom King

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=marc-linux-ia64-105590693005200@msgid-missing \
    --to=fg@mandrakesoft.com \
    --cc=linux-ia64@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