All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Luca Fancellu <luca.fancellu@arm.com>, xen-devel@lists.xenproject.org
Cc: bertrand.marquis@arm.com, wei.chen@arm.com,
	andrew.cooper3@citrix.com, Wei Liu <wl@xen.org>,
	Anthony PERARD <anthony.perard@citrix.com>
Subject: Re: [PATCH] tools/libxl: optimize domain creation skipping domain cpupool move
Date: Fri, 27 May 2022 15:46:13 +0200	[thread overview]
Message-ID: <91a372cb-2e4c-e738-a6bd-d65189bcd194@suse.com> (raw)
In-Reply-To: <20220526081230.3194-1-luca.fancellu@arm.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 705 bytes --]

On 26.05.22 10:12, Luca Fancellu wrote:
> Commit 92ea9c54fc81 ("arm/dom0less: assign dom0less guests to cpupools")
> introduced a way to start a domain directly on a certain cpupool,
> adding a "cpupool_id" member to struct xen_domctl_createdomain.
> 
> This was done to be able to start dom0less guests in different pools than
> cpupool0, but the toolstack can benefit from it because it can now use
> the struct member directly instead of creating the guest in cpupool0
> and then moving it to the target cpupool.
> 
> Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Signed-off-by: Luca Fancellu <luca.fancellu@arm.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2022-05-27 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26  8:12 [PATCH] tools/libxl: optimize domain creation skipping domain cpupool move Luca Fancellu
2022-05-27 13:46 ` Juergen Gross [this message]
2022-06-01 10:31 ` Anthony PERARD

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=91a372cb-2e4c-e738-a6bd-d65189bcd194@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=bertrand.marquis@arm.com \
    --cc=luca.fancellu@arm.com \
    --cc=wei.chen@arm.com \
    --cc=wl@xen.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 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.