All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Tamas K Lengyel <tamas.lengyel@intel.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wl@xen.org>,
	George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [Xen-devel] [PATCH v9 1/5] xen/x86: Make hap_get_allocation accessible
Date: Mon, 24 Feb 2020 16:20:51 +0100	[thread overview]
Message-ID: <20200224152051.GS4679@Air-de-Roger> (raw)
In-Reply-To: <8ccfd49088b2c811415f0c09886133a936e460d2.1582310142.git.tamas.lengyel@intel.com>

On Fri, Feb 21, 2020 at 10:49:19AM -0800, Tamas K Lengyel wrote:
> During VM forking we'll copy the parent domain's parameters to the client,
> including the HAP shadow memory setting that is used for storing the domain's
> EPT. We'll copy this in the hypervisor instead doing it during toolstack launch
> to allow the domain to start executing and unsharing memory before (or
> even completely without) the toolstack.
> 
> Signed-off-by: Tamas K Lengyel <tamas.lengyel@intel.com>

Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>

I would also be fine with this merged into the respective patch where
hap_get_allocation gets called.

Thanks, Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2020-02-24 15:21 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 18:49 [Xen-devel] [PATCH v9 0/5] VM forking Tamas K Lengyel
2020-02-21 18:49 ` [Xen-devel] [PATCH v9 1/5] xen/x86: Make hap_get_allocation accessible Tamas K Lengyel
2020-02-24 15:20   ` Roger Pau Monné [this message]
2020-02-25 13:16     ` Jan Beulich
2020-02-25 13:21       ` Tamas K Lengyel
2020-02-21 18:49 ` [Xen-devel] [PATCH v9 2/5] xen: add parent_domid field to createdomain domctl Tamas K Lengyel
2020-02-21 21:02   ` Julien Grall
2020-02-21 21:35     ` Tamas K Lengyel
2020-02-21 22:34       ` Julien Grall
2020-02-21 22:53         ` Tamas K Lengyel
2020-02-21 23:18           ` Julien Grall
2020-02-21 23:31             ` Tamas K Lengyel
2020-02-24 15:44   ` Andrew Cooper
2020-02-24 15:55     ` Tamas K Lengyel
2020-02-21 18:49 ` [Xen-devel] [PATCH v9 3/5] xen/mem_sharing: VM forking Tamas K Lengyel
2020-02-24 12:39   ` Roger Pau Monné
2020-02-24 15:45     ` Tamas K Lengyel
2020-02-24 15:59       ` Roger Pau Monné
2020-02-24 22:14       ` Tamas K Lengyel
2020-02-25  9:40         ` Roger Pau Monné
2020-02-24 22:26       ` Tamas K Lengyel
2020-02-25  9:40         ` Roger Pau Monné
2020-02-25 13:30       ` Jan Beulich
2020-02-25 13:28     ` Jan Beulich
2020-02-25 13:39       ` Tamas K Lengyel
2020-02-25 10:04   ` Roger Pau Monné
2020-02-25 11:43     ` Tamas K Lengyel
2020-02-25 12:06       ` Roger Pau Monné
2020-02-25 12:23         ` Tamas K Lengyel
2020-02-25 14:23           ` Tamas K Lengyel
2020-02-21 18:49 ` [Xen-devel] [PATCH v9 4/5] x86/mem_sharing: reset a fork Tamas K Lengyel
2020-02-24 15:12   ` Roger Pau Monné
2020-02-24 15:35     ` Tamas K Lengyel
2020-02-24 15:42       ` Roger Pau Monné
2020-02-24 15:49         ` Tamas K Lengyel
2020-02-24 16:02           ` Roger Pau Monné
2020-02-25 13:39       ` Jan Beulich
2020-02-25 13:45         ` Tamas K Lengyel
2020-02-25 14:13           ` Jan Beulich
2020-02-25 14:26             ` Tamas K Lengyel
2020-02-21 18:49 ` [Xen-devel] [PATCH v9 5/5] xen/tools: VM forking toolstack side Tamas K Lengyel
2020-02-24 16:12   ` Julien Grall
2020-02-24 16:19     ` Tamas K Lengyel
2020-02-24 16:30       ` Julien Grall
2020-02-24 16:45         ` Tamas K Lengyel

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=20200224152051.GS4679@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=tamas.lengyel@intel.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.