All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v9 10/15] tools/libxc: x86 HVM save code
Date: Wed, 15 Apr 2015 12:29:07 +0100	[thread overview]
Message-ID: <1429097347.15516.213.camel@citrix.com> (raw)
In-Reply-To: <552BC2BE.2020406@citrix.com>

On Mon, 2015-04-13 at 14:21 +0100, Andrew Cooper wrote:
> >> +static int write_hvm_params(struct xc_sr_context *ctx)
> >> +{
> >> +    static const unsigned int params[] = {
[...]
> > While reviewing my 'soft reset' series Ian C raised a question about the
> > unsafeness of sequential get/set of HVM params:
> > http://lists.xen.org/archives/html/xen-devel/2015-01/msg01177.html
> >[...]
> This code currently mirrors what the old migration did.  This was one
> area we deliberately didn't try to clean up (we were focusing on a
> functional replacement).

Apart from what else you say (which I agree with) I think all Vitaly was
asking here was whether your params[] array could be moved into a
location which was accessible to the rest of libxc.

In any case I would say it would be fine for the second user to refactor
out any list which the first one added. Gentlemen, start your
engines ;-)

Ian.

  reply	other threads:[~2015-04-15 11:29 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 17:15 [PATCH v9 00/15] Migration v2 (libxc) Andrew Cooper
2015-04-10 17:15 ` [PATCH v9 01/15] tools/libxc: Implement writev_exact() in the same style as write_exact() Andrew Cooper
2015-04-15 10:44   ` Ian Campbell
2015-04-10 17:15 ` [PATCH v9 02/15] libxc/progress: Extend the progress interface Andrew Cooper
2015-04-15 10:55   ` Ian Campbell
2015-04-20 13:15     ` Andrew Cooper
2015-04-22 15:38       ` Ian Campbell
2015-04-10 17:15 ` [PATCH v9 03/15] tools/libxc: Migration v2 framework Andrew Cooper
2015-04-15 10:57   ` Ian Campbell
2015-04-10 17:15 ` [PATCH v9 04/15] tools/libxc: C implementation of stream format Andrew Cooper
2015-04-15 10:59   ` Ian Campbell
2015-04-10 17:15 ` [PATCH v9 05/15] tools/libxc: noarch common code Andrew Cooper
2015-04-15 11:00   ` Ian Campbell
2015-04-10 17:15 ` [PATCH v9 06/15] tools/libxc: x86 " Andrew Cooper
2015-04-10 17:15 ` [PATCH v9 07/15] tools/libxc: x86 PV " Andrew Cooper
2015-04-15 11:07   ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 08/15] tools/libxc: x86 PV save code Andrew Cooper
2015-04-15 11:13   ` Ian Campbell
2015-04-15 11:41     ` Andrew Cooper
2015-04-15 11:52       ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 09/15] tools/libxc: x86 PV restore code Andrew Cooper
2015-04-15 11:22   ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 10/15] tools/libxc: x86 HVM save code Andrew Cooper
2015-04-13 12:28   ` Vitaly Kuznetsov
2015-04-13 13:21     ` Andrew Cooper
2015-04-15 11:29       ` Ian Campbell [this message]
2015-04-15 11:30   ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 11/15] tools/libxc: x86 HVM restore code Andrew Cooper
2015-04-15 11:31   ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 12/15] tools/libxc: noarch save code Andrew Cooper
2015-04-15 11:34   ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 13/15] tools/libxc: noarch restore code Andrew Cooper
2015-04-15 11:42   ` Ian Campbell
2015-04-15 11:50     ` Andrew Cooper
2015-04-15 11:53       ` Ian Campbell
2015-04-10 17:16 ` [PATCH v9 14/15] docs: libxc migration stream specification Andrew Cooper
2015-04-15 11:46   ` Ian Campbell
2015-04-15 12:05     ` Andrew Cooper
2015-04-15 12:11       ` Ian Campbell
2015-04-15 12:02   ` David Vrabel
2015-04-15 12:09     ` Andrew Cooper
2015-04-10 17:16 ` [PATCH v9 15/15] tools/libxc: Migration v2 compatibility for unmodified libxl Andrew Cooper
2015-04-15 11:51   ` Ian Campbell
2015-04-15 12:14     ` Andrew Cooper
2015-04-15 12:52       ` Ian Campbell

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=1429097347.15516.213.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=vkuznets@redhat.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.