From: Dario Faggioli <dfaggioli@suse.com>
To: "Anders Törnqvist" <anders.tornqvist@codiax.se>,
"Julien Grall" <julien@xen.org>,
xen-devel@lists.xenproject.org,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: Null scheduler and vwfi native problem
Date: Mon, 25 Jan 2021 16:45:04 +0100 [thread overview]
Message-ID: <3e7a9989b35ac05c668f6dd7310faad682989b33.camel@suse.com> (raw)
In-Reply-To: <8eef0e27-63bc-5202-9857-8143c94acd04@codiax.se>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
On Fri, 2021-01-22 at 18:44 +0100, Anders Törnqvist wrote:
> Listing vcpus looks like this when the domain is running:
>
> xl vcpu-list
> Name ID VCPU CPU State Time(s)
> Affinity (Hard / Soft)
> Domain-0 0 0 0 r-- 101.7 0 /
> all
> Domain-0 0 1 1 r-- 101.0 1 /
> all
> Domain-0 0 2 2 r-- 101.0 2 /
> all
> Domain-0 0 3 3 r-- 100.9 3 /
> all
> Domain-0 0 4 4 r-- 100.9 4 /
> all
> mydomu 1 0 5 r-- 89.5 5 /
> all
>
> vCPU nr 0 is also for dom0. Is that normal?
>
Yeah, that's the vCPU IDs numbering. Each VM/guest (including dom0) has
its vCPUs and they have ID starting from 0.
What counts here, to make sure that the NULL scheduler "configuration"
is correct, is that each VCPU is associated to one and only one PCPU.
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-25 15:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 10:54 Null scheduler and vwfi native problem Anders Törnqvist
2021-01-21 18:32 ` Dario Faggioli
2021-01-21 19:40 ` Julien Grall
2021-01-21 23:35 ` Dario Faggioli
2021-01-22 8:06 ` Anders Törnqvist
2021-01-22 9:05 ` Dario Faggioli
2021-01-22 14:26 ` Julien Grall
2021-01-22 17:44 ` Anders Törnqvist
2021-01-25 15:45 ` Dario Faggioli [this message]
2021-01-25 16:11 ` Dario Faggioli
2021-01-26 17:03 ` Anders Törnqvist
2021-01-26 22:31 ` Dario Faggioli
2021-01-29 8:08 ` Anders Törnqvist
2021-01-29 8:18 ` Jürgen Groß
2021-01-29 10:16 ` Dario Faggioli
2021-02-01 6:53 ` Anders Törnqvist
2021-01-30 17:59 ` Dario Faggioli
2021-02-01 6:55 ` Anders Törnqvist
2021-02-02 7:59 ` Julien Grall
2021-02-02 15:03 ` Dario Faggioli
2021-02-02 15:23 ` Julien Grall
2021-02-03 7:31 ` Dario Faggioli
2021-02-03 9:19 ` Julien Grall
2021-02-03 11:00 ` Jürgen Groß
2021-02-03 11:20 ` Julien Grall
2021-02-03 12:02 ` Jürgen Groß
2021-02-15 7:15 ` Anders Törnqvist
2021-01-22 14:02 ` Julien Grall
2021-01-22 17:30 ` Anders Törnqvist
2021-01-22 8:07 ` Anders Törnqvist
2021-01-21 19:16 ` Julien Grall
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=3e7a9989b35ac05c668f6dd7310faad682989b33.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=anders.tornqvist@codiax.se \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).