From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 3/5] pseries: Fixes and enhancements to L1 cache properties
Date: Mon, 18 Mar 2013 11:54:05 +0100 [thread overview]
Message-ID: <5146F24D.7090003@suse.de> (raw)
In-Reply-To: <E5F875F4-78CD-4D58-9C09-8AAF8415CC35@suse.de>
Am 15.03.2013 13:27, schrieb Alexander Graf:
>
> On 14.03.2013, at 02:53, David Gibson wrote:
>
>> PAPR requires that the device tree's CPU nodes have several properties
>> with information about the L1 cache. We already create two of these
>> properties, but with incorrect names - "[id]cache-block-size" instead
>> of "[id]-cache-block-size" (note the extra hyphen).
>>
>> We were also missing some of the required cache properties. This
>> patch adds the [id]-cache-line-size properties (which have the same
>> values as the block size properties in all current cases). We also
>> add the [id]-cache-size properties.
>>
>> Adding the cache sizes requires some extra infrastructure in the
>> general target-ppc code to (optionally) set the cache sizes for
>> various CPUs. The CPU family descriptions in translate_init.c can set
>> these sizes - this patch adds correct information for POWER7, I'm
>> leaving other CPU types to people who have a physical example to
>> verify against. In addition, for -cpu host we take the values
>> advertised by the host (if available) and use those to override the
>> information based on PVR.
>>
>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>> ---
>> hw/ppc/spapr.c | 20 ++++++++++++++++++--
>> target-ppc/cpu.h | 1 +
>> target-ppc/kvm.c | 39 +++++++++++++++++++++++++++++++++++++++
>> target-ppc/translate_init.c | 4 ++++
>> 4 files changed, 62 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
>> index 9a13697..7293082 100644
>> --- a/hw/ppc/spapr.c
>> +++ b/hw/ppc/spapr.c
>> @@ -333,10 +333,26 @@ static void *spapr_create_fdt_skel(const char *cpu_model,
>> _FDT((fdt_property_string(fdt, "device_type", "cpu")));
>>
>> _FDT((fdt_property_cell(fdt, "cpu-version", env->spr[SPR_PVR])));
>> - _FDT((fdt_property_cell(fdt, "dcache-block-size",
>> + _FDT((fdt_property_cell(fdt, "d-cache-block-size",
>> env->dcache_line_size)));
>> - _FDT((fdt_property_cell(fdt, "icache-block-size",
>> + _FDT((fdt_property_cell(fdt, "d-cache-line-size",
>> + env->dcache_line_size)));
>> + _FDT((fdt_property_cell(fdt, "i-cache-block-size",
>> + env->icache_line_size)));
>> + _FDT((fdt_property_cell(fdt, "i-cache-line-size",
>> env->icache_line_size)));
>> +
>> + if (env->l1_dcache_size) {
>> + _FDT((fdt_property_cell(fdt, "d-cache-size", env->l1_dcache_size)));
>> + } else {
>> + fprintf(stderr, "Warning: Unknown L1 dcache size for cpu\n");
>> + }
>> + if (env->l1_icache_size) {
>> + _FDT((fdt_property_cell(fdt, "i-cache-size", env->l1_icache_size)));
>> + } else {
>> + fprintf(stderr, "Warning: Unknown L1 icache size for cpu\n");
>> + }
>
> The L1 sizes should come from the class, not env, right? Andreas, any ideas on this?
Generally speaking,
CPUPPCState: Only if this is used for TCG with an offset from AREG0 (or
for legacy grouping reasons).
PowerPCCPU: If you ever intend to let the user override this value
(per-instance) from the command line.
PowerPCCPUClass: If the value is always constant at runtime.
I can't tell from a brief look at this patch which may be the case here.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-03-18 10:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 1:53 [Qemu-devel] [0/5] Assorted pending pseries machine patches David Gibson
2013-03-14 1:53 ` [Qemu-devel] [PATCH 1/5] target-ppc: Synchronize VPA state with KVM David Gibson
2013-03-15 12:22 ` Alexander Graf
2013-04-08 5:01 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2013-03-14 1:53 ` [Qemu-devel] [PATCH 2/5] pseries: Remove "busname" property for PCI host bridge David Gibson
2013-03-15 12:39 ` Alexander Graf
2013-03-14 1:53 ` [Qemu-devel] [PATCH 3/5] pseries: Fixes and enhancements to L1 cache properties David Gibson
2013-03-15 12:27 ` Alexander Graf
2013-03-16 7:10 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2013-03-18 11:10 ` Andreas Färber
2013-03-19 0:52 ` David Gibson
2013-03-18 10:54 ` Andreas Färber [this message]
2013-03-18 11:05 ` [Qemu-devel] " Alexander Graf
2013-03-19 11:06 ` Andreas Färber
2013-03-19 11:09 ` Alexander Graf
2013-03-19 11:16 ` Andreas Färber
2013-03-19 11:37 ` Alexander Graf
2013-03-19 1:00 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2013-03-19 10:10 ` Alexander Graf
2013-03-14 1:53 ` [Qemu-devel] [PATCH 4/5] target-ppc: Remove CONFIG_PSERIES dependency in kvm.c David Gibson
2013-03-15 12:39 ` Alexander Graf
2013-03-14 1:53 ` [Qemu-devel] [PATCH 5/5] pseries: Move XICS initialization before cpu initialization David Gibson
2013-03-15 12:33 ` Alexander Graf
2013-03-16 3:14 ` Benjamin Herrenschmidt
2013-03-16 5:33 ` Alexander Graf
2013-03-16 5:41 ` Benjamin Herrenschmidt
2013-03-16 6:07 ` Alexander Graf
2013-03-18 2:55 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2013-03-18 3:12 ` Alexander Graf
2013-03-18 3:38 ` David Gibson
2013-03-21 10:01 ` Alexander Graf
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=5146F24D.7090003@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 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).