general high-level discussion about spectrum
 help / color / mirror / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: discuss@spectrum-os.org
Cc: Demi Marie Obenour <demiobenour@gmail.com>
Subject: Re: This Week in Spectrum, 2025-W25
Date: Mon, 23 Jun 2025 14:04:24 +0200	[thread overview]
Message-ID: <87jz521x6f.fsf@alyssa.is> (raw)
In-Reply-To: <87ms9y1xf2.fsf@alyssa.is>

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

Alyssa Ross <hi@alyssa.is> writes:

> Demi has been getting familiar with the Cloud Hypervisor codebase by
> finding and fixing various safety issues in it.  We expect her to be
> doing a lot more work on Cloud Hypervisor in future, and this is a good
> on-ramp that's already resulting in upstream improvements.  So far two
> PRs have been accepted, and another is still in progress.

Oh, and Demi also sent her first patch to Spectrum[1], which with
everything else I haven't had a chance to review yet, and got some good
discussions with kernel developers[2] going on how we might solve the
interrupt remapping problem[3] on x86_64.

[1]: https://spectrum-os.org/lists/archives/spectrum-devel/2ff17d00-6603-46ae-9eb0-d4fa179db86c@gmail.com/
[2]: https://lore.kernel.org/linux-iommu/a65d955c-192b-4e79-ab11-8e2af78b62af@gmail.com/
[3]: https://pad.lassul.us/s/mDfFPvHjA#Cloud-Hypervisor-support-interrupt-remapping-inside-x86_64-guests

That's what happens when I leave writing the update until right before
my self-imposed deadline. ;)

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

      reply	other threads:[~2025-06-23 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 11:59 This Week in Spectrum, 2025-W25 Alyssa Ross
2025-06-23 12:04 ` Alyssa Ross [this message]

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=87jz521x6f.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --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).