From: Takashi Iwai <tiwai@suse.de>
To: "Raphaël Dingé" <raphael.dinge@ohmforce.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Can't detect "XRUNs"
Date: Wed, 04 Jul 2018 16:02:41 +0200 [thread overview]
Message-ID: <s5hd0w3w132.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAL-i0qHv-W0Qva1QW6FUUj04P=F41_Q4X1TWaYoZXCjHB7bXoA@mail.gmail.com>
On Wed, 04 Jul 2018 15:49:51 +0200,
Raphaël Dingé wrote:
>
> Hi Takashi,
>
> >> No event gets logged.
> >
> > Are you testing with XRUN injection? I found that the code path
> > doesn't trigger the event tracing. The patch below should trigger the
> > tracing event with xrun injection as well.
>
> I'm testing with a real program with an extreme test that can't be
> completed on time most of the times.
>
> Maybe I should first apply your patch and trigger a synthesised xrun
> with xrun_injection to see if I'm not missing something else.
Yes, it makes more sense.
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2018-07-04 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 10:26 Can't detect "XRUNs" Raphaël Dingé
2018-07-04 10:33 ` Takashi Iwai
2018-07-04 10:38 ` Raphaël Dingé
2018-07-04 12:11 ` Raphaël Dingé
2018-07-04 13:16 ` Takashi Iwai
2018-07-04 13:49 ` Raphaël Dingé
2018-07-04 14:02 ` Takashi Iwai [this message]
2018-07-04 14:16 ` Raphaël Dingé
2018-07-04 15:11 ` Raphaël Dingé
2018-07-04 15:14 ` Takashi Iwai
2018-07-04 15:16 ` Raphaël Dingé
2018-07-04 15:49 ` Raphaël Dingé
2018-07-04 15:56 ` Takashi Iwai
2018-07-04 16:06 ` Raphaël Dingé
2018-07-05 9:10 ` Raphaël Dingé
2018-07-05 10:05 ` Takashi Iwai
2018-07-05 10:59 ` Raphaël Dingé
2018-07-05 12:34 ` Raphaël Dingé
2018-07-05 15:02 ` Takashi Iwai
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=s5hd0w3w132.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=raphael.dinge@ohmforce.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox