>> [...] compute/peripheral processors [...] abstraction [...]
> How about using/extending the ptrace API to handle this? It looks
> like the primitives required are the same (+mmap you mention).
> And it would make sense to be able to attach to a
> qemu/coprocessor-provided "process". [...]
>
Matt Thomas writes:
> A lot of systems are coming with compute/peripheral processors with
> limited ram, etc.
>
> I was wondering what the abstraction should be?
>
> Obviously, mmap()'ing their memory would be nice. But what about
> stopping/starting? Messaging?
How about using/extending the
Hi.
On 8 Oct 2013, at 11:13 AM, Michael wrote:
> on Monday 07 October 2013 18:50:53 Mouse wrote:
>
>> As for the minimal abstraction? Here's a strawman:
>>
>> - mmap to access the coprocessor's memory
>> - ways (read/write? ioctl?) to do various things:
>> - - halt
>> - - single-step
>> - - r
Hello,
on Monday 07 October 2013 18:50:53 Mouse wrote:
> As for the minimal abstraction? Here's a strawman:
>
> - mmap to access the coprocessor's memory
> - ways (read/write? ioctl?) to do various things:
> - - halt
> - - single-step
> - - run
> - - grab processor state (registers &c)
> - - set
Hello,
on Monday 07 October 2013 20:48:04 Masao Uebayashi wrote:
> On Tue, Oct 8, 2013 at 7:24 AM, Matt Thomas wrote:
> > A lot of systems are coming with compute/peripheral processors with
> > limited ram, etc.
>
> For example?
I guess he means things like the DSPs found in OMAP SoCs, SGI's VIC
On Tue, Oct 8, 2013 at 7:24 AM, Matt Thomas wrote:
>
> A lot of systems are coming with compute/peripheral processors with
> limited ram, etc.
For example?
How are those compute/peripheral processors connected?
> A lot of systems are coming with compute/peripheral processors with
> limited ram, etc.
> I was wondering what the abstraction should be?
> Obviously, mmap()'ing their memory would be nice. But what about
> stopping/starting? Messaging?
> Ideas are welcome.
I would suggest something minimal
A lot of systems are coming with compute/peripheral processors with
limited ram, etc.
I was wondering what the abstraction should be?
Obviously, mmap()'ing their memory would be nice. But what about
stopping/starting? Messaging?
Ideas are welcome.