qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Volkmar Sieh <Volkmar.Sieh@informatik.uni-erlangen.de>
To: qemu-devel@nongnu.org, info@faumachine.org
Cc: Volkmar.Sieh@informatik.uni-erlangen.de
Subject: [Qemu-devel] FAUmachine internal docs
Date: Thu, 5 Nov 2009 15:05:14 +0100	[thread overview]
Message-ID: <20091105140424.GA8267@faui31h.informatik.uni-erlangen.de> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1381 bytes --]

Hi!

> Hi list,
>
> there's been a lot of discussion about abstraction of hardware devices
> and machine description.
>
> Last Saturday I've been running into some developers from the University
> of Erlangen (FAU) who work on an x86 emulator, used to simulate machine
> failures (memory bit flips, hard drive failures) [1].
>
> The most interesting part of their project appears to be the hardware
> abstraction layer. So in the general discussion of creating a generic
> machine description, it might be a good idea to get them to contribute
> their experience to Qemu :-). Maybe we can learn about dead ends and
> unexplored alternatives from them.
>
> FAUmachine guys, it would be awesome if you could either point us to a
> thorough documentation of the device abstraction layers or give some
> overview in a reply to this email.

Here it is...:

	http://www.faumachine.org/internals.pdf

If there are any questions feel free to ask...!

> Alex
>
> [1] http://www.faumachine.org

        Volkmar
-- 
Dr.-Ing. Volkmar Sieh            Universität Erlangen-Nürnberg
                                 Lehrstuhl für Informatik 3 (Rechnerarchitektur)
                                 Department Informatik
Tel: +49(0)9131/8527911          Martensstr. 3
Fax: +49(0)9131/8527239          D-91058 Erlangen
sieh@informatik.uni-erlangen.de  Germany

                 reply	other threads:[~2009-11-05 14:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20091105140424.GA8267@faui31h.informatik.uni-erlangen.de \
    --to=volkmar.sieh@informatik.uni-erlangen.de \
    --cc=info@faumachine.org \
    --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).