From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Disable interrupts on Cortex M3 (lm3s6965evb)
Date: Sun, 05 Jun 2011 18:32:12 +0200 [thread overview]
Message-ID: <4DEBAF8C.2090502@embedded-brains.de> (raw)
In-Reply-To: <BANLkTinLg__spSTPaX3G6Ts3HFSO6oV=gA@mail.gmail.com>
On 05/06/11 16:57, Peter Maydell wrote:
> On 5 June 2011 15:17, Sebastian Huber
> <sebastian.huber@embedded-brains.de> wrote:
>
>> On 05/06/11 15:44, Peter Maydell wrote:
[...]
>>> (It looks suspiciously as if most of the v7M priority handling
>>> is simply missing from QEMU, ie you have bigger problems than
>>> can be fixed by a small patch like this...)
>>>
>
>> Yes, but the current behaviour is definitely not right. Since the
>> PRIMASK is mapped to the I bit in the CPSR I guessed that this was the
>> right place to fix it.
>>
> I agree that the current behaviour is not right. However, to fix
> this problem you need to work on a larger scale than attempting
> to apply two line patches which fix your particular use case.
>
I agree, but you have to start somewhere. What is "this problem"? Is
that we have no execution priority (in the sense of the ARMv7
architecture, B1.3.2 Exceptions), but instead use a mapping to CPSR_I
and CPSR_F?
next prev parent reply other threads:[~2011-06-05 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 10:31 [Qemu-devel] Disable interrupts on Cortex M3 (lm3s6965evb) Sebastian Huber
2011-06-05 13:06 ` Sebastian Huber
2011-06-05 13:44 ` Peter Maydell
2011-06-05 14:17 ` Sebastian Huber
2011-06-05 14:57 ` Peter Maydell
2011-06-05 16:32 ` Sebastian Huber [this message]
2011-06-05 19:23 ` 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=4DEBAF8C.2090502@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=paul@codesourcery.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).