general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: discuss@spectrum-os.org, devel@spectrum-os.org
Cc: Demi Marie Obenour <demiobenour@gmail.com>
Subject: This Week in Spectrum, 2025-W22
Date: Mon, 02 Jun 2025 13:40:01 +0200	[thread overview]
Message-ID: <87jz5ucqy6.fsf@alyssa.is> (raw)

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

This week I was once again mostly preoccupied with arranging continuing
funding.  If approved, this will be the biggest funding allocation
Spectrum has ever had, but with that comes a corresponding increase in
the work required to make it happen.  I also spent some time fixing
Nixpkgs build issues that would affect Spectrum in future.

That doesn't mean there hasn't been any exciting Spectrum work this
week, though.  Demi, whose name you may recognize from her extensive
past work on Qubes OS, submitted a patch to the VIRTIO specification to
add interrupt remapping capabilities to virtio-iommu on x86_64.  This is
an important requirement for being able to move implementations of
virtual devices into their own VMs, which will in turn enable running
hardware drivers in VMs rather than on the host, and it has been a
longstanding wish list item in Spectrum's upcoming projects list[1].
It's very exciting to have somebody as knowledgeable as Demi working
towards Spectrum's goals.

[1]: https://pad.lassul.us/s/mDfFPvHjA#Cloud-Hypervisor-support-interrupt-remapping-inside-x86_64-guests

BTW: From next week onwards, I think I'll start sending these updates
only to discuss@, not devel@, because I don't think it makes sense to
duplicate them.

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

                 reply	other threads:[~2025-06-02 11:40 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=87jz5ucqy6.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --cc=devel@spectrum-os.org \
    --cc=discuss@spectrum-os.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).