From: Peter Maydell <peter.maydell@linaro.org>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Jamie Iles <jamie.iles@picochip.com>,
qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] target-arm: support for ARM1176JZ-s cores
Date: Wed, 22 Jun 2011 17:01:30 +0100 [thread overview]
Message-ID: <BANLkTin-5Cjyr_tYBmg3kr+T9uk4JpoptA@mail.gmail.com> (raw)
In-Reply-To: <20110622154555.GE2704@pulham.picochip.com>
On 22 June 2011 16:45, Jamie Iles <jamie@jamieiles.com> wrote:
> On Wed, Jun 22, 2011 at 10:40:12AM +0100, Peter Maydell wrote:
>> Mostly what I'd like is for the actual code implementing things to
>> be gated on a fairly fine-grained set of flags, so that we can confine
>> the "what does this core have? what things imply what other things?"
>> code to a single place where it's easy to tweak if we get it wrong.
>
> OK, I don't think I can object to that! I'll submit a patch to fix up
> the v7 VMSA ap/remap dependency to be v6K rather than v7. Given that,
> do you have any objection to adding 1167 as a v6K? I'm happy to help
> with/test some of the feature cleanup.
I think the question is, if you mark the 1176 as a v6K then how do
you gate the "working WFI from WFI instruction", which otherwise
could reasonably be marked as one of the features implied by v6K?
-- PMM
next prev parent reply other threads:[~2011-06-22 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:55 [Qemu-devel] [PATCH] target-arm: support for ARM1176JZ-s cores Jamie Iles
2011-06-21 15:43 ` Peter Maydell
2011-06-21 16:13 ` Jamie Iles
2011-06-21 22:13 ` Peter Maydell
2011-06-21 23:42 ` Jamie Iles
2011-06-22 9:40 ` Peter Maydell
2011-06-22 15:45 ` Jamie Iles
2011-06-22 16:01 ` Peter Maydell [this message]
2011-06-22 16:16 ` Jamie Iles
2011-06-22 16:26 ` 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=BANLkTin-5Cjyr_tYBmg3kr+T9uk4JpoptA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=jamie.iles@picochip.com \
--cc=jamie@jamieiles.com \
--cc=paul@codesourcery.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).