All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	xen-users@lists.xen.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Zhigang Wang <zhigang.x.wang@oracle.com>,
	marmarek@invisiblethingslab.com,
	"Ian.Campbell@citrix.com" <Ian.Campbell@citrix.com>
Subject: Intention to deprecate and remove some Python libxc bindings
Date: Fri, 9 Oct 2015 14:20:15 +0200	[thread overview]
Message-ID: <5617B0FF.10805@suse.com> (raw)

Mostly for historical reasons Xen includes Python bindings for libxc.
They have been used by xm/xend in the past but nowadays there is only
one usage in the Xen source tree: pygrub is using xc.xeninfo().

I wrote a patch to remove all libxc Python bindings but xc.xeninfo() and
got some feedback regarding out-of-tree users. Up to now there have been
reports of users of the following bindings:

     xc.getcpuinfo()
     xc.domain_getinfo()
     xc.tmem_control()
     xc.domain_set_target_mem()
     xc.domain_setmaxmem()
     xc.physinfo()
     xc.xeninfo()

Before removing all but above bindings I'd like to ask for any other
users of the libxc Python bindings. In case you are using one of those
and are planning to do so with Xen 4.7 and later, please stand up and
tell me, in order to keep the specific binding.

Just for reference: There are no known users of:

     xc.domain_create()
     xc.domain_max_vcpus()
     xc.domain_dumpcore()
     xc.domain_pause()
     xc.domain_unpause()
     xc.domain_destroy()
     xc.domain_destroy_hook()
     xc.domain_resume()
     xc.domain_shutdown()
     xc.vcpu_setaffinity()
     xc.domain_sethandle()
     xc.vcpu_getinfo()
     xc.linux_build()
     xc.getBitSize()
     xc.gnttab_hvm_seed()
     xc.hvm_get_param()
     xc.hvm_set_param()
     xc.get_device_group()
     xc.test_assign_device()
     xc.assign_device()
     xc.deassign_device()
     xc.sched_id_get()
     xc.sched_credit_domain_set()
     xc.sched_credit_domain_get()
     xc.sched_credit2_domain_set()
     xc.sched_credit2_domain_get()
     xc.evtchn_alloc_unbound()
     xc.evtchn_reset()
     xc.physdev_map_pirq()
     xc.physdev_pci_access_modify()
     xc.readconsolering()
     xc.topologyinfo()
     xc.numainfo()
     xc.shadow_control()
     xc.shadow_mem_control()
     xc.domain_set_memmap_limit()
     xc.domain_ioport_permission()
     xc.domain_irq_permission()
     xc.domain_iomem_permission()
     xc.pages_to_kib()
     xc.domain_set_time_offset()
     xc.domain_set_tsc_info()
     xc.domain_disable_migrate()
     xc.domain_send_trigger()
     xc.send_debug_keys()
     xc.domain_check_cpuid()
     xc.domain_set_cpuid()
     xc.domain_set_policy_cpuid()
     xc.domain_set_machine_address_size()
     xc.domain_suppress_spurious_page_faults()
     xc.tmem_shared_auth()
     xc.dom_set_memshr()
     xc.cpupool_create()
     xc.cpupool_destroy()
     xc.cpupool_getinfo()
     xc.cpupool_addcpu()
     xc.cpupool_removecpu()
     xc.cpupool_movedomain()
     xc.cpupool_freeinfo()
     xc.flask_context_to_sid()
     xc.flask_sid_to_context()
     xc.flask_load()
     xc.flask_getenforce()
     xc.flask_setenforce()
     xc.flask_access()


Juergen

                 reply	other threads:[~2015-10-09 12:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5617B0FF.10805@suse.com \
    --to=jgross@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@lists.xen.org \
    --cc=zhigang.x.wang@oracle.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.