From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=48715 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OPJli-0007El-LZ
	for qemu-devel@nongnu.org; Thu, 17 Jun 2010 14:24:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1OPJlh-0004QC-Ke
	for qemu-devel@nongnu.org; Thu, 17 Jun 2010 14:24:50 -0400
Received: from mail2.shareable.org ([80.68.89.115]:44268)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1OPJlh-0004Q2-G9
	for qemu-devel@nongnu.org; Thu, 17 Jun 2010 14:24:49 -0400
Date: Thu, 17 Jun 2010 19:24:44 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] VLIW?
Message-ID: <20100617182444.GD4979@shareable.org>
References: <2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A46216@NASANEXMB07.na.qualcomm.com>
	<4C190CC6.9090400@twiddle.net>
	<2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A463D0@NASANEXMB07.na.qualcomm.com>
	<4C1A4716.90102@twiddle.net>
	<2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A46410@NASANEXMB07.na.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2CEA5ECB5C60A7469530D1EA92A1ABBB04C9A46410@NASANEXMB07.na.qualcomm.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Gibbons, Scott" <sgibbons@qualcomm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Richard Henderson <rth@twiddle.net>

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