All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 00 of 18] libxc: preparation for hypercall buffers + random cleanups
Date: Tue, 12 Oct 2010 15:16:18 +0100	[thread overview]
Message-ID: <patchbomb.1286892978@localhost.localdomain> (raw)

The following contains some clean ups in preparation for the hypercall
buffer patch series, plus some other bits a bobs which I happened to
notice while preparing that series.

The bulk is adding (and consistently using) specific libxc functions
for each XENMEM_* operation. This allows the memory management in
xc_memory_op to be greatly simplified by converting it to a purely
internal function.

Part of this involved adding variants of
xc_domain_memory_{increase_reservation,decrease_reservation,populate_physmap}
which return the actual number of succesful operations instead of
swallowing partial success and converting to failure.

Rather than add a difficult to detect API change by redefining the
meaning of the integer return value of these types I have instead
introduced new names for these functions in the form of
xc_domain_{increase_reservation,decrease_reservation,populate_physmap}. In
each case I have also added an xc_domain_*_exact variant which
maintains the semantics of the old xc_domain_memory_* functions.

For consistency xc_domain_memory_{set,get}_pod_target have now become
xc_domain_{set,get}_pod_target.

The bits which touch ia64 are not even compile tested since I do not
have access to a suitable userspace-capable cross compiler. However
they are relatively straightforward substitutions.

One patch in the series (#11/18) adds a "# XXX update" suffix to
QEMU_TAG. Rather than applying directly QEMU_TAG should be updated at
this point to include the qemu series posted alongside this one.

             reply	other threads:[~2010-10-12 14:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 14:16 Ian Campbell [this message]
2010-10-12 14:16 ` [PATCH 01 of 18] libxc: flask: use (un)lock pages rather than open coding m(un)lock Ian Campbell
2010-10-12 14:16 ` [PATCH 02 of 18] libxc: pass an xc_interface handle to page locking functions Ian Campbell
2010-10-12 14:16 ` [PATCH 03 of 18] libxc: remove unnecessary double indirection from xc_readconsolering Ian Campbell
2010-10-12 14:16 ` [PATCH 04 of 18] libxc: use correct size of struct xen_mc Ian Campbell
2010-10-12 14:16 ` [PATCH 05 of 18] libxc: add wrappers for XENMEM {increase, decrease}_reservation and populate_physmap Ian Campbell
2010-10-12 14:16 ` [PATCH 06 of 18] libxc: add xc_domain_memory_exchange_pages to wrap XENMEM_exchange Ian Campbell
2010-10-12 14:16 ` [PATCH 07 of 18] libxc: add xc_domain_add_to_physmap to wrap XENMEM_add_to_physmap Ian Campbell
2010-10-12 14:16 ` [PATCH 08 of 18] libxc: add xc_domain_maximum_gpfn to wrap XENMEM_maximum_gpfn Ian Campbell
2010-10-12 14:16 ` [PATCH 09 of 18] libxc: add xc_machphys_mfn_list to wrap XENMEM_machphys_mfn_list Ian Campbell
2010-10-12 14:16 ` [PATCH 10 of 18] libxc: add xc_maximum_ram_page to wrap XENMEM_maximum_ram_page Ian Campbell
2010-10-12 14:16 ` [PATCH 11 of 18] libxc: update QEMU_TAG and remove compatibility macro Ian Campbell
2010-10-12 14:16 ` [PATCH 12 of 18] libxc: make xc_memory_op library private Ian Campbell
2010-10-12 14:16 ` [PATCH 13 of 18] libxc: make do_memory_op's callers responsible for locking indirect buffers Ian Campbell
2010-10-12 14:16 ` [PATCH 14 of 18] libxc: simplify performance counters API Ian Campbell
2010-10-12 14:16 ` [PATCH 15 of 18] libxc: simplify lock profiling API Ian Campbell
2010-10-12 14:16 ` [PATCH 16 of 18] libxc: drop xc_get_max_pages Ian Campbell
2010-10-12 14:16 ` [PATCH 17 of 18] libxc: do not lock VCPU context in xc_ia64_pv_recv_vcpu_context Ian Campbell
2010-10-12 14:16 ` [PATCH 18 of 18] libxc: use generic xc_get_pfn_list on ia64 Ian Campbell
2010-10-18 16:43 ` [PATCH 00 of 18] libxc: preparation for hypercall buffers + random cleanups Ian Jackson
2010-10-19  8:25   ` 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=patchbomb.1286892978@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.