All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: libvir-list@redhat.com, Jim Fehlig <jfehlig@suse.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] libxl: include a XLU_Config in _libxlDriverConfig
Date: Thu, 7 May 2015 09:57:06 +0100	[thread overview]
Message-ID: <20150507085706.GA29004__36463.3129247979$1430989125$gmane$org@zion.uk.xensource.com> (raw)
In-Reply-To: <20150507082023.GA20349@aepfle.de>

On Thu, May 07, 2015 at 10:20:23AM +0200, Olaf Hering wrote:
> On Wed, May 06, Wei Liu wrote:
> 
> > On Wed, May 06, 2015 at 10:58:11AM +0200, Olaf Hering wrote:
> > > On Wed, May 06, Olaf Hering wrote:
> > > 
> > > > Since libvirtd runs forever there is very little code to undo most
> > > > things. But I will see if there is any unload function, did not actively
> > > > look for such thing.
> > > 
> > > Looking through libxlStateDriver it seems that libxl and libxlu remains
> > > as is. Not sure if thats supposed that way or if perhaps libxl should be
> > > fully reinitialized during ->stateReload, and if logfiles should be
> > > closed in ->stateCleanup.
> > > 
> > 
> > FWIW libxl ctx is destroy in libxlDriverConfigDispose. You can probably
> > just call xlu_cfg_destroy there.
> 
> In libvirt libxlDriverConfigDispose calls both libxl_ctx_free and
> xtl_logger_destroy. Both functions check if the input is valid, just
> xlu_cfg_destroy dereferences the input unconditionally. Should
> xlu_cfg_destroy be changed to do nothing if it gets passed a NULL
> pointer?
> 

That is orthogonal to this patch. I don't particularly care if it's
NULL-tolerant or not. In any case,  You will need to check validity for
older libxl's xlu_cfg_destroy.

Wei.

> Olaf

  parent reply	other threads:[~2015-05-07  8:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  6:40 [PATCH] libxl: include a XLU_Config in _libxlDriverConfig Olaf Hering
2015-05-05  7:54 ` Wei Liu
     [not found] ` <20150505075434.GA26431@zion.uk.xensource.com>
2015-05-06  8:07   ` Olaf Hering
     [not found]   ` <20150506080759.GA10182@aepfle.de>
2015-05-06  8:58     ` Olaf Hering
     [not found]     ` <20150506085811.GA28064@aepfle.de>
2015-05-06  9:13       ` Wei Liu
2015-05-06 15:08       ` Jim Fehlig
     [not found]       ` <20150506091345.GD23664@zion.uk.xensource.com>
2015-05-06 15:12         ` Jim Fehlig
2015-05-07  8:20         ` Olaf Hering
     [not found]         ` <20150507082023.GA20349@aepfle.de>
2015-05-07  8:57           ` Wei Liu [this message]
2015-05-06 15:16 ` Jim Fehlig
     [not found] <1429292679-32340-1-git-send-email-olaf@aepfle.de>
2015-04-17 20:06 ` Jim Fehlig
  -- strict thread matches above, loose matches on Subject: below --
2015-04-17 17:44 Olaf Hering

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='20150507085706.GA29004__36463.3129247979$1430989125$gmane$org@zion.uk.xensource.com' \
    --to=wei.liu2@citrix.com \
    --cc=jfehlig@suse.com \
    --cc=libvir-list@redhat.com \
    --cc=olaf@aepfle.de \
    --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.