Skip to content

Question: details of "Our architecture provides hardware-enforced isolation between workloads" #2

Open
Open
Question: details of "Our architecture provides hardware-enforced isolation between workloads"#2

Description

@AkihiroSuda
AkihiroSuda
opened on Oct 13, 2026

multikernel.io/faq.html

Lines 129 to 134 in bda42c8

<div class="faq-item">
<div class="faq-question">
<i data-lucide="shield"></i> How does multikernel enhance security?
</div>
<p class="faq-answer">Our architecture provides hardware-enforced isolation between workloads, minimizes attack surfaces through tailored kernels, and supports confidential computing for sensitive data processing. By running applications directly in initramfs without a full OS, we further reduce the attack surface compared to traditional environments.</p>
</div>

multikernel.io/how-it-works.html

Lines 221 to 222 in bda42c8

<h3 class="feature-title">Isolation Without a Hypervisor</h3>
<p class="feature-description">Each workload has its own kernel, so a kernel bug or exploit in one cannot reach another. There is no hypervisor layer to pay for, and it works on bare metal or inside VMs you already run.</p>

I'd like to know the details of Our architecture provides hardware-enforced isolation between workloads and a kernel bug or exploit in one cannot reach another.

AFAICS a spawned kernel can easily read and write the entire physical memory, e.g., via /dev/mem.

I saw "Call for Hardware Enhancements" in your LPC 2025 slides, but could not find how they are actually implemented as of v7.0-mk3.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions