All of lore.kernel.org
 help / color / mirror / Atom feed
* High Level Design - OPW project "CPU/RAM/PCI diagram tool"
@ 2014-10-17  3:25 Rita Sinha
  2014-10-29 17:57 ` Dario Faggioli
  0 siblings, 1 reply; 2+ messages in thread
From: Rita Sinha @ 2014-10-17  3:25 UTC (permalink / raw)
  To: Xen-devel; +Cc: Andrew Cooper

Hi,

I am looking to work on the CPU/RAM/PCI Diagram tool project for
Outreach Program For Women - Round9.

Having discussed with my mentor, we have agreed that a good first step
is to attempt a tool which draws a graphical  representation of numa
nodes and the distribution of the VMs vcpus and memory. This email is
intended as a high level design.

I wish to get the host topology information which is normally
available in the APCI tables which identify Numa nodes and cpus inside
those nodes so we plan to  parse the ACPI tables manually. The
vcpus/memory information would be queried from Xen by using lstopo and
xl.

Then using gnuplot we would generate a diagram combining the above
information to generate an integrated view.

Reading number of vcpus, Numa nodes and the quantity of RAM attached
to each NUMA node is available from BIOS or from virtual filesystem
interfaces like sysfs and proc but BIOS makes more sense since in a
virtual enviroment(dom0), some of this information is no longer
accurate.

P.S. - Any feedback or suggestions are welcome.

Regards,
Rita Sinha

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: High Level Design - OPW project "CPU/RAM/PCI diagram tool"
  2014-10-17  3:25 High Level Design - OPW project "CPU/RAM/PCI diagram tool" Rita Sinha
@ 2014-10-29 17:57 ` Dario Faggioli
  0 siblings, 0 replies; 2+ messages in thread
From: Dario Faggioli @ 2014-10-29 17:57 UTC (permalink / raw)
  To: Rita Sinha; +Cc: Andrew Cooper, Xen-devel


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

On Fri, 2014-10-17 at 08:55 +0530, Rita Sinha wrote:
> 
> Reading number of vcpus, Numa nodes and the quantity of RAM attached
> to each NUMA node is available from BIOS or from virtual filesystem
> interfaces like sysfs and proc but BIOS makes more sense since in a
> virtual enviroment(dom0), some of this information is no longer
> accurate.
> 
Indeed they are inaccurate in dom0.

However, what does it mean to read these information from the BIOS? I
mean, what calls/services that can be invoked from within dom0 are we
talking about? How does that differ from asking the same to Xen?

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- 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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-10-29 17:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-17  3:25 High Level Design - OPW project "CPU/RAM/PCI diagram tool" Rita Sinha
2014-10-29 17:57 ` Dario Faggioli

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.