All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Zachary Amsden <zach@vmware.com>
Cc: linux-kernel@vger.kernel.org, macro@linux-mips.org
Subject: Re: 2.6.14: CR4 not needed to be inspected on the 486 anymore?
Date: 05 Nov 2005 18:40:10 +0100	[thread overview]
Message-ID: <p73fyqb2dtx.fsf@verdi.suse.de> (raw)
In-Reply-To: <436AA1FD.3010401@vmware.com>

Zachary Amsden <zach@vmware.com> writes:
 > 
> He won't like me too much. I'll write up a proper patch for this, a la
> mode de rdmsr_safe / wrmsr_safe. At least it's not a bug, just missing
> information.

I don't think it's a good idea. Relying on nested faults in oops
is a bit unsafe because it could lead to recursive faults in the worst case. 
Yes it does it already with __get_user, but that
is only last resort. You would make it default on these systems.

Better keep the if

-Andi

  reply	other threads:[~2005-11-05 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 16:12 2.6.14: CR4 not needed to be inspected on the 486 anymore? Maciej W. Rozycki
2005-11-03 16:34 ` Zachary Amsden
2005-11-03 17:20   ` Maciej W. Rozycki
2005-11-03 23:49     ` Zachary Amsden
2005-11-05 17:40       ` Andi Kleen [this message]
2005-11-07  9:38         ` Maciej W. Rozycki
2005-11-07 15:44           ` Zachary Amsden
2005-11-07 16:37             ` Maciej W. Rozycki
2005-11-07 16:51               ` Zachary Amsden
2005-11-07 17:00                 ` linux-os (Dick Johnson)
2005-11-07 17:32                   ` Zachary Amsden
2005-11-07 18:17                     ` linux-os (Dick Johnson)
2005-11-07 19:02                       ` Ondrej Zary
2005-11-07 17:11                 ` Maciej W. Rozycki

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=p73fyqb2dtx.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=zach@vmware.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 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.