From: Dario Faggioli <dario.faggioli@citrix.com>
To: Rita Sinha <rita.sinha89@gmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: High Level Design - OPW project "CPU/RAM/PCI diagram tool"
Date: Wed, 29 Oct 2014 18:57:59 +0100 [thread overview]
Message-ID: <1414605479.20696.76.camel@Abyss> (raw)
In-Reply-To: <CAMscQT0t1P8TNJFBX0KvGcBnAD43VFQPPC0b-g0S53yoKi9UvA@mail.gmail.com>
[-- 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
prev parent reply other threads:[~2014-10-29 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=1414605479.20696.76.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=rita.sinha89@gmail.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.