From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Julian Brown <julian@codesourcery.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 1/6] Add cfgend parameter for ARM CPU selection.
Date: Wed, 18 Jan 2017 14:52:56 -0200 [thread overview]
Message-ID: <20170118165256.GC6657@thinpad.lan.raisama.net> (raw)
In-Reply-To: <CAFEAcA8eYeLNrTK-hupM9jA7CPjD8OgEU85As94fWXQETxRgXA@mail.gmail.com>
On Tue, Jan 17, 2017 at 11:52:24AM +0000, Peter Maydell wrote:
> On 12 January 2017 at 14:28, Julian Brown <julian@codesourcery.com> wrote:
> > On Wed, 11 Jan 2017 12:35:52 +0000
> > Julian Brown <julian@codesourcery.com> wrote:
> >
> >> I'm a little confused, I think -- these changes seemed to be necessary
> >> to allow the parsing of the command-line syntax you suggested earlier
> >> (-mcpu=foo,cfgend=bar):
> >> [...]
> >> Can the existing properties be set like that via the command line?
> >
> > Aha! The answer was yes, but only currently for the "virt" board
> > (which we haven't been using for aarch32, and only supports a few recent
> > CPU types at present). I'm less confused now! (The string-splitting code
> > in arm_cpu_class_by_name is still dubious though, IMO.)
>
> Oops, I'd forgotten there was board-specific code for handling
> cpu feature flags. I think we want to change the other boards
> to do it like the virt board does, but maybe I'm wrong.
> I've cc'd Eduardo who will hopefully know the right way to handle
> this.
I don't understand what's missing here: cpu_arm_init() already
calls cpu_generic_init(), which already calls
CPUClass::parse_features() after splitting the cpu_model string
and calling CPUClass::class_by_name().
Which board aree you using to test this? Is the board calling
cpu_arm_init() to create the CPU?
--
Eduardo
next prev parent reply other threads:[~2017-01-18 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 14:48 [Qemu-devel] [PATCH v2 0/6] ARM BE8/BE32 big-endian system-mode fixes (semihosting, gdbstub) Julian Brown
2016-12-07 14:48 ` [Qemu-devel] [PATCH v2 1/6] Add cfgend parameter for ARM CPU selection Julian Brown
2017-01-05 17:17 ` Peter Maydell
2017-01-11 12:35 ` Julian Brown
2017-01-12 14:28 ` Julian Brown
2017-01-17 11:52 ` Peter Maydell
2017-01-18 16:52 ` Eduardo Habkost [this message]
2017-01-19 15:12 ` Peter Maydell
2017-01-19 18:02 ` Julian Brown
2017-01-19 18:25 ` Peter Maydell
2016-12-07 14:48 ` [Qemu-devel] [PATCH v2 2/6] Infer endianness from SCTLR reset value Julian Brown
2017-01-05 17:29 ` Peter Maydell
2016-12-07 14:48 ` [Qemu-devel] [PATCH v2 3/6] ARM big-endian system-mode semihosting support Julian Brown
2017-01-05 17:49 ` Peter Maydell
2016-12-07 14:49 ` [Qemu-devel] [PATCH v2 4/6] ARM big-endian system-mode gdbstub support Julian Brown
2017-01-05 17:53 ` Peter Maydell
2016-12-07 14:49 ` [Qemu-devel] [PATCH v2 5/6] Fix Thumb-1 BE32 execution and disassembly Julian Brown
2017-01-05 18:18 ` Peter Maydell
2016-12-07 14:49 ` [Qemu-devel] [PATCH v2 6/6] ARM BE32 watchpoint fix Julian Brown
2017-01-05 18:25 ` Peter Maydell
2016-12-07 15:09 ` [Qemu-devel] [PATCH v2 0/6] ARM BE8/BE32 big-endian system-mode fixes (semihosting, gdbstub) no-reply
2016-12-07 15:28 ` no-reply
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=20170118165256.GC6657@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=julian@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).