All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] MCA recovery for TLB faults for 2.4
Date: Wed, 28 May 2003 22:37:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706059@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723706058@msgid-missing>

On Wed, 28 May 2003 13:35:53 -0700, 
"Luck, Tony" <tony.luck@intel.com> wrote:
>The underlying algorithm is to save information about what
>each of the ITR/DTR registers is mapping, then at MCA time
>we can purge the whole TLB (TC and TR) and reload the TR
>registers before jumping to virtual mode.

ia64_os_mca_tlb_purge_and_reload() will break if somebody compiles the
kernel with -pg, say for profiling or stack monitoring.  -pg adds a
call to mcount() at the start of every function and mcount expects to
run in virtual mode.  kdb has the same problem, I get around it by
adding this line to the Makefile.

override CFLAGS := $(CFLAGS:%-pg=% )

That affects all objects in the directory, we do not want to apply that
to all objects in arch/ia64/kernel, we do not even want to apply it to
all functions in mca.c.  Please move ia64_os_mca_tlb_purge_and_reload()
to its own source file in a sub directory, say arch/ia64/kernel/physical.



  reply	other threads:[~2003-05-28 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 20:35 [Linux-ia64] [PATCH] MCA recovery for TLB faults for 2.4 Luck, Tony
2003-05-28 22:37 ` Keith Owens [this message]
2003-05-31  1:34 ` David Mosberger
2003-06-02 17:00 ` Luck, Tony
2003-06-02 18:19 ` David Mosberger
2003-06-02 18:34 ` Luck, Tony
2003-06-02 18:39 ` David Mosberger

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-105590723706059@msgid-missing \
    --to=kaos@ocs.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.