From: Jamie Lokier <jamie@shareable.org>
To: "Gibbons, Scott" <sgibbons@qualcomm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] VLIW?
Date: Thu, 17 Jun 2010 19:24:44 +0100 [thread overview]
Message-ID: <20100617182444.GD4979@shareable.org> (raw)
In-Reply-To: <2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A46410@NASANEXMB07.na.qualcomm.com>
Gibbons, Scott wrote:
> My architecture is an Interleaved Multithreading VLIW architecture. One bundle (packet) executes per processor cycle, rotating between threads (i.e., thread 0 executes at time 0, thread 1 executes at time 1, then thread 0 executes at time 2, etc.). Each thread has its own context (including a program counter). I'm not sure what kind of performance I would get in translating a single bundle at a time (or maybe I'm misunderstanding).
>
> I think I'll get basic single-thread operation working first, then attempt multithreading when I have a spare month or so.
I know of another CPU architecture that has fine-grained hardware
threads and has working qemu emulation at a useful performance for
debugging kernels, but it's not public as far as I know, and I don't
know if it's ok to name it. I don't think it's VLIW, only that it has
lots of hardware threads and a working qemu model.
-- Jamie
next prev parent reply other threads:[~2010-06-17 18:24 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
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 [this message]
-- 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=20100617182444.GD4979@shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).