From: Geoff Levand <geoffrey.levand@am.sony.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 6/16] cell: abstract spu management routines
Date: Sun, 12 Nov 2006 20:34:13 -0800 [thread overview]
Message-ID: <4557F5C5.7080604@am.sony.com> (raw)
In-Reply-To: <1163391081.7410.65.camel@localhost.localdomain>
Michael Ellerman wrote:
> On Fri, 2006-11-10 at 12:01 -0800, Geoff Levand wrote:
>> This adds a platform specific spu management abstraction and the coresponding
>> routines to support the IBM Cell Blade. It also removes the hypervisor only
>> resources that were included in struct spu.
>>
>> Three new platform specific routines are introduced, spu_enumerate_spus(),
>> spu_create_spu() and spu_destroy_spu(). The underlining design uses a new
>> type, struct spu_management_ops, to hold function pointers that the platform
>> setup code is expected to initialize to instances appropriate to that platform.
>>
>> For the IBM Cell Blade support, I put the hypervisor only resources that were
>> in struct spu into a platform specific data structure struct spu_pdata.
>
> As far as I can see you haven't posted your HV-backed management ops, is
> that right?
Yes, that is in '[PATCH 15/16] cell: add ps3 platform spu support' posted
with the other ps3pf patches.
> Why can't your PS3 platform code fake-up device nodes for SPUs? It seems
> that would simplify this quite a lot.
Seems like a hack to me. My concern is that I just have to keep adding some
extra hack for every new spu feature that comes out. I would prefer to make
a proper design from the start, but if anyone can be more convincing I am
open to suggestions.
-Geoff
next prev parent reply other threads:[~2006-11-13 4:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 20:01 [PATCH 6/16] cell: abstract spu management routines Geoff Levand
2006-11-13 4:11 ` Michael Ellerman
2006-11-13 4:34 ` Geoff Levand [this message]
2006-11-14 2:01 ` Michael Ellerman
2006-11-14 2:56 ` Geoff Levand
2006-11-14 3:13 ` Michael Ellerman
2006-11-14 11:32 ` Geoff Levand
2006-11-14 3:44 ` Michael Ellerman
2006-11-14 9:55 ` Arnd Bergmann
2006-11-14 10:50 ` Geoff Levand
2006-11-15 0:07 ` Michael Ellerman
2006-11-15 0:47 ` Geoff Levand
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=4557F5C5.7080604@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.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).