qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: stewart@linux.vnet.ibm.com, thuth@redhat.com, benh@au1.ibm.com,
	nacc@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	qemu-ppc@nongnu.org, paulus@au1.ibm.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v3 2/2] target-ppc: Implement rtas_get_sysparm(PROCESSOR_MODULE_INFO)
Date: Wed, 2 Dec 2015 17:42:44 -0800	[thread overview]
Message-ID: <20151203014244.GA16046@us.ibm.com> (raw)
In-Reply-To: <20151202023257.GB3107@voom.redhat.com>

David Gibson [david@gibson.dropbear.id.au] wrote:
| > Should we walk the /proc/device-tree/cpus/ tree and count only dirs with
| > device-type "cpu" (rather than relying on the pattern PowerPC,POWER*)?
| 
| Yes, I think you'll have to.
| 
Ok. Are we ok with the xscom check I have (copied below):

+static int kvmppc_count_sockets_chips_dt(int *num_sockets, int *num_chips)
+{
+    const char *chip_pattern = "/proc/device-tree/xscom@*/ibm,chip-id";
+    const char *module_pattern = "/proc/device-tree/xscom@*/ibm,hw-module-id";

---

I am not sure of a reliable way to detect number of chips besides the
xscom. I do see that sysfs has node entries:

	for i in `ls -d /sys/bus/cpu/devices/cpu*`; 
	> do
	> basename $i/node*
	> done | sort | uniq
	node0
	node1
	node16
	node17

which seems to correspond to

	$ lsprop /proc/device-tree/xscom@*/ibm,chip-id
	/proc/device-tree/xscom@3fc0000000000/ibm,chip-id
			 00000000
	/proc/device-tree/xscom@3fc0800000000/ibm,chip-id
			 00000001
	/proc/device-tree/xscom@3fc8000000000/ibm,chip-id
			 00000010 (16)
	/proc/device-tree/xscom@3fc8800000000/ibm,chip-id
			 00000011 (17)

but is that reliable?
> +
| > | 
| > | In a number of ways I'd actually prefer to move to /cpus/cpu@NNN in
| > | general, since that follows the OF generic names recommendation we
| > | follow for most other nodes.
| > 
| > Do you mean rename '/proc/device-tree/cpus/PowerPC,POWER8@NNN' to
| > /proc/device-tree/cpus/cpu@NNN?
| 
| Yes.  This is a firmware matter, so it's not something that can simply
| be changed everywhere, but it's the approach that I'd prefer to
| encourage for people making future machines and firmwares.

Sure. ppc64_cpu also seems to rely on '/proc/device-tree/cpus/PowerPC'
to count cores present and maybe there are other utilities that would
need to be updated.

Sukadev

  reply	other threads:[~2015-12-03  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14  2:13 [Qemu-devel] [PATCH v3 1/2] target-ppc: Define kvmppc_read_int_dt() Sukadev Bhattiprolu
2015-11-14  2:13 ` [Qemu-devel] [PATCH v3 2/2] target-ppc: Implement rtas_get_sysparm(PROCESSOR_MODULE_INFO) Sukadev Bhattiprolu
2015-11-25  6:30   ` [Qemu-devel] [Qemu-ppc] " Sukadev Bhattiprolu
2015-11-27  6:47     ` David Gibson
2015-11-27  6:47   ` [Qemu-devel] " David Gibson
2015-12-01 19:49     ` Sukadev Bhattiprolu
2015-12-02  2:32       ` David Gibson
2015-12-03  1:42         ` Sukadev Bhattiprolu [this message]
2015-11-16  7:41 ` [Qemu-devel] [PATCH v3 1/2] target-ppc: Define kvmppc_read_int_dt() David Gibson

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=20151203014244.GA16046@us.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=benh@au1.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=nacc@linux.vnet.ibm.com \
    --cc=paulus@au1.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=thuth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).