All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Rödel" <joro@8bytes.org>
To: Carlos Bilbao <carlos.bilbao@amd.com>
Cc: svsm-devel@coconut-svsm.dev, Roy Hopkins <roy.hopkins@suse.com>
Subject: Re: [svsm-devel] [RFC] task/schedule: Idle process?
Date: Thu, 7 Sep 2023 10:47:16 +0200	[thread overview]
Message-ID: <ZPmGEFGYVQtQF9uT@8bytes.org> (raw)
In-Reply-To: <9ff1416f-5436-9148-73e1-fdd72ceb6285@amd.com>

Hi Carlos,

On Wed, Sep 06, 2023 at 09:29:00AM -0500, Carlos Bilbao wrote:
> The PR for the scheduler (#64) is still under review. In traditional OSs,
> it makes sense to include an idle userspace process that does nothing and
> is always there to be scheduled. So I was wondering if we should do the
> same for the SVSM.
> 
> Currently, SVSM schedules the "root" task responsible for running the
> request loop. However, in the event of a SvsmReqError:FatalError, this
> process may terminate prematurely. This raises the question: should we
> introduce an idle process in SVSM, or is it irrelevant in that context?
> 
> My first intuition is that if we don't have an idle process, then the SVSM
> itself would terminate, and perhaps that would difficult further debugging
> of potential errors. Or maybe it would not?

Yes, we plan with an idle process. It will be the (kernel-only) process
that gives control back to the guest OS by switching the VMPL.

The idea is that we have a runqueue and execute tasks from that as
long as any of them is runable. Once no process is runable anymore the
idle task is selected by the scheduler and switches back to the guest
VMPL.

Regards,

	Joerg

  reply	other threads:[~2023-09-07  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 14:29 [svsm-devel] [RFC] task/schedule: Idle process? Carlos Bilbao
2023-09-07  8:47 ` Jörg Rödel [this message]
2023-09-07 13:35   ` Roy Hopkins

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=ZPmGEFGYVQtQF9uT@8bytes.org \
    --to=joro@8bytes.org \
    --cc=carlos.bilbao@amd.com \
    --cc=roy.hopkins@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.