From: Tamas K Lengyel <tamas@tklengyel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Tamas K Lengyel" <tamas.lengyel@intel.com>,
"Wei Liu" <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v8 3/5] xen/mem_sharing: VM forking
Date: Fri, 21 Feb 2020 11:08:06 -0700 [thread overview]
Message-ID: <CABfawh=mizacs_L3v-UaxdNG5G=eTncEPu-GX__70ryNfE3J6g@mail.gmail.com> (raw)
In-Reply-To: <24288f4e-36da-f701-9709-ca3acc1f815a@citrix.com>
> One question needing considering is whether such a hypercall could in
> theory be useful without the mem_sharing infrastructure, or not. (i.e.
> how tightly integrated we should aim for.)
It would be possible to create domain forks without mem_sharing. The
mem_sharing part just adds an extra optimization on top so we don't
end up copying all accessed pages needlessly, we only do that when the
page is written to. In one of the earlier revisions of the series
(~v4) due to a bug we actually ran the system with all pages being
deduplicated and no mem_sharing and it was working just fine. I'm not
sure if that's what you were asking though :)
Tamas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-21 18:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 19:21 [Xen-devel] [PATCH v8 0/5] VM forking Tamas K Lengyel
2020-02-10 19:21 ` [Xen-devel] [PATCH v8 1/5] x86/p2m: Allow p2m_get_page_from_gfn to return shared entries Tamas K Lengyel
2020-02-11 9:16 ` Jan Beulich
2020-02-11 10:29 ` Tamas K Lengyel
2020-02-11 11:04 ` Jan Beulich
2020-02-11 13:34 ` Tamas K Lengyel
2020-02-21 13:48 ` Andrew Cooper
2020-02-21 14:21 ` Tamas K Lengyel
2020-02-10 19:21 ` [Xen-devel] [PATCH v8 2/5] xen/x86: Make hap_get_allocation accessible Tamas K Lengyel
2020-02-10 19:21 ` [Xen-devel] [PATCH v8 3/5] xen/mem_sharing: VM forking Tamas K Lengyel
2020-02-21 13:43 ` Andrew Cooper
2020-02-21 14:02 ` Andrew Cooper
2020-02-21 14:22 ` Tamas K Lengyel
2020-02-21 14:42 ` Andrew Cooper
2020-02-21 17:07 ` Tamas K Lengyel
2020-02-21 17:47 ` Andrew Cooper
2020-02-21 17:56 ` Tamas K Lengyel
2020-02-21 18:08 ` Tamas K Lengyel [this message]
2020-02-10 19:21 ` [Xen-devel] [PATCH v8 4/5] x86/mem_sharing: reset a fork Tamas K Lengyel
2020-02-10 19:21 ` [Xen-devel] [PATCH v8 5/5] xen/tools: VM forking toolstack side 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='CABfawh=mizacs_L3v-UaxdNG5G=eTncEPu-GX__70ryNfE3J6g@mail.gmail.com' \
--to=tamas@tklengyel.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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 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).