From: Kamil Rytarowski <n54@gmx.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] NetBSD maintenance
Date: Sun, 23 Apr 2017 01:27:58 +0200 [thread overview]
Message-ID: <e1b08f20-77e6-83c8-85e6-b73c645c44c1@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
Hello,
I noted a call for NetBSD maintainers in the 2.9.0 release notes.
I'm willing to attach a NetBSD machine to CI cluster and volunteer basic
maintenance. I'm mostly interested in NetBSD as host & as guest as this
is my daily and work driver on my desktop and development machines.
If I understand correctly there is currently no infrastructure for CI:
http://wiki.qemu.org/Testing/ContinuousIntegration
I'm familiar with Python buildbot, I run a machine for the LLVM
toolchain with Clang and LLDB. This setup works very well and it's easy
to setup with minimal dependencies:
http://llvm.org/docs/HowToAddABuilder.html
My LLVM machine:
http://lab.llvm.org:8011/builders/lldb-amd64-ninja-netbsd7
Although, I plan to upgrade it pretty soon and rename, so look for
lldb-amd64-ninja-netbsd8.
As of today NetBSD patches for qemu are maintained in pkgsrc. There are
also at least DragonFly and SunOS (SmartOS) diffs available.
https://github.com/NetBSD/pkgsrc/tree/trunk/emulators/qemu/patches
Qemu is one of the core tools in NetBSD development and it's used in our
release engineering infrastructure:
http://releng.netbsd.org/test-results.html
I will start with upstreaming local diffs and move on to running tests.
I'm aware that there are lately issues with ACPI, APIC, SMP and certain
device drivers... but not everything at once.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2017-04-22 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 23:27 Kamil Rytarowski [this message]
2017-04-23 10:19 ` [Qemu-devel] NetBSD maintenance Peter Maydell
2017-04-23 22:45 ` Kamil Rytarowski
2017-04-24 7:26 ` Fam Zheng
2017-04-24 7:54 ` Kamil Rytarowski
2017-04-24 10:12 ` Peter Maydell
2017-04-25 13:49 ` Kamil Rytarowski
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=e1b08f20-77e6-83c8-85e6-b73c645c44c1@gmx.com \
--to=n54@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).