From: Michael Davidsaver <mdavidsaver@gmail.com>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] armv7-m: add MPU to cortex-m3 and cortex-m4
Date: Sun, 11 Oct 2015 23:51:00 -0400 [thread overview]
Message-ID: <561B2E24.9020600@gmail.com> (raw)
In-Reply-To: <CAPokK=qdfBqCR5nfK4toekX7AVzRHkOLr=4pi5imgavWKN_kRg@mail.gmail.com>
On 10/11/2015 11:23 AM, Peter Crosthwaite wrote:
> On Fri, Oct 9, 2015 at 6:28 AM, Michael Davidsaver
> <mdavidsaver@gmail.com> wrote:
>> The M series MPU is almost the same as the already
>> implemented R series MPU. So use the M series
>> and translate as best we can.
>>
> There is some work on list for this that never got a respin:
>
> https://lists.gnu.org/archive/html/qemu-devel/2015-07/msg01945.html
Well, I totally missed that. I'll have look.
> ...
>> + case 0xd34: /* MMFAR MemManage Fault Address */
>> + return ARM_CPU(current_cpu)->pmsav7_mmfar;
> Why reorder the addresses in the switch?
I was thinking to avoid duplicating the qemu_log_mask() for the
unimplemented registers. I take it that this to you is not the lesser
evil :)
> ... If you run your patch through scripts/checkpatch.pl it will detect
> some of these conventions.
Will do.
> ... More style nits here....
All noted.
> Regards, Peter
Michael
prev parent reply other threads:[~2015-10-12 3:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 13:28 [Qemu-devel] [PATCH 0/3] armv7-m exit, exception fixes and add MPU Michael Davidsaver
2015-10-09 13:28 ` [Qemu-devel] [PATCH 1/3] armv7-m: exit on external reset request Michael Davidsaver
2015-10-09 13:28 ` [Qemu-devel] [PATCH 2/3] armv7-m: fix non-IRQ exceptions Michael Davidsaver
2015-10-11 15:25 ` Peter Crosthwaite
2015-10-11 18:58 ` Michael Davidsaver
2015-10-11 19:00 ` Peter Maydell
2015-10-09 13:28 ` [Qemu-devel] [PATCH 3/3] armv7-m: add MPU to cortex-m3 and cortex-m4 Michael Davidsaver
2015-10-11 15:23 ` Peter Crosthwaite
2015-10-12 3:51 ` Michael Davidsaver [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=561B2E24.9020600@gmail.com \
--to=mdavidsaver@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--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.