public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: root@chaos.analogic.com
Cc: Chris Wedgwood <cw@f00f.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	richard.brunner@amd.com, linux-kernel@vger.kernel.org
Subject: Re: Intel vs AMD64
Date: Thu, 26 Feb 2004 14:25:18 -0500	[thread overview]
Message-ID: <403E481E.7060609@techsource.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0402260913300.32691@chaos>



Richard B. Johnson wrote:

> Whether or not the CPU traps this invalid instruction is moot. No
> compiler would emit junk like this and anybody horsing around with
> an assembler deserves whatever they get, although you shouldn't
> be able to smoke the CPU on a multi-user multitasking system because
> it can be used as a DOS attack.


If this is junk that's invalid, why was it mentioned in the first place?


  reply	other threads:[~2004-02-26 19:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26  5:32 Intel vs AMD64 Nakajima, Jun
2004-02-26 13:39 ` Chris Wedgwood
2004-02-26 14:35   ` Richard B. Johnson
2004-02-26 19:25     ` Timothy Miller [this message]
2004-02-26 19:46       ` Richard B. Johnson
2004-02-27 18:44   ` H. Peter Anvin
2004-02-26 19:18 ` Timothy Miller
2004-02-26 19:45   ` Scott Robert Ladd
2004-02-27 14:43     ` Timothy Miller
2004-03-03 17:34   ` Pavel Machek
     [not found] <7F740D512C7C1046AB53446D37200173EA28A5@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
     [not found] ` <403E4681.20603@techsource.com.suse.lists.linux.kernel>
2004-02-26 20:17   ` Andi Kleen
2004-02-27 14:50     ` Timothy Miller
  -- strict thread matches above, loose matches on Subject: below --
2004-02-26  4:28 richard.brunner

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=403E481E.7060609@techsource.com \
    --to=miller@techsource.com \
    --cc=cw@f00f.org \
    --cc=jun.nakajima@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.brunner@amd.com \
    --cc=root@chaos.analogic.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