From: Meador Inge <meadori@codesourcery.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] target-arm: Add "anyvfp" CPU
Date: Mon, 13 Jul 2015 13:21:00 -0700 [thread overview]
Message-ID: <20150713202059.GB24071@mentor.com> (raw)
In-Reply-To: <CAEgOgz5CSXmyc6GEbArFvGB-imUHzQ8QnZW3ooizPaGaPtXCRg@mail.gmail.com>
On Mon, Jul 06, 2015 at 03:00:20PM -0700, Peter Crosthwaite wrote:
> So a better way to do this is via QOM properties. You can propertyify
> VFP support on the QOM type ARMCPU then users can use -global to set
> in on the command line. You could do this for any number of ARM CPU
> features you care about to create the combos you want on the command
> line rather than having an in tree CPU def for special cases.
>
> Have a look at the way the has_el3 feature is handled as a CPU property.
I will look into that. Thank you.
> Do you have originals in a git with the author SOBs that you can just
> amend with your own editor notes?
Unfortunately for this case, no. This is a very hold patch that was
originally in an SVN mirror.
-- Meador
next prev parent reply other threads:[~2015-07-13 20:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 18:53 [Qemu-devel] [PATCH 0/2] target-arm: "any" CPUs for system-mode meadori
2015-07-06 18:53 ` [Qemu-devel] [PATCH 1/2] target-arm: Allow CPU "any" for system-mode emulation meadori
2015-07-06 21:51 ` Peter Crosthwaite
2015-07-06 18:53 ` [Qemu-devel] [PATCH 2/2] target-arm: Add "anyvfp" CPU meadori
2015-07-06 22:00 ` Peter Crosthwaite
2015-07-13 20:21 ` Meador Inge [this message]
2015-07-13 21:32 ` Peter Crosthwaite
2015-07-06 22:31 ` Peter Maydell
2015-07-13 20:36 ` Meador Inge
2015-07-06 22:29 ` [Qemu-devel] [PATCH 0/2] target-arm: "any" CPUs for system-mode Peter Maydell
2015-07-06 22:42 ` Peter Crosthwaite
2015-07-06 22:49 ` Peter Maydell
2015-07-06 23:05 ` Peter Crosthwaite
2015-07-13 20:34 ` Meador Inge
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=20150713202059.GB24071@mentor.com \
--to=meadori@codesourcery.com \
--cc=peter.crosthwaite@xilinx.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).