qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@suse.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [RFC PATCH] s390x-linux-user
Date: Fri, 26 Jun 2009 18:49:43 +0200	[thread overview]
Message-ID: <200906261849.43746.uli@suse.de> (raw)

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

Hi!

Here's an alpha of the S/390 target I'm currently working on. So far, 
only the s390x-linux-user target is supported. No machine emulation, no 
31-bit or 24-bit addressing modes. The S/390 instruction set is 
gargantuan, and I implement instructions as they come along, which means 
that everything not emitted by GCC (and then some) is unimplemented. 
Nonetheless, it runs dynamically linked binaries from SLE11 and most of 
the stuff in /bin, including bash and vim. (You wouldn't believe how 
many binaries there require 128-bit floats...)

Besides the unimplemented instructions, the code still leaves a lot of 
room for improvement, especially for optimization. All condition code 
computation, for instance, is currently done in helper functions.

There is a very peculiar S/390 instruction called "EXECUTE". What it does 
is to take another instruction stored somewhere in memory, logical-OR 
the second byte of the instruction with the LSB of R0 and then execute 
the result, without changing the instruction in memory or the program 
counter. Any idea how to implement this in QEMU? Currently, I'm 
interpreting the couple of instructions that GCC uses EXECUTE with, but 
in the long run that would amount to implementing a second emulator...

CU
Uli

-- 
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

[-- Attachment #2: s390x-linux-user.patch.gz --]
[-- Type: application/x-gzip, Size: 26899 bytes --]

             reply	other threads:[~2009-06-26 16:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 16:49 Ulrich Hecht [this message]
2009-06-26 17:17 ` [Qemu-devel] [RFC PATCH] s390x-linux-user Blue Swirl
2009-06-26 17:40   ` Paul Brook
2009-06-26 17:46     ` Blue Swirl
2009-06-26 17:59       ` Paul Brook
2009-06-26 18:18         ` Paul Brook
2009-06-26 18:22         ` Blue Swirl
2009-06-26 18:39           ` Paul Brook
2009-06-26 19:07   ` Stuart Brady
2009-06-26 19:24     ` Paul Brook
2009-07-03 15:11     ` Ulrich Hecht

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=200906261849.43746.uli@suse.de \
    --to=uli@suse.de \
    --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).