qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] hw/arm: add Fixed Virtual Platform VE support
Date: Wed, 25 Mar 2015 10:52:42 -0700	[thread overview]
Message-ID: <5512F5EA.4090407@gmail.com> (raw)
In-Reply-To: <CAFEAcA83sUss4U_YGq8FyJHvs3Yo1Pj9mrgkzZ6KchJQDFFBiA@mail.gmail.com>



On 25.03.2015 04:06, Peter Maydell wrote:
> On 25 March 2015 at 01:43, Sergey Fedorov <serge.fdrv@gmail.com> wrote:
>> On 24.03.2015 18:30, Sergey Fedorov wrote:
>>> So if I understand you correctly, it would be suitable to implement a
>>> model like Juno ARM Development Platform in order to get AArch64 VE
>>> model with SMP support in system mode?
>> As you can guess, my objective is to get a model based on Versatile
>> Express with Cortex-A57 CPU which could be used to run an SMP Linux
>> kernel on system mode QEMU. So I decided to use the same model as ARM
>> FastModels provides. I could get ARMv8-A Foundation Platform model as
>> well, but it also uses spin table boot method. Seems there's no much choice.
> Basically I'd rather we modelled some bit of real hardware.
> I don't see the point in providing a model of somebody
> else's model -- if you don't care about matching real
> hardware we have 'virt' already. So I don't really want
> to model either the Foundation Platform or the AEM,
> unless there's a really compelling reason to do that.
>
> thanks
> -- PMM

I understand your view. Unfortunately, I'm not going to implement any
other model so far. I'd rather focus on EL2 implementation for AArch64.
But maybe someone will find useful these patches :)

Thanks,
Sergey

      reply	other threads:[~2015-03-25 17:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 23:55 [Qemu-devel] [PATCH 0/3] hw/arm: add Fixed Virtual Platform VE support Sergey Fedorov
2015-03-24 23:55 ` [Qemu-devel] [PATCH 1/3] hw/arm/boot: add secondary loader for AArch64 Sergey Fedorov
2015-03-24 23:55 ` [Qemu-devel] [PATCH 2/3] hw/arm/vexpress: introduce VEDBoardInfo::smp_bootreg_addr Sergey Fedorov
2015-03-24 23:55 ` [Qemu-devel] [PATCH 3/3] hw/arm/vexpress: add FVP VE board support Sergey Fedorov
2015-03-25  0:13 ` [Qemu-devel] [PATCH 0/3] hw/arm: add Fixed Virtual Platform VE support Peter Maydell
2015-03-25  0:18   ` Sergey Fedorov
2015-03-25  0:23     ` Peter Maydell
2015-03-25  0:31       ` Sergey Fedorov
2015-03-25  0:48         ` Peter Maydell
2015-03-25  1:30           ` Sergey Fedorov
2015-03-25  1:43             ` Sergey Fedorov
2015-03-25 11:06               ` Peter Maydell
2015-03-25 17:52                 ` Sergey Fedorov [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=5512F5EA.4090407@gmail.com \
    --to=serge.fdrv@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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).