From: Ian Campbell <ian.campbell@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] libxc: unify handling of vNUMA layout
Date: Wed, 17 Jun 2015 12:13:35 +0100 [thread overview]
Message-ID: <1434539615.13744.324.camel@citrix.com> (raw)
In-Reply-To: <55708251.5060607@oracle.com>
On Thu, 2015-06-04 at 12:52 -0400, Boris Ostrovsky wrote:
> On 06/04/2015 06:23 AM, Wei Liu wrote:
> > This patch does the following:
> > 1. Use local variables for dummy vNUMA layout in PV case.
> > 2. Avoid leaking dummy layout back to caller in PV case.
> > 3. Use local variables to reference vNUMA layout (whether it is dummy
> > or provided by caller) for both PV and HVM.
> >
> > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
>
>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Acked + applied, thanks.
prev parent reply other threads:[~2015-06-17 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 10:23 [PATCH] libxc: unify handling of vNUMA layout Wei Liu
2015-06-04 16:52 ` Boris Ostrovsky
2015-06-17 11:13 ` Ian Campbell [this message]
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=1434539615.13744.324.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=wei.liu2@citrix.com \
--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.