All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <raistlin.df@gmail.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	libvir-list@redhat.com, Jim Fehlig <jfehlig@suse.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: libvirt/libxl implemetation of get_online_cpu / virNodeGetCPUMap?
Date: Wed, 25 Feb 2015 10:24:37 +0100	[thread overview]
Message-ID: <1424856277.4742.179.camel@gmail.com> (raw)
In-Reply-To: <1424783459.27930.337.camel@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1176 bytes --]

On Tue, 2015-02-24 at 13:10 +0000, Ian Campbell wrote:
> On Tue, 2015-02-24 at 12:41 +0000, Anthony PERARD wrote:

> > What libxl API those provide this information, if it exist?
> > 
> > I found libxl_get_online_cpus() but that not enough. They want a
> > bitmap.
> 
> I think that is all which currently exists, at least at the libxl level,
> you may need to add a new interface.
> 
> It'd be worth looking into the various host numa interfaces -- perhaps
> one of them indirectly exposes what you want?
> 
Given Daniel's latest emails, I'm not sure this is useful but
libxl_get_cpu_topology() should put LIBXL_CPUTOPOLOGY_INVALID_ENTRY in
all the fields of the i-eth element of the array it returns, if the
i-eth pcpu is offline (see the implementation of XEN_SYSCTL_topologyinfo
in xen/common/sysctl.c).

So, scanning that array and constructing the bitmap according to whether
or not we find that marker on the various elements would be the way to
go, I would say.

I've actually never tested this, i.e., I've never tried offlining a pcpu
on the host. I'll give it a go as soon as I find 5 minutes, and let know
if it works.

Regards,
Dario

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2015-02-25  9:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150224124101.GX1345@perard.uk.xensource.com>
2015-02-24 12:46 ` [libvirt] libvirt/libxl implemetation of get_online_cpu / virNodeGetCPUMap? Daniel P. Berrange
2015-02-24 13:10 ` Ian Campbell
     [not found] ` <20150224124644.GK21611@redhat.com>
2015-02-24 13:15   ` [libvirt] " Anthony PERARD
2015-02-24 13:22     ` Daniel P. Berrange
     [not found]     ` <20150224132219.GL21611@redhat.com>
2015-02-24 15:00       ` Anthony PERARD
2015-02-25 12:57         ` Daniel P. Berrange
2015-03-24  8:47         ` Manish Jaggi
     [not found] ` <1424783459.27930.337.camel@citrix.com>
2015-02-25  9:24   ` Dario Faggioli [this message]
2015-02-25  9:43     ` Ian Campbell
2015-02-25 15:03     ` [libvirt] " Daniel P. Berrange
2015-02-25 15:13       ` Ian Campbell
     [not found]       ` <1424877216.18290.9.camel@citrix.com>
2015-02-25 15:20         ` Daniel P. Berrange
     [not found]         ` <20150225152042.GN4263@redhat.com>
2015-02-25 15:30           ` Ian Campbell
2015-02-24 12:41 Anthony PERARD

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=1424856277.4742.179.camel@gmail.com \
    --to=raistlin.df@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jfehlig@suse.com \
    --cc=libvir-list@redhat.com \
    --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.