From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: Initialization of cr.dcr
Date: Mon, 06 Jun 2005 08:09:21 +0000 [thread overview]
Message-ID: <42A404B1.1010703@hob.de> (raw)
In-Reply-To: <42A01CA2.8010209@hob.de>
Chen, Kenneth W schrieb:
>Patch to update the comments to reflect the actual code in cpu_init().
>
However the actual code distincts between TLB miss and other faults. The
other faults are deferred.
Christian
>
>Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
>Acked-by: David Mosberger-Tang <davidm@hpl.hp.com>
>
>--- linux-2.6.11/arch/ia64/kernel/setup.c.orig 2005-06-03 12:21:00.891940166 -0700
>+++ linux-2.6.11/arch/ia64/kernel/setup.c 2005-06-03 12:22:36.036470251 -0700
>@@ -720,7 +720,7 @@ cpu_init (void)
> ia64_set_kr(IA64_KR_PT_BASE, __pa(ia64_imva(empty_zero_page)));
>
> /*
>- * Initialize default control register to defer all speculative faults. The
>+ * Initialize default control register not to defer speculative faults. The
> * kernel MUST NOT depend on a particular setting of these bits (in other words,
> * the kernel must have recovery code for all speculative accesses). Turn on
> * dcr.lc as per recommendation by the architecture team. Most IA-32 apps
>
>
>
prev parent reply other threads:[~2005-06-06 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 9:02 Initialization of cr.dcr Christian Hildner
2005-06-03 18:11 ` Chen, Kenneth W
2005-06-03 18:27 ` Russ Anderson
2005-06-03 19:05 ` Chen, Kenneth W
2005-06-03 19:11 ` David Mosberger
2005-06-03 19:26 ` Chen, Kenneth W
2005-06-06 8:09 ` Christian Hildner [this message]
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=42A404B1.1010703@hob.de \
--to=christian.hildner@hob.de \
--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