All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Geoffrey McRae <geoff@hostfission.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v8] audio/jack: add JACK client audiodev
Date: Mon, 11 May 2020 15:53:47 +0100	[thread overview]
Message-ID: <20200511145347.GD182627@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200511042538.60E863A0386@moya.office.hostfission.com>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

On Wed, Apr 29, 2020 at 03:53:58PM +1000, Geoffrey McRae wrote:
> This commit adds a new audiodev backend to allow QEMU to use JACK as
> both an audio sink and source.
> 
> Signed-off-by: Geoffrey McRae <geoff@hostfission.com>
> ---
>  audio/Makefile.objs    |   5 +
>  audio/audio.c          |   1 +
>  audio/audio_template.h |   2 +
>  audio/jackaudio.c      | 677 +++++++++++++++++++++++++++++++++++++++++
>  configure              |  17 ++
>  qapi/audio.json        |  56 +++-
>  6 files changed, 756 insertions(+), 2 deletions(-)
>  create mode 100644 audio/jackaudio.c

Cool! Out of interest, which emulated audio device do you use and have
you had issues with buffer sizes/latency?

I haven't reviewed in depth but in general this looks good.

> +typedef struct QJackBuffer {
> +    int          channels;
> +    int          frames;
> +    _Atomic(int) used;

stdatomic.h isn't used directly in QEMU. Can you use "qemu/atomic.h"
instead?

> +static inline int qjack_buffer_used(QJackBuffer *buffer)
> +{
> +    assert(buffer->data);
> +    return atomic_load_explicit(&buffer->used, memory_order_relaxed);
> +}

Is this function used?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-11 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  5:53 [PATCH v8] audio/jack: add JACK client audiodev Geoffrey McRae
2020-05-11 14:53 ` Stefan Hajnoczi [this message]
2020-05-11 14:58   ` Geoffrey McRae
2020-05-11 20:31 ` Eric Blake

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=20200511145347.GD182627@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=geoff@hostfission.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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.