All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Grzegorz Milos <gm281@cam.ac.uk>
Cc: Patrick Colp <pjcolp@cs.ubc.ca>,
	xen-devel@lists.xensource.com,
	Andrew Peace <Andrew.Peace@eu.citrix.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] Paging and memory sharing for HVM guests
Date: Thu, 17 Dec 2009 11:38:45 -0500	[thread overview]
Message-ID: <20091217163845.GA26398@phenom.dumpdata.com> (raw)
In-Reply-To: <db8ce2bd0912161514s7a162546gf7f5909db22e274c@mail.gmail.com>

On Wed, Dec 16, 2009 at 11:14:47PM +0000, Grzegorz Milos wrote:
> The series of 46 patches attached to this email contain the initial
> implementation of memory paging and sharing for Xen. Patrick Colp
> leads the work on the pager, and I am mostly responsible for memory
> sharing. We would be grateful for any comments/suggestions you might
> have. Individual patches are labeled with comments describing their
> purpose and a sign-off footnote. Of course we are happy to discuss
> them in more detail, as required. Assuming that there are no major
> objections against including them in the mainstream xen-unstable tree,
> we would like to move future development to that tree.


Congrats!

And now to the tiny review I did:

1). mem_event_xen_core.patch

"Copyright (c) 2009 Citrix (R)&D) Ltd. (Patrick Colp)"

The lawyers might not like it the copyright being assigned to a non-existent
entity :-(


2).  mem_paging_xen_pfec_page_paged.patch:

15 +    if ( p2m_is_paging(p2mt) )
 16 +    {
 17 +//        if ( p2m_is_paged(p2mt) )

I think you can safely remove the commented out code.

3). mem_sharing_xen_mm.patch:

 27 +    /*
 28 +     * Initialise our DOMID_IO domain.
                                ^^->COW
 29 +     * This domain owns sharable pages.
 30 +     */
 31 +    dom_cow = domain_create(DOMID_COW, DOMCRF_dummy, 0);


4), mem_sharing_tools_eagain.patch

The code spins with a 1 second timeout forever. Would it make sense
to include a retry counter so that, say after an hour (or maybe something
much smaller) you give up?

In the pv-ops patch series:

1). The  "*mfnp |= 0x80000000U;" and "*mfnp |= 0xf0000000U;" should
    use a #define. Maybe copy over the #defines from the xen tree ?

  parent reply	other threads:[~2009-12-17 16:38 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 23:14 [PATCH] Paging and memory sharing for HVM guests Grzegorz Milos
2009-12-16 23:52 ` Dan Magenheimer
2009-12-17  0:00   ` Patrick Colp
2009-12-17  0:15     ` Dan Magenheimer
2009-12-17  8:47 ` Jan Beulich
2009-12-17 13:08   ` Grzegorz Milos
2009-12-17 15:11     ` Patrick Colp
2009-12-17 11:19 ` Jan Beulich
2009-12-17 15:59   ` Keir Fraser
2009-12-17 18:34     ` Jeremy Fitzhardinge
2009-12-17 16:19 ` Dan Magenheimer
2009-12-18 18:05   ` Dan Magenheimer
2009-12-18 18:51     ` Patrick Colp
2009-12-20 15:04     ` Grzegorz Milos
2009-12-21 16:52       ` Dan Magenheimer
2009-12-17 16:38 ` Konrad Rzeszutek Wilk [this message]
2009-12-17 16:59   ` Jan Beulich
2009-12-17 17:05     ` Patrick Colp
2009-12-18  8:08       ` Jan Beulich
2009-12-18 17:29         ` Patrick Colp
2009-12-18 18:36           ` Konrad Rzeszutek Wilk
2009-12-18 18:54             ` Patrick Colp
2009-12-17 18:27     ` Konrad Rzeszutek Wilk
2009-12-17 17:02   ` Patrick Colp
2009-12-17 17:26     ` Patrick Colp
2009-12-17 19:47 ` Jeremy Fitzhardinge
2009-12-17 20:08   ` Patrick Colp
2009-12-17 20:15     ` Jeremy Fitzhardinge
2009-12-17 20:16       ` Jeremy Fitzhardinge
2009-12-17 20:22         ` Patrick Colp
2009-12-18 16:00 ` Jan Beulich
2009-12-18 17:16   ` Patrick Colp
2009-12-22 10:49 ` Jan Beulich
2009-12-22 11:34   ` Keir Fraser
2009-12-22 12:56     ` Jan Beulich
2009-12-22 13:35       ` Keir Fraser
2010-01-04 14:14 ` Jan Beulich
2010-01-04 15:32   ` Keir Fraser
2010-01-04 16:30     ` Jan Beulich
2010-01-05  7:51       ` Jan Beulich

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=20091217163845.GA26398@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Andrew.Peace@eu.citrix.com \
    --cc=gm281@cam.ac.uk \
    --cc=keir.fraser@eu.citrix.com \
    --cc=pjcolp@cs.ubc.ca \
    --cc=xen-devel@lists.xensource.com \
    /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.