All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Andrii Anisov <andrii_anisov@epam.com>
Cc: Artem Mygaiev <artem_mygaiev@epam.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>,
	Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>
Subject: Re: [XenSummit 2017] Shared coprocessor framework followup
Date: Mon, 31 Jul 2017 22:42:52 +0200	[thread overview]
Message-ID: <20170731204252.GW4859@toto> (raw)
In-Reply-To: <4ee2be1b-5fd3-c439-ea56-483f9ab8f0cb@epam.com>

On Tue, Jul 18, 2017 at 08:10:15PM +0300, Andrii Anisov wrote:
> **Dear All,
> 
> During the developers summit a Shared Coprocessor Framework (SCF) concept
> was presented. Noticeable interest from community was discovered during
> discussions. So this is a call for all interested parties to collect a
> feedback and setup a collaboration.

Hi Andrii!


> 
> There are several topics I would like to collect responses from the
> community:
>     - Who are interested in SCF design, discussions, development, usage,
> etc? Personalities or organizations.

Yes I'm interested in this. I'm not sure how much time I'll be able to
contribute but at least I can review proposals and hopefully look at
implementing a driver/backend that may be useful for our FPGA platforms.

Cheers,
Edgar


>     - What devices (type of devices) are intended to be shared using SCF?
>     - What are expected coprocessor sharing use-cases (i.e. DSP running
> different FW for different domains, etc).
>     - If someone is willing to take a part in SCF design and development
> (core, API)?
>     - If someone is willing to implement their coprocessor support (driver)
> for SCF?
> 
> I look forward to hearing from you.
> 
> -- 
> 
> *Andrii Anisov*
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-07-31 20:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 17:10 [XenSummit 2017] Shared coprocessor framework followup Andrii Anisov
2017-07-31 20:42 ` Edgar E. Iglesias [this message]
2017-08-01 11:52   ` Andrii Anisov
2017-08-01 14:56     ` Edgar E. Iglesias
2017-08-01 17:04       ` Andrii Anisov
2017-08-01 17:13         ` Edgar E. Iglesias
2017-08-02 11:07           ` Andrii Anisov
2017-08-02 12:58             ` Edgar E. Iglesias
2017-08-02 13:50               ` Andrii Anisov
2017-08-16  9:56                 ` Andrii Anisov

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=20170731204252.GW4859@toto \
    --to=edgar.iglesias@gmail.com \
    --cc=Oleksandr_Andrushchenko@epam.com \
    --cc=Oleksandr_Tyshchenko@epam.com \
    --cc=andrii_anisov@epam.com \
    --cc=artem_mygaiev@epam.com \
    --cc=xen-devel@lists.xenproject.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.