public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lexington Luthor <lexington.luthor@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Stealing ur megahurts (no, really)
Date: Fri, 19 May 2006 16:06:22 +0100	[thread overview]
Message-ID: <e4kmte$bpc$1@sea.gmane.org> (raw)
In-Reply-To: <446DA5B0.8020703@lumumba.uhasselt.be>

Panagiotis Issaris wrote:
> An easier way might be to use a system emulator like Qemu.
> You can specify the amount of memory the emulated system has,
> and if you do not use the kernel accelerating module (kqemu)
> it slows down considerably.
> 
> Of course, it would be nicer if you could actually specify performance
> levels and an issue with this approach is that it does not uniformly
> scale down performance: I think IO emulation performance is a lot worse
> then CPU emulation performance (in Qemu).
> 

I have in the past used Bochs to precisely control the exact speed at 
which I run an emulated machine. Though this was for some DOS app which 
insisted on a ~20Mhz CPU, there is no reason this would not work on a 
Linux system emulated by Bochs.

http://bochs.sourceforge.net/

Regards,
LL


  reply	other threads:[~2006-05-19 15:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  6:13 Stealing ur megahurts (no, really) John Richard Moser
2006-05-19 10:10 ` Matti Aarnio
2006-05-19 15:40   ` Joel Jaeggli
2006-05-20 18:35     ` Antonio Vargas
2006-05-19 17:21   ` John Richard Moser
2006-05-19 11:02 ` Panagiotis Issaris
2006-05-19 15:06   ` Lexington Luthor [this message]
2006-05-19 17:22   ` John Richard Moser
2006-05-19 11:22 ` Dr. David Alan Gilbert
2006-05-19 11:43   ` linux-os (Dick Johnson)
2006-05-19 17:23   ` John Richard Moser
2006-05-19 17:37     ` Dr. David Alan Gilbert
2006-05-19 17:56       ` David Lang

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='e4kmte$bpc$1@sea.gmane.org' \
    --to=lexington.luthor@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox