From: malc <av1474@comtv.ru>
To: Nat Gurumoorthy <ngurumoorthy@ubicom.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help multi thread support.
Date: Wed, 7 Oct 2009 15:26:29 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0910071521001.2148@linmac.oyster.ru> (raw)
In-Reply-To: <CB2DD11991B27C4F99935E6229450D320352316C@STORK.scenix.com>
On Tue, 6 Oct 2009, Nat Gurumoorthy wrote:
> Hi,
> I am trying to add support for Ubicom 32 bit processors in QEMU.
> These cpus have 10 - 12 hardware threads. The current versions have no
> mmu. The threads do run independent of each other. How do I expose such
> capabilities to QEMU. There is a flag "-cpu" which seems to allow
> specification of multiple cores. Would I be using that? I still have to
> figure out how to deal with cases where registers writes by one thread
> affect the execution of another hardware thread.
IP3K i'd guess? There are multiple challenges with Ubicom's CPUs, one
being deterministic schedulling which might imply every TB being only
one instruction big, anyways support for this beast is very interesting.
--
mailto:av1474@comtv.ru
prev parent reply other threads:[~2009-10-07 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 22:26 [Qemu-devel] Help multi thread support Nat Gurumoorthy
2009-10-07 11:26 ` malc [this message]
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=Pine.LNX.4.64.0910071521001.2148@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=ngurumoorthy@ubicom.com \
--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).