qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Andre Przywara <andre.przywara@calxeda.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	aliguori@us.ibm.com, Mitsyanko Igor <i.mitsyanko@samsung.com>,
	qemu-devel@nongnu.org, Rob Herring <rob.herring@calxeda.com>
Subject: Re: [Qemu-devel] [PATCH] highbank: add initial Calxeda Midway A15 support
Date: Sat, 29 Jun 2013 15:25:04 +0200	[thread overview]
Message-ID: <51CEE030.70904@suse.de> (raw)
In-Reply-To: <51CED912.4080905@suse.de>

Am 29.06.2013 14:54, schrieb Andreas Färber:
> Am 28.06.2013 13:59, schrieb Andre Przywara:
>> From: Rob Herring <rob.herring@calxeda.com>
>>
>> While the Calxeda Midway part is actually a bit more than a "Highbank
>> with A15s", for QEMU's purposes this view is sufficient. So to allow
>> both emulation with that chip as well as KVM guests using that model
>> add an A15 CPU and it's peripherals as an option. The use of:
>> "-M highbank -cpu cortex-a15" simply gives the new chip without the
>> need for a new model.
>>
>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>> Signed-off-by: Andre Przywara <andre.przywara@calxeda.com>
>> ---
>>  hw/arm/highbank.c | 19 +++++++++++++------
>>  1 file changed, 13 insertions(+), 6 deletions(-)
>>
>> diff --git a/hw/arm/highbank.c b/hw/arm/highbank.c
>> index 4405dbd..ed864c6 100644
>> --- a/hw/arm/highbank.c
>> +++ b/hw/arm/highbank.c
>> @@ -196,6 +196,7 @@ static void highbank_init(QEMUMachineInitArgs *args)
>>      const char *kernel_filename = args->kernel_filename;
>>      const char *kernel_cmdline = args->kernel_cmdline;
>>      const char *initrd_filename = args->initrd_filename;
>> +    CPUARMState *env = NULL;
>>      DeviceState *dev;
>>      SysBusDevice *busdev;
>>      qemu_irq *irqp;
>> @@ -223,6 +224,8 @@ static void highbank_init(QEMUMachineInitArgs *args)
>>          cpu->reset_cbar = GIC_BASE_ADDR;
>>          irqp = arm_pic_init_cpu(cpu);
>>          cpu_irq[n] = irqp[ARM_PIC_CPU_IRQ];
>> +
>> +        env = &cpu->env;
>>      }
>>  
>>      sysmem = get_system_memory();
>> @@ -246,7 +249,16 @@ static void highbank_init(QEMUMachineInitArgs *args)
>>          }
>>      }
>>  
>> -    dev = qdev_create(NULL, "a9mpcore_priv");
>> +    if (arm_feature(env, ARM_FEATURE_LPAE)) {
>> +        dev = qdev_create(NULL, "a15mpcore_priv");
> 
> This feels a bit fragile to me... Cortex-A7 or other cores might grow
> support for LPAE, too.

Add to that, feature inference is done as part of QOM realize, for which
it is too early to depend on in machine init.

> I would suggest something along these lines:
> 
> if (object_get_class(OBJECT(cpu)) == object_class_by_name("cortex-a15-"
> TYPE_ARM_CPU)) {...}

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-06-29 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28 11:59 [Qemu-devel] [PATCH] highbank: add initial Calxeda Midway A15 support Andre Przywara
2013-06-29 12:54 ` Andreas Färber
2013-06-29 13:25   ` Andreas Färber [this message]
2013-07-04 11:51 ` Peter Maydell

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=51CEE030.70904@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=andre.przywara@calxeda.com \
    --cc=i.mitsyanko@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rob.herring@calxeda.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).