From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 11a082: doc: enable virtio-fs in tester kernel configs
Date: Thu, 10 Sep 2026 11:43:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1162236/000000-86f64a@github.com> (raw)
Branch: refs/heads/1162236
Home: https://github.com/bluez/bluez
Commit: 11a082740637d5116451964b54ceb6077fbb2ece
https://github.com/bluez/bluez/commit/11a082740637d5116451964b54ceb6077fbb2ece
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-10 (Thu, 10 Sep 2026)
Changed paths:
M doc/ci.config
M doc/tester.config
Log Message:
-----------
doc: enable virtio-fs in tester kernel configs
Add support for virtio-fs in tester configs.
Commit: 86f64a2e96dd1f6a571bf21c2fb0d2d766a22a56
https://github.com/bluez/bluez/commit/86f64a2e96dd1f6a571bf21c2fb0d2d766a22a56
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-10 (Thu, 10 Sep 2026)
Changed paths:
M doc/test-runner.rst
M tools/test-runner.c
Log Message:
-----------
tools: test-runner: use virtiofsd for filesystem passthrough
The 9p mount passthrough I/O is fairly CPU hungry and slow. This matters
for e.g. running Python in test-runner, since it has to read some amount
of files for startup.
Add support for virtio-fs, which is significantly less CPU intensive.
Enable it by default if /usr/libexec/virtiofsd is available, fall back
to 9p if virtiofsd not usable.
Before:
$ time make check-functional
real 2m9,736s
user 1m29,570s
sys 0m32,715s
After:
$ time make check-functional
real 1m35,703s
user 0m28,938s
sys 0m7,453s
Compare: https://github.com/bluez/bluez/compare/11a082740637%5E...86f64a2e96dd
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-10 18:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1162236/000000-86f64a@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox