From: Wei Liu <wei.liu2@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Olaf Hering <ohering@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Regression in xen-unstable due to commit 3802ecbaa9eb36
Date: Thu, 16 May 2019 12:24:48 +0100 [thread overview]
Message-ID: <20190516112448.GV2798@zion.uk.xensource.com> (raw)
In-Reply-To: <20190516104540.7hiqsn6qjeaam2c6@Air-de-Roger>
On Thu, May 16, 2019 at 12:45:40PM +0200, Roger Pau Monné wrote:
> On Thu, May 16, 2019 at 11:07:35AM +0200, Olaf Hering wrote:
> > Am Thu, 16 May 2019 10:09:38 +0200
> > schrieb Juergen Gross <jgross@suse.com>:
> >
> > > The patch "libxl: add helper function to set device_model_version"
> > > breaks creating any domain for me.
> >
> > The issue is, create_domain will eventually call freemem.
> > If autoballoon is set, due to dom0_mem= for example, all is fine.
> > If memory has to be freed, libxl_domain_need_memory will get an
> > incomplete b_info. Somehow the new libxl__domain_set_device_model
> > must be called for the d_config returned by parse_config_data.
> >
> > How should this be fixed?
>
> Having a field in build_info with a default value that depends on
> fields outside of build_info is problematic, since not all callers of
> libxl__domain_build_info_setdefault have access to libxl_domain_config.
>
> An option would be to pass libxl_domain_config to
> libxl__domain_build_info_setdefault and fixup the callers. That seems
> like the best solution ATM, but it would require reverting the
That will 1) make the name wrong 2) you will have to conjure up a
domain_config structure even if it is not needed...
Wei.
> currently committed patches, since there won't be a reason anymore to
> split the device model selection code out of
> libxl__domain_build_info_setdefault.
>
> Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Wei Liu <wei.liu2@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Olaf Hering <ohering@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Regression in xen-unstable due to commit 3802ecbaa9eb36
Date: Thu, 16 May 2019 12:24:48 +0100 [thread overview]
Message-ID: <20190516112448.GV2798@zion.uk.xensource.com> (raw)
Message-ID: <20190516112448.qtc-nyrriDwPMuzNi0jFWfVtPsfV7UK6qP8a2Cxu8zU@z> (raw)
In-Reply-To: <20190516104540.7hiqsn6qjeaam2c6@Air-de-Roger>
On Thu, May 16, 2019 at 12:45:40PM +0200, Roger Pau Monné wrote:
> On Thu, May 16, 2019 at 11:07:35AM +0200, Olaf Hering wrote:
> > Am Thu, 16 May 2019 10:09:38 +0200
> > schrieb Juergen Gross <jgross@suse.com>:
> >
> > > The patch "libxl: add helper function to set device_model_version"
> > > breaks creating any domain for me.
> >
> > The issue is, create_domain will eventually call freemem.
> > If autoballoon is set, due to dom0_mem= for example, all is fine.
> > If memory has to be freed, libxl_domain_need_memory will get an
> > incomplete b_info. Somehow the new libxl__domain_set_device_model
> > must be called for the d_config returned by parse_config_data.
> >
> > How should this be fixed?
>
> Having a field in build_info with a default value that depends on
> fields outside of build_info is problematic, since not all callers of
> libxl__domain_build_info_setdefault have access to libxl_domain_config.
>
> An option would be to pass libxl_domain_config to
> libxl__domain_build_info_setdefault and fixup the callers. That seems
> like the best solution ATM, but it would require reverting the
That will 1) make the name wrong 2) you will have to conjure up a
domain_config structure even if it is not needed...
Wei.
> currently committed patches, since there won't be a reason anymore to
> split the device model selection code out of
> libxl__domain_build_info_setdefault.
>
> Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-16 11:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 8:09 Regression in xen-unstable due to commit 3802ecbaa9eb36 Juergen Gross
2019-05-16 8:09 ` [Xen-devel] " Juergen Gross
2019-05-16 8:27 ` Olaf Hering
2019-05-16 8:27 ` [Xen-devel] " Olaf Hering
2019-05-16 8:29 ` Juergen Gross
2019-05-16 8:29 ` [Xen-devel] " Juergen Gross
2019-05-16 8:30 ` Olaf Hering
2019-05-16 8:30 ` [Xen-devel] " Olaf Hering
2019-05-16 8:34 ` Juergen Gross
2019-05-16 8:34 ` [Xen-devel] " Juergen Gross
2019-05-16 8:40 ` Olaf Hering
2019-05-16 8:40 ` [Xen-devel] " Olaf Hering
2019-05-16 8:50 ` Olaf Hering
2019-05-16 8:50 ` [Xen-devel] " Olaf Hering
2019-05-16 8:54 ` Juergen Gross
2019-05-16 8:54 ` [Xen-devel] " Juergen Gross
2019-05-16 9:07 ` Olaf Hering
2019-05-16 9:07 ` [Xen-devel] " Olaf Hering
2019-05-16 10:45 ` Roger Pau Monné
2019-05-16 10:45 ` [Xen-devel] " Roger Pau Monné
2019-05-16 10:57 ` Olaf Hering
2019-05-16 10:57 ` [Xen-devel] " Olaf Hering
2019-05-16 11:24 ` Wei Liu
2019-05-16 11:24 ` [Xen-devel] " Wei Liu
2019-05-16 11:38 ` Olaf Hering
2019-05-16 11:38 ` [Xen-devel] " Olaf Hering
2019-05-16 11:50 ` Wei Liu
2019-05-16 11:50 ` [Xen-devel] " Wei Liu
2019-05-16 12:04 ` Olaf Hering
2019-05-16 12:04 ` [Xen-devel] " Olaf Hering
2019-05-16 12:18 ` Olaf Hering
2019-05-16 12:18 ` [Xen-devel] " Olaf Hering
2019-05-16 12:50 ` Wei Liu
2019-05-16 12:50 ` [Xen-devel] " Wei Liu
2019-05-16 11:52 ` Olaf Hering
2019-05-16 11:52 ` [Xen-devel] " Olaf Hering
2019-05-16 11:42 ` Roger Pau Monné
2019-05-16 11:42 ` [Xen-devel] " Roger Pau Monné
2019-05-16 12:42 ` Wei Liu
2019-05-16 12:42 ` [Xen-devel] " Wei Liu
2019-05-16 11:24 ` Wei Liu [this message]
2019-05-16 11:24 ` Wei Liu
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=20190516112448.GV2798@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=ohering@suse.com \
--cc=roger.pau@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.