linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Adam Dunlap <acdunlap@google.com>
To: "Jörg Rödel" <joro@8bytes.org>
Cc: svsm-devel@coconut-svsm.dev, linux-coco@lists.linux.dev
Subject: Re: [svsm-devel] SVSM Development Call April 10th, 2024
Date: Wed, 10 Apr 2024 08:52:33 -0700	[thread overview]
Message-ID: <CAMBK9=bhzO3SFv+6439X=VZ6Raa2hAwVOKE7XN4U9DPJZyX_Ng@mail.gmail.com> (raw)
In-Reply-To: <ZhZfWhyOQ4ZmTdVP@8bytes.org>

Hi Jörg,

In light of the ahoi attacks (https://ahoi-attacks.github.io/) being
disclosed, it would be interesting to discuss what it would take for
coconut-svsm to enable restricted interrupt injection for vmpl3 to
protect a linux guest against maliciously injected interrupts.

Adam

On Wed, Apr 10, 2024 at 2:44 AM Jörg Rödel <joro@8bytes.org> wrote:
>
> Hi,
>
> Here is the usual call for agenda items for this weeks SVSM development
> call. I don't have agenda items so far, please send me yours or raise
> them during the meeting.
>
> Details of the meeting (GMeet and Calendar links, meeting time) can be
> found in our governance repository at:
>
>         https://github.com/coconut-svsm/governance
>
> The meeting will be recorded and the recording eventually published.
>
> See you all there.
>
> Regards,
>
>         Jörg
> --
> Svsm-devel mailing list
> Svsm-devel@coconut-svsm.dev
> https://mail.8bytes.org/cgi-bin/mailman/listinfo/svsm-devel

  reply	other threads:[~2024-04-10 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10  9:43 SVSM Development Call April 10th, 2024 Jörg Rödel
2024-04-10 15:52 ` Adam Dunlap [this message]
2024-04-11  7:20 ` [svsm-devel] " Jörg Rödel

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='CAMBK9=bhzO3SFv+6439X=VZ6Raa2hAwVOKE7XN4U9DPJZyX_Ng@mail.gmail.com' \
    --to=acdunlap@google.com \
    --cc=joro@8bytes.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=svsm-devel@coconut-svsm.dev \
    /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).