From: Richard Henderson <rth@twiddle.net>
To: "Gibbons, Scott" <sgibbons@qualcomm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] VLIW?
Date: Wed, 16 Jun 2010 10:41:26 -0700 [thread overview]
Message-ID: <4C190CC6.9090400@twiddle.net> (raw)
In-Reply-To: <2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A46216@NASANEXMB07.na.qualcomm.com>
On 06/15/2010 08:53 AM, Gibbons, Scott wrote:
> Has anyone done a port of QEMU to a VLIW architecture? I’m interested
> in seeing what was done.
Do you mean as guest or host? I presume guest.
There's not such a port in the main repository; I don't know
what might have been done privately.
It'll be a more difficult job if you have an open pipeline, but
even then I should think it could be done. It really depends on
the exact specification of your cpu.
For instance, with a closed pipeline, I think all you would need
to track during translation are the output temporaries. You would
translate each member instruction sequentially, but delay writeback
to the architectual register until the end of the vliw packet.
With an open pipeline, I imagine that you would model each exposed
architectural feature. For instance, if a load insn places its
result onto a bus in the cycle following the issue of the load,
then you could model the bus with a TCG register and have the
translator be responsible for issuing moves between the TCG
registers during appropriate cycles.
I imagine the difficulty increases (but not intractably) if you
want the translator to catch and signal user coding errors in the
vliw assembly. Though usually that's a job that can be performed
statically by the assembler...
r~
next prev parent reply other threads:[~2010-06-16 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 15:53 [Qemu-devel] VLIW? Gibbons, Scott
2010-06-16 15:54 ` Aurelien Jarno
2010-06-16 17:41 ` Richard Henderson [this message]
2010-06-17 15:12 ` Gibbons, Scott
2010-06-17 16:02 ` Richard Henderson
2010-06-17 18:05 ` Gibbons, Scott
2010-06-17 18:14 ` Richard Henderson
2010-06-17 18:24 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2010-06-15 22:57 Gibbons, Scott
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=4C190CC6.9090400@twiddle.net \
--to=rth@twiddle.net \
--cc=qemu-devel@nongnu.org \
--cc=sgibbons@qualcomm.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 NNTP newsgroup(s).