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,
aik@ozlabs.ru, nacc@linux.vnet.ibm.com, agraf@suse.de,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org, paulus@au1.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 2/2] target-ppc: Implement rtas_get_sysparm(PROCESSOR_MODULE_INFO)
Date: Tue, 1 Dec 2015 11:49:31 -0800 [thread overview]
Message-ID: <20151201194931.GA22634@us.ibm.com> (raw)
In-Reply-To: <20151127064738.GD25500@voom.redhat.com>
David Gibson [david@gibson.dropbear.id.au] wrote:
| > @@ -240,6 +241,36 @@ static void rtas_ibm_get_system_parameter(PowerPCCPU *cpu,
| > target_ulong ret = RTAS_OUT_SUCCESS;
| >
| > switch (parameter) {
| > + case RTAS_SYSPARM_PROCESSOR_MODULE_INFO: {
| > + struct sPAPRRTASModuleInfo modinfo;
| > + int i, size = sizeof(modinfo), offset = 0;
| > +
| > + memset(&modinfo, 0, size);
| > + if (kvmppc_rtas_get_module_info(&modinfo)) {
| > + ret = RTAS_OUT_HW_ERROR;
| > + break;
| > + }
| > +
| > + stw_be_phys(&address_space_memory, buffer+offset, size);
|
| You're still advertising the full structure size to the guest, even
| though it may be only partially populated.
|
| That will probably work in practice, but I think we should be
| PAPRishly correct and only output the size that we actually use here.
Ok. Will have kvmppc_rtas_get_module_info() take/update a size parameter
and use that here.
|
<snip>
| > +/* Each core in the system is represented by a directory with the prefix
| > + * 'PowerPC,POWER' in directory /proc/device-tree/cpus/. Process that
| > + * directory and count the number of cores in the system.
| > + *
| > + * Return 0 if one or more cores are found. Return -1 otherwise.
| > + */
| > +static int kvmppc_count_cores_dt(int *num_cores)
| > +{
| > + int rc;
| > + glob_t dtglob;
| > + const char *cpus_pattern = "/proc/device-tree/cpus/PowerPC,POWER*";
|
| Under KVM PR, this could still be too specific to IBM machines. I
| think it's probably safer to just use /proc/device-tree/cpus/*, I
| don't *think* we get anything under /cpus that isn't a cpu node.
Well, on my Tuleta system (3.18.22-355.el7_1.pkvm3_1_0.3700.3.ppc64le)
I see several l2-cache, l3-cache entries as well as some properties
(like phandle, #size-cells) besides the PowerPC,POWER* entries.
$ cd /proc/device-tree/cpus
$ lsprop l3-cache@30000020/device_type
l3-cache@30000020/device_type
"cache"
$ lsprop l2-cache@200008f0/device_type
l2-cache@200008f0/device_type
"cache"
$ lsprop PowerPC,POWER8@860/device_type
PowerPC,POWER8@860/device_type
"cpu"
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*)?
|
| 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?
Thanks,
Sukadev
next prev parent reply other threads:[~2015-12-01 19:49 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 [this message]
2015-12-02 2:32 ` David Gibson
2015-12-03 1:42 ` [Qemu-devel] [Qemu-ppc] " Sukadev Bhattiprolu
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=20151201194931.GA22634@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--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).