9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] self modifying code in intel vga bios?
Date: Tue,  8 Mar 2011 10:52:36 -0500	[thread overview]
Message-ID: <aa2cd89ac2cb618e4de778f9c27ef247@ladd.quanstro.net> (raw)
In-Reply-To: <20110308152734.GH4355@fangle.proxima.alt.za>

On Tue Mar  8 10:30:25 EST 2011, lucio at proxima.alt.za wrote:
> On Tue, Mar 08, 2011 at 07:21:50AM -0800, Paul Lalonde wrote:
> > The last time I poked at one of these self-modifying bits they were really
> > just jitting a blit loop, in place.  Drops register pressure a little bit,
> > which has always been a bit of an issue in x86 land.
> > 
> A bankrupt CPU architecture.  I guess the day they all do it, it will
> be decreed "the right way".  In the meantime, I guess we can still
> shop around.

just like ata is no longer a physical spec, x86 is no longer a architecture.
it is simply an instruction set.  i can think of many different architectures
that implement the x86 instruction set you can buy today, for example:
bonnell (atom), athlon64, intel 5000 (conroe and friends), nehalem,
sandy bridge, via c7, etc.  the same thing goes for arm, and power.

you can complain that it's hard to decode x86, but this is also a strength:
x86 has good code density.

imagine the chaos that we'd have if the cpu vendors released a new
instruction set for each new architecture?

it may be that instruction sets aren't very important any longer.

- erik



  reply	other threads:[~2011-03-08 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  9:24 cinap_lenrek at gmx.de
2011-03-08  9:45 ` Lucio De Re
2011-03-08 15:03 ` ron minnich
2011-03-08 15:21   ` Paul Lalonde
2011-03-08 15:27     ` Lucio De Re
2011-03-08 15:52       ` erik quanstrom [this message]
2011-03-08 17:34         ` Lucio De Re
2011-03-08 19:53           ` Wes Kussmaul

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=aa2cd89ac2cb618e4de778f9c27ef247@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    /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;
as well as URLs for NNTP newsgroup(s).