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>,
Anthony PERARD <anthony.perard@citrix.com>,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH 2/3] tools/libxc: change xc_memshr_fork_reset API to match hypervisor
Date: Thu, 5 May 2022 10:17:21 +0200 [thread overview]
Message-ID: <YnOIEb9sNfshZwtZ@Air-de-Roger> (raw)
In-Reply-To: <f3fdd4e99892549dc68e7511f2d84f51af446e86.1651073086.git.tamas.lengyel@intel.com>
On Wed, Apr 27, 2022 at 11:34:19AM -0400, Tamas K Lengyel wrote:
> Need to separately specify if the reset is for the memory or for the VM state,
> or both.
>
> Signed-off-by: Tamas K Lengyel <tamas.lengyel@intel.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
Thanks.
next prev parent reply other threads:[~2022-05-05 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:34 [PATCH 1/3] x86/mem_sharing: make fork_reset more configurable Tamas K Lengyel
2022-04-27 15:34 ` [PATCH 2/3] tools/libxc: change xc_memshr_fork_reset API to match hypervisor Tamas K Lengyel
2022-05-04 13:10 ` Tamas K Lengyel
2022-05-05 8:17 ` Roger Pau Monné [this message]
2022-05-12 13:46 ` Tamas K Lengyel
2022-05-18 15:01 ` Tamas K Lengyel
2022-05-18 15:48 ` Jan Beulich
2022-05-18 17:03 ` Tamas K Lengyel
2022-05-19 6:03 ` Jan Beulich
2022-04-27 15:34 ` [PATCH 3/3] x86/monitor: Add new monitor event to catch all vmexits Tamas K Lengyel
2022-04-28 13:55 ` Roger Pau Monné
2022-04-28 14:02 ` Tamas K Lengyel
2022-05-04 13:12 ` Tamas K Lengyel
2022-05-12 13:47 ` Tamas K Lengyel
2022-05-18 15:02 ` Tamas K Lengyel
2022-05-20 0:35 ` Tian, Kevin
2022-05-20 14:05 ` Lengyel, Tamas
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=YnOIEb9sNfshZwtZ@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=jgross@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.