All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabien Chouteau <chouteau@adacore.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Cortex-M4F Floating Point system registers
Date: Wed, 20 Mar 2013 18:26:27 +0100	[thread overview]
Message-ID: <5149F143.9000506@adacore.com> (raw)
In-Reply-To: <CAFEAcA80ym3NnrZOB5ziGq=L-+BOkM1ix39oQvBPYG7GQhhOew@mail.gmail.com>

On 03/20/2013 05:43 PM, Peter Maydell wrote:
> On 20 March 2013 16:05, Fabien Chouteau <chouteau@adacore.com> wrote:
>> I'm looking at the ARMv7-M profile and the implementation in QEMU.
>> Looks like M3 is supported and I'd like to work on M4F (FP context save
>> and lazy FP context save).
>
> This is going to be interesting because we don't currently have
> any mechanisms implemented for 'trap on attempt to use FP insn'.
> (Not impossible, just the code isn't there at the moment.)
>

OK, if you can give me any insight of what needs to be done for M4F and
how should I do it, don't hesitate.

>> I wonder how the FPU system registers, and more generally how the
>> co-processor registers are implemented in QEMU.
>>
>> For example in the Cortex-M4 TRM it seems like FP system registers are
>> mapped in memory. I don't see that implemented in QEMU.
>
> Yes, M profile maps lots of sysregs in memory. Mostly we implement
> these in hw/armv7m_nvic.c. It's kind of ugly the way that code
> reaches into the CPU implementation though.
>

Thanks, I'll take a look at this.

-- 
Fabien Chouteau

      reply	other threads:[~2013-03-20 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 16:05 [Qemu-devel] Cortex-M4F Floating Point system registers Fabien Chouteau
2013-03-20 16:43 ` Peter Maydell
2013-03-20 17:26   ` Fabien Chouteau [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=5149F143.9000506@adacore.com \
    --to=chouteau@adacore.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.