All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: anthony.perard@citrix.com, stefano.stabellini@eu.citrix.com,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/5] libxl: remove DM path in libxl__device_model_destroy
Date: Wed, 18 Mar 2015 13:23:03 +0000	[thread overview]
Message-ID: <1426684983.14291.26.camel@citrix.com> (raw)
In-Reply-To: <1426684863.14291.24.camel@citrix.com>

On Wed, 2015-03-18 at 13:21 +0000, Ian Campbell wrote:
> On Fri, 2015-03-13 at 10:34 +0000, Wei Liu wrote:
> > ... because it is the right place to clean up device model stuffs.
> 
> ... and not devices_destroy_cb because it is the right ...
> 
> (also "stuff").
> 
> > And the path should use LIBXL_TOOLSTACK_DOMID instead of hardcoded 0.
> 
> Between this and what is in the next patch I think you probably should
> refactor into a helper function to get the correct path for a given
> domid.
> 
> FWIW I think you might also be able to do:
>         GCSPRINTF("/local/domain/" #LIBXL_TOOLSTACK_DOMID "/device-model/%d",
>                   domid);
> 
> If you want, although perhaps the intention is for it to eventually not
> be a hard-define of 0 and become e.g. a function call or a global
> variable reference, in which case best not?

Having reread patch #0 more carefully I suppose the helper would need to
take the dm_domid too, which would then rule out that cpp trick.

Ian.

  reply	other threads:[~2015-03-18 13:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 10:34 [PATCH 0/5] Fix QEMU startup protocol Wei Liu
2015-03-13 10:34 ` [PATCH 1/5] libxl: remove DM path in libxl__device_model_destroy Wei Liu
2015-03-18 13:21   ` Ian Campbell
2015-03-18 13:23     ` Ian Campbell [this message]
2015-03-13 10:34 ` [PATCH 2/5] libxl: use LIBXL_TOOLSTACK_DOMID Wei Liu
2015-03-18 13:21   ` Ian Campbell
2015-03-13 10:34 ` [PATCH 3/5] libxl: use new QEMU xenstore protocol Wei Liu
2015-03-18 13:30   ` Ian Campbell
2015-03-19 10:36     ` Wei Liu
2015-03-19 10:55       ` Ian Campbell
2015-03-19 11:04         ` Wei Liu
2015-03-13 10:34 ` [PATCH 4/5] libxl: wait for stubdom to be ready Wei Liu
2015-03-16 17:55   ` Wei Liu
2015-03-18 13:35   ` Ian Campbell
2015-03-19 10:46     ` Wei Liu
2015-03-13 10:34 ` [PATCH 5/5] Revert "x86/hvm: wait for at least one ioreq server to be enabled" Wei Liu
2015-03-13 11:32   ` Paul Durrant
2015-03-13 10:38 ` [PATCH] xenstore: use relative path for device-model node Wei Liu
2015-03-13 10:46   ` Ian Campbell
2015-03-13 11:01     ` Wei Liu
2015-03-13 11:04   ` Stefano Stabellini
2015-03-18 13:24   ` Ian Campbell
2015-03-19 10:54     ` Wei Liu
2015-03-19 11:04       ` Ian Campbell
2015-03-24 17:16   ` Ian Jackson

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=1426684983.14291.26.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.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.