From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Arm MMU Fixes
Date: Wed, 31 Oct 2007 01:49:37 +0100 [thread overview]
Message-ID: <fb249edb0710301749k5b95bc5cs322b93bcf78838ea@mail.gmail.com> (raw)
In-Reply-To: <2BB0007D-1679-435D-BBE4-201598484A05@ok-labs.com>
Hi,
On 15/10/2007, Matthew Warton <mwarton@ok-labs.com> wrote:
> The first is that Qemu would not enable changing of the pid register
> on processors with an MMU. This is a legal operation, and one that
> several parts of our kernel rely on. See (for example) the ARM920t
> technical reference manual to verify that this register is available
> on ARM processors with an MMU.
I committed the change, but I'm wondering if it was originally a typo
and the operation should instead be illegal on processors with an MPU
(note that MPU != MMU), i.e. a spurious "!". Can somebody check this?
Thanks,
Andrew
next prev parent reply other threads:[~2007-10-31 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 1:53 [Qemu-devel] [PATCH] Arm MMU Fixes Matthew Warton
2007-10-31 0:49 ` andrzej zaborowski [this message]
2007-11-01 3:03 ` Matthew Warton
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=fb249edb0710301749k5b95bc5cs322b93bcf78838ea@mail.gmail.com \
--to=balrogg@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 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).