All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Türkyılmaz" <ozan.turkyilmaz@gmail.com>
To: dfeustel@mindspring.com, qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Cell processor
Date: Wed, 16 Nov 2005 20:00:48 +0200	[thread overview]
Message-ID: <b465f34b0511161000w6818acc2j@mail.gmail.com> (raw)
In-Reply-To: <200511161232.37855.dfeustel@verizon.net>

On 16/11/05, Dave Feustel <dfeustel@verizon.net> wrote:
> On Wednesday 16 November 2005 11:42, Paul Brook wrote:
> > On Wednesday 16 November 2005 13:10, Lars Roland wrote:
> > > On 11/16/05, Dave Feustel <dfeustel@verizon.net> wrote:
> > > > Is there any chance that simulation of the
> > > > IBM Cell processor will be added to Qemu?
> > >
> > > Although this would be great, I am not sure how easy it is to get a
> > > accurate simulation of this chip. The cell architecture consists of
> > > both a power processor element (PPE) and 8 synergistic processor
> > > elements (SPEs) while the PPE is a conventional microprocessor the
> > > SPEs are far from so
> > >
> > > The point of the cell is to get the PPE to prepare tasks that can be
> > > executed in a parallel distributed manner across all the SPEs and I am
> > > afraid that this scheduling is going to be very hard to implement
> > > correctly - I may however be proven wrong.
> >
> > It depends how accurate you want the simulation to be. A cycle accurate
> > simulator is probably going to be trickier. If you don't need cycle accuracy
> > it shouldn't be worse than any other multiprocessor system.
> >
> > The only real fundamental missing feature in QEMU is SMP guest support.
> > The main PPE is a virtual 2-way 64-bit PowerPC core. Qemu ppc64 is currently
> > incomplete, but that's fixable.
> >
> > I'd expect the SPE to be very easy to emulate. These are simple RISC vector
> > cores with their own local memory, no MMU, and a DMA/mailbox engine to
> > communicate with the rest of the system.
> >
> > It's a significant amount of work, but other than the SMP issue (which needs
> > fixing for other targets anyway) it's not excessively hard.
>
> Slightly off topic, but AMD has just announced its intention to ship a 4-core
> Opteron chip in 2007. The 4-core chip will use AMD's upcoming m2 socket.
>
isn't writing a OS for dual (or n) core chips hell ?

> > Paul
> >
>
> --
> Switch to Secure OpenBSD with a KDE desktop!!!
> NOW with Virtual PC OS support via QEMU and
> Beowulf clustering using PETSc and MPICH2!
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>


--
Ozan

  reply	other threads:[~2005-11-16 18:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 12:30 [Qemu-devel] Cell processor Dave Feustel
2005-11-16 13:10 ` Lars Roland
2005-11-16 13:26   ` Lars Roland
2005-11-16 14:12     ` Dave Feustel
2005-11-16 14:15     ` Dave Feustel
2005-11-16 14:40     ` Karel Gardas
2005-11-16 16:42   ` Paul Brook
2005-11-16 17:32     ` Dave Feustel
2005-11-16 18:00       ` Ozan Türkyılmaz [this message]
2005-11-16 18:08         ` Paul Brook
2005-11-16 19:03         ` Dave Feustel
2005-11-16 13:34 ` Henrik Nordstrom

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=b465f34b0511161000w6818acc2j@mail.gmail.com \
    --to=ozan.turkyilmaz@gmail.com \
    --cc=dfeustel@mindspring.com \
    --cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.