This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Xen PV audio XenStore

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen PV audio XenStore
From: George Boutsioukis <gboutsioukis@xxxxxxxxx>
Date: Tue, 5 Jul 2011 00:16:41 +0200
Delivery-date: Mon, 04 Jul 2011 15:17:39 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=ENxmJiLPZqbhlZ72taW3u7WVY8KGHh78BbxsWluz/eQ=; b=fH7LBEHoohEcYhihuBS8D0pnFwxNxThjV0zG6H1m1Iz4bEcq0i0GWfmrbFBlxFDhVc hOpRx6ebOrK6YsWUwSBVeoXsDd7C8J2ga9Iql84uQJ2tdRQ1ldRfAz6LdtLzc4cpNEuT QIl63rxOW45w5bx8kzH9KSy+VNRguAMq7axuE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello everyone, as some of you may remember there is a GSoC project
this year to implement a paravirtualized audio driver and I am the
student undertaking this effort.

As the rest of the PV audio drivers, my frontend uses XenStore to pass
the event channel & grant reference to the backend, along with a few
configuration data. Although the driver is far from usable, the
XenStore layout is not going to change much in the future, so I think
it would be useful to describe it to the community.

First of all, although the frontend is implemented in userspace, I
tried to follow the scheme used by the rest of the PV drivers. This
looks something like:


where devID is a unique device ID for the guest system.

Accordingly the backend will use something like:


which will likely be a way for the backend to advertise the
capabilities of the sound hardware to the guests and perhaps pass a
few other parameters.
This looked like the simplest way to go. Of course I'm only new here
and I might be missing something grave, so please let me know what you

George Boutsioukis

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>