public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Johan Rydberg <jrydberg@gnu.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: x86 full system simulation.
Date: Tue, 31 Oct 2006 14:30:00 -0000	[thread overview]
Message-ID: <87lkmwy2u9.fsf@gnu.org> (raw)
In-Reply-To: <20061031134314.GS4978@redhat.com> (Frank Ch. Eigler's message of 	"Tue, 31 Oct 2006 08:43:14 -0500")

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

"Frank Ch. Eigler" <fche@redhat.com> writes:

> Hi -
>
> On Tue, Oct 31, 2006 at 01:54:04PM +0100, Johan Rydberg wrote:
>> I noticed that SID nowdays has a x86-component.  
>
> Yes, Tom Fitzsimmions imported a copy of BOCHS there several years ago.

"several years ago" is "nowdays" when it comes to the development pace
of SID :) 

>> Do SID come with enough hardware models to run a full machine (eg
>> 440bx)?
>
> Pretty close.  Check out the component library for details.

Cool.  I'll see if I can get it to work when I have a few hours over.

Unrelated: Has anyone toyed with the idea of maybe throwing away
mainDynamic+configrun and replacing it with a Python frontend?  In
some situations it can be of great value to script both the
configuration process and the actual simulation session.  I'm mostly
thinking about testing (of guests, not the simulator) here.

I know that SID is somewhat hooked up to tcl, but I won't touch that
with a three hundred meter pole.

~j

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2006-10-31 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 13:30 Johan Rydberg
2006-10-31 13:43 ` Frank Ch. Eigler
2006-10-31 14:30   ` Johan Rydberg [this message]
2006-10-31 14:56     ` Frank Ch. Eigler

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=87lkmwy2u9.fsf@gnu.org \
    --to=jrydberg@gnu.org \
    --cc=fche@redhat.com \
    --cc=sid@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).