1. 14 Feb, 2023 2 commits
  2. 11 Feb, 2023 1 commit
  3. 10 Feb, 2023 1 commit
  4. 09 Feb, 2023 1 commit
  5. 08 Feb, 2023 3 commits
  6. 04 Feb, 2023 2 commits
    • Mark Brown's avatar
      kselftest/alsa: Run PCM tests for multiple cards in parallel · 69218b59
      Mark Brown authored
      With each test taking 4 seconds the runtime of pcm-test can add up. Since
      generally each card in the system is physically independent and will be
      unaffected by what's going on with other cards we can mitigate this by
      testing each card in parallel. Make a list of cards as we enumerate the
      system and then start a thread for each, then join the threads to ensure
      they have all finished. The threads each run the same tests we currently
      run for each PCM on the card before exiting.
      
      The list of PCMs is kept global since it helps with global operations
      like working out our planned number of tests and identifying missing PCMs
      and it seemed neater to check for PCMs on the right card in the card
      thread than make every PCM loop iterate over cards as well.
      
      We don't run per-PCM tests in parallel since in embedded systems it can
      be the case that resources are shared between the PCMs and operations on
      one PCM on a card may constrain what can be done on another PCM on the same
      card leading to potentially unstable results.
      
      We use a mutex to ensure that the reporting of results is serialised and we
      don't have issues with anything like the current test number, we could do
      this in the kselftest framework but it seems like this might cause problems
      for other tests that are doing lower level testing and building in
      constrained environments such as nolibc so this seems more sensible.
      
      Note that the ordering of the tests can't be guaranteed as things stand,
      this does not seem like a major problem since the numbering of tests often
      changes as test programs are changed so results parsers are expected to
      rely on the test name rather than the test numbers. We also now prefix the
      machine generated test name when printing the description of the test since
      this is logged before streaming starts.
      
      On my two card desktop system this reduces the overall runtime by a
      third.
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      Link: https://lore.kernel.org/r/20230203-alsa-pcm-test-card-thread-v1-1-59941640ebba@kernel.orgSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      69218b59
    • Takashi Sakamoto's avatar
      ALSA: fireface: add field for the number of messages copied to user space · 0d9eb7ed
      Takashi Sakamoto authored
      Current structure includes no field to express the number of messages
      copied to user space, thus user space application needs to information
      out of the structure to parse the content of structure.
      
      This commit adds a field to express the number of messages copied to user
      space since It is more preferable to use self-contained structure.
      
      Kees Cook proposed an idea of annotation for bound of flexible arrays
      in his future improvement for flexible-length array in kernel. The
      additional field for message count is suitable to the idea as well.
      
      Reference: https://people.kernel.org/kees/bounded-flexible-arrays-in-cSigned-off-by: default avatarTakashi Sakamoto <o-takashi@sakamocchi.jp>
      Link: https://lore.kernel.org/r/20230202133708.163936-1-o-takashi@sakamocchi.jpSigned-off-by: default avatarTakashi Iwai <tiwai@suse.de>
      0d9eb7ed
  7. 03 Feb, 2023 1 commit
  8. 31 Jan, 2023 2 commits
  9. 29 Jan, 2023 1 commit
  10. 25 Jan, 2023 2 commits
  11. 23 Jan, 2023 5 commits
  12. 19 Jan, 2023 1 commit
  13. 18 Jan, 2023 3 commits
  14. 17 Jan, 2023 2 commits
  15. 13 Jan, 2023 8 commits
  16. 12 Jan, 2023 5 commits