From: Peter Maydell <peter.maydell@linaro.org>
To: Deepak kumar Raju <raju.deepakkumar@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Regarding Cortex-A7 CPU definition
Date: Mon, 8 Feb 2016 15:54:45 +0000 [thread overview]
Message-ID: <CAFEAcA9xjmU_Exep6uTxq_8gq9hffPO5vdMj5kTEL9DTbmjD+Q@mail.gmail.com> (raw)
In-Reply-To: <CACga1gmqTS89gw_RT-A754TQ2z5-Ps1-71-G1qtghAavtTa7rg@mail.gmail.com>
> On Mon, Feb 8, 2016 at 2:21 PM, Deepak kumar Raju <raju.deepakkumar@gmail.com> wrote:
>> I am Deepak. I have a Cortex-A7 board and I am using qemu code from Linaro.
>> In Qemu-linaro.git, under .../target-arm/cpu.c, I do not see CPU definitions for Cortex-A7.
>> I have few questions:
>>
>> a)Can you please point to Cortex-A7 CPU definitions?
We don't implement a Cortex-A7 in QEMU, because we have no board
models that need it.
>> b) Can we use the CPU definitions of Cortex-A15 for Cortex-A7?
Typically guest code doesn't care about the exact CPU type between
the A15 and the A7. If you wanted to add A7 support then starting
with the A15 would be a good start.
>> c) What would be the diff of Cortex-A7 definitions compared to Cortex-A15?
You need to look at the Technical Reference Manual for the two CPUs
to determine the difference. As far as QEMU is concerned the things
to look at are:
* ID register values
* supported CPU features
* any implementation-specific coprocessor registers
...in other words, all the things we set in the
cortex_a15_initfn().
thanks
-- PMM
next prev parent reply other threads:[~2016-02-08 15:55 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 [this message]
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
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=CAFEAcA9xjmU_Exep6uTxq_8gq9hffPO5vdMj5kTEL9DTbmjD+Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=raju.deepakkumar@gmail.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).