qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Deepak kumar Raju <raju.deepakkumar@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Regarding Cortex-A7 CPU definition
Date: Wed, 24 Feb 2016 19:20:28 +0530	[thread overview]
Message-ID: <CACga1g=1Jk4dDLF=uEHv9mUdfXYD0-QvwqW0DN9zhVEv+zkBsA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-UhDUXhj1gZbZo3s1rLThM17WrniwGJMShJ_E6icfuzQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

Hi Peter,

We are emulating the A7 hardware board in QEMU. Currently I have started
with A15 CPU config. I need to enable GIC and generic timer. Can you please
point me to how GIC & generic timer should be enabled considering
vexpress.c emulation board?.
Thanks in advance for the help,

Best Regards,
-Deepak

On Wed, Feb 10, 2016 at 3:43 PM, Peter Maydell <peter.maydell@linaro.org>
wrote:

> On 10 February 2016 at 05:25, Deepak kumar Raju
> <raju.deepakkumar@gmail.com> wrote:
> > Regarding the questions, we have hw board which has Cortex-A7, so we
> thought
> > we have to go with A7 emulation. we were not very sure A15 emulation
> will be
> > almost equivalent to A7 emulation.
> > All we want to do is A7 emulation but now I am understanding that A15
> > emulation should similar to A7 emulation. please correct me.
>
> If you want to emulate the whole hardware board in QEMU,
> then adding the A7 CPU emulation is the right thing (and
> not very hard compared to doing the whole hardware model).
> If you don't care about emulating the hardware because you're
> going to run (say) a Linux kernel on one of QEMU's existing
> models and you mostly care about userspace, then using the
> A15 will be fine -- the two CPUs are basically identical
> for that purpose, and Linux supports both.
>
> If you're running QEMU to use KVM on the ARM hardware,
> then you want "-cpu host", which means "use the best CPU
> type that the kernel can provide" and works on A7 and A15
> hosts.
>
> thanks
> -- PMM
>

[-- Attachment #2: Type: text/html, Size: 2078 bytes --]

  reply	other threads:[~2016-02-24 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACga1gnbjqsoRkJCSDQnd_=fgvmjS_05ViYN_kK2soAynP2Kgw@mail.gmail.com>
2016-02-08  9:31 ` [Qemu-devel] Regarding Cortex-A7 CPU definition Deepak kumar Raju
2016-02-08 15:54   ` Peter Maydell
2016-02-09  7:43     ` Deepak kumar Raju
2016-02-09  9:31       ` Peter Maydell
2016-02-09 18:08         ` Deepak kumar Raju
2016-02-09 18:12           ` Peter Maydell
2016-02-10  5:25             ` Deepak kumar Raju
2016-02-10 10:13               ` Peter Maydell
2016-02-24 13:50                 ` Deepak kumar Raju [this message]
2016-02-26  6:48                   ` Deepak kumar Raju
2016-02-26 10:21                     ` 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='CACga1g=1Jk4dDLF=uEHv9mUdfXYD0-QvwqW0DN9zhVEv+zkBsA@mail.gmail.com' \
    --to=raju.deepakkumar@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).