All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: "Anthony PERARD" <anthony.perard@citrix.com>,
	"Jürgen Groß" <jgross@suse.com>,
	"Ian Jackson" <ian.jackson@eu.citrix.com>, "Wei Liu" <wl@xen.org>
Subject: [Xen-devel] [XEN PATCH for-4.13 0/6] Drop/deprecate libxl_get_required_*_memory
Date: Fri, 4 Oct 2019 16:17:01 +0100	[thread overview]
Message-ID: <20191004151707.24844-1-ian.jackson@eu.citrix.com> (raw)

libxl_get_required_shadow_memory has always been anomalous.  libxl
ought to default these things itself.  Recently, another analogous
setting, iommu_memkb, was introduced, along with another function
along the same lines.

This API is not very good.  Fixing it was not entirely trivial.
(Thanks to Paul for explaining some of the difficulties and Anthony
for in-principle review of my proposal.)

Ian Jackson (6):
  libxl: Offer API versions 0x040700 and 0x040800
  xl: Pass libxl_domain_config to freemem(), instead of b_info
  libxl: libxl__domain_config_setdefault: New function
  libxl: libxl_domain_need_memory: Make it take a domain_config
  libxl: Move shadow_memkb and iommu_memkb defaulting into libxl
  libxl: Remove/deprecate libxl_get_required_*_memory from the API

 tools/libxl/libxl.h          | 24 ++++++++++-
 tools/libxl/libxl_create.c   | 95 ++++++++++++++++++++++++++++++++++++++------
 tools/libxl/libxl_dom.c      |  7 ++--
 tools/libxl/libxl_internal.h | 10 +++++
 tools/libxl/libxl_mem.c      | 70 ++++++++++++++++++++++++++------
 tools/libxl/libxl_utils.c    | 15 -------
 tools/libxl/libxl_utils.h    |  2 +-
 tools/xl/xl_parse.c          | 15 +------
 tools/xl/xl_vmcontrol.c      |  6 +--
 9 files changed, 183 insertions(+), 61 deletions(-)

-- 
2.11.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-10-04 15:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 15:17 Ian Jackson [this message]
2019-10-04 15:17 ` [Xen-devel] [XEN PATCH for-4.13 1/6] libxl: Offer API versions 0x040700 and 0x040800 Ian Jackson
2019-10-04 15:33   ` Anthony PERARD
2019-10-04 16:08     ` Ian Jackson
2019-10-04 15:17 ` [Xen-devel] [XEN PATCH for-4.13 2/6] xl: Pass libxl_domain_config to freemem(), instead of b_info Ian Jackson
2019-10-04 17:24   ` Anthony PERARD
2019-10-04 15:17 ` [Xen-devel] [XEN PATCH for-4.13 3/6] libxl: libxl__domain_config_setdefault: New function Ian Jackson
2019-10-04 15:53   ` Anthony PERARD
2019-10-04 16:04     ` Ian Jackson
2019-10-04 17:25       ` Anthony PERARD
2019-10-07  9:57         ` Ian Jackson
2019-10-04 15:17 ` [Xen-devel] [XEN PATCH for-4.13 4/6] libxl: libxl_domain_need_memory: Make it take a domain_config Ian Jackson
2019-10-04 16:19   ` Anthony PERARD
2019-10-04 15:17 ` [Xen-devel] [XEN PATCH for-4.13 5/6] libxl: Move shadow_memkb and iommu_memkb defaulting into libxl Ian Jackson
2019-10-04 17:19   ` Anthony PERARD
2019-10-04 17:23     ` Ian Jackson
2019-10-04 15:17 ` [Xen-devel] [XEN PATCH for-4.13 6/6] libxl: Remove/deprecate libxl_get_required_*_memory from the API Ian Jackson
2019-10-04 17:24   ` Anthony PERARD
2019-10-07  6:45 ` [Xen-devel] [XEN PATCH for-4.13 0/6] Drop/deprecate libxl_get_required_*_memory Jürgen Groß

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=20191004151707.24844-1-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=jgross@suse.com \
    --cc=wl@xen.org \
    --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.