qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Derek Fawcus <dfawcus@cisco.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The QEMU Accelerator Module
Date: Fri, 11 Feb 2005 16:09:10 +0000	[thread overview]
Message-ID: <20050211160909.G12093@mrwint.cisco.com> (raw)
In-Reply-To: <420BEEB7.1010906@bellard.org>; from fabrice@bellard.org on Fri, Feb 11, 2005 at 12:31:03AM +0100

Well,
  rather than whinging because Fabrice has not chosen to distribute his
work under your preferred licence.  People could simply reimplement it.

Mind - this involves effort on their behalf,  and some thinking.  So it's
certainly easier to moan.  However I suggest that such moaning is simply
a waste of time and effort.

Now I don't know how Fabrice has done the kqemu module,  but the obvious
approach that springs to mind is simply moving the qemu-fast processing
into the kernel with checks for the address boundary.  So if I was to
attempt to reimplement it,  my starting point would be to approach it
in that fashion.

Namely placing a version of cpu_exec() and/or main_loop() into the kernel
together with the use of the USE_CODE_COPY facility and some bounds checks
such that if the machine being emulated attempted to have accessable memory
above 0xc0000000 it would fall back to the user-space SOFT_MMU emulation.
One could then manipulate the process space such that while the kernel
module was running user space code,  it's process address space (< 0xc0000000)
reflected the emulated machine space.

However,  I've got other things to do,  so the above is not a priority,
and I'm quite happy to use Fabrice's module.  Mind - I need to update
to a more recent version of the code,  my current work is in a version
dating back to ~ September / October last year.

DF

  parent reply	other threads:[~2005-02-11 16:24 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 23:31 [Qemu-devel] The QEMU Accelerator Module Fabrice Bellard
2005-02-10 23:57 ` Grzegorz Kulewski
2005-02-11  1:00   ` Lennert Buytenhek
2005-02-11  1:27   ` Tim
2005-02-12 14:10   ` Fabrice Bellard
2005-02-12 15:28     ` Fabrice Bellard
2005-02-11  0:38 ` Darryl Dixon
2005-02-11  1:01   ` Hetz Ben Hamo
2005-02-11  1:20 ` Leigh Dyer
2005-02-11  2:11 ` James Mastros
2005-02-11  5:15 ` Tom Marble
2005-02-11  9:23   ` Karel Gardas
2005-02-11 10:52     ` Lionel Ulmer
2005-02-11 12:05       ` Karel Gardas
2005-02-11 13:44         ` Lionel Ulmer
2005-02-11 13:47     ` Grzegorz Kulewski
2005-02-11  9:54   ` [Qemu-devel] KQemu logic and marketing goals Jean-Michel POURE
2005-02-11 11:37     ` Lionel Ulmer
2005-02-11 12:27     ` Julian Seward
2005-02-11 12:48       ` Lennert Buytenhek
2005-02-11 13:17         ` Johannes Schindelin
2005-02-11 14:16           ` Lennert Buytenhek
2005-02-11 14:05       ` Jean-Michel POURE
2005-02-11 12:02   ` [Qemu-devel] The QEMU Accelerator Module Johannes Schindelin
2005-02-11 12:38     ` Jens Arm
2005-02-11 16:09 ` Derek Fawcus [this message]
2005-02-11 17:17   ` Jim C. Brown
2005-02-11 16:16 ` [Qemu-devel] " Anand Kumria
2005-02-11 21:33   ` Antti-Juhani Kaijanaho
2005-02-12  2:01   ` Johannes Schindelin
2005-02-12  3:23     ` Darryl Dixon
2005-02-12  4:06       ` Hetz Ben Hamo
2005-02-12  6:14     ` [Qemu-devel] " Anand Kumria
2005-02-12 16:19       ` Natalia Portillo
2005-02-12 17:04         ` Jean-Christian de Rivaz
2005-02-12 17:29         ` René Korthaus
2005-02-12 19:48           ` Natalia Portillo
2005-02-12 20:51             ` Jean-Christian de Rivaz
2005-02-13  0:07             ` René Korthaus
2005-02-11 16:22 ` [Qemu-devel] " Alexander E. Patrakov
2005-02-12  5:37 ` Ronald
2005-02-12 17:12 ` [Qemu-devel] " Felipe Sanchez
  -- strict thread matches above, loose matches on Subject: below --
2005-02-12 15:55 Bob Barry
2005-02-12 16:41 ` Hetz Ben Hamo
2005-02-12 16:59 ` Panagiotis Issaris

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=20050211160909.G12093@mrwint.cisco.com \
    --to=dfawcus@cisco.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).