All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: andrii.tseglytskyi@globallogic.com,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: [Xen Hackathon] new PV drivers
Date: Tue, 3 Jun 2014 12:47:40 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1406031243270.4779@kaball.uk.xensource.com> (raw)

Present (by memory):
- Julien Grall,
- Stefano Stabellini,
- Ian Campbell,
- Roger Pau Monne,
- Dario Faggioli,
- Andrii Tseglytskyi,
- David Vrabel,
- Konrad Wilk.

* What new PV devices do we need? What has been done already?
* Where should they live?


New PV Drivers, GlobalLogic has done:
- PV tiny-ALSA, very simple forwarding, backend in Linux, frontend is
  userspace, stand-alone. Could be in their own git tree on xenbits.
- Made old PV USB patches working, backend and frontend in Linux.
- Improved PVFB: do they use the backend in QEMU? Can be upstreamed?
- PV WPA supplicant, WIP with simple frontend and backend in Linux.

IPU support (TI). We need Remote Proc Framework working on Xen:
http://lwn.net/Articles/489009/
We need PV Remote Proc to have HD video reproduction in Android.
We could use an IOMMU to assign the IPU to the domU but the IPU is not
behind an IOMMU.
We could use a PV protocol to assign the IPU to one domain, using Remove
Proc to talk to the other DomU.
The PV protocol would be a simple protocol to assign the IPU to one
domain only.
Dom0 could allocate the initial memory for IPU, we are sure it is
contiguous in machine memory because it is mapped 1:1.
Dom0 need to translate the addresses on behalf of the guest.
A limited IOMMU is present between IPU and main memory. Dom0 could
program it with the memory for the IPU.

GPU support. At the moment GlobalLogic is mapping memory and irqs into the
guest. Possibility of creating a frontend/backend protocol.
We could virtualize GPU similarly to the ALSA protocol: virtual EGL or
OpenGL ES.

David: new PV protocols need a standard state machine, we should
document what a basic PV protocol looks like.

IanC: what about the security implication of assigning GPU and IPU to
guests? Is that a problem?
Andrii: For now, it is acceptable.

             reply	other threads:[~2014-06-03 11:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:47 Stefano Stabellini [this message]
2014-06-06 13:56 ` [Xen Hackathon] new PV drivers Anil Madhavapeddy
2014-06-08  0:02   ` Adam Wick
2014-06-09  9:02   ` Ian Campbell
2014-06-09  9:42     ` Stefano Stabellini
2014-06-09  9:45       ` Ian Campbell
2014-06-09 14:30       ` Boris Ostrovsky
2014-06-09 14:33         ` Ian Campbell
2014-06-09 14:39           ` Boris Ostrovsky
2014-06-09 14:43             ` Ian Campbell
2014-06-09 14:55               ` Boris Ostrovsky
2014-06-09 15:06                 ` Ian Campbell
2014-06-09 19:16                   ` Andy Smith

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=alpine.DEB.2.02.1406031243270.4779@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=xen-devel@lists.xensource.com \
    /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.