From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Laurent Vivier <laurent@vivier.eu>,
Alistair Francis <alistair.francis@xilinx.com>
Subject: Re: [Qemu-devel] [PATCH] null-machine: Add support for the "-kernel" parameter
Date: Mon, 27 Feb 2017 17:53:37 +0000 [thread overview]
Message-ID: <CAFEAcA_k_7wCaUv8eRNvpNVeh7JExEMx_69De5rVs1Cu9eES+Q@mail.gmail.com> (raw)
In-Reply-To: <76dcc6f2-f888-ad42-eb72-56940b5a7f87@redhat.com>
On 27 February 2017 at 17:49, Thomas Huth <thuth@redhat.com> wrote:
> On 27.02.2017 14:16, Marcel Apfelbaum wrote:
>> Why do we need the "-kernel" parameter for the null-machine? I mean -
>> what are the use cases?
>
> Since it is now possible to instantiate a CPU and memory with the
> null-machine, you can use it as a simple instruction set simulator board
> now. Start QEMU with something like "-M none -cpu xxx -m 1G -S -s" and
> then connect a remote GDB to interact with the emulated CPU. This is
> e.g. useful for CPU models that do not have a matching emulated machine
> yet. Adding the possibility to use the "-kernel" parameter for this,
> too, would make things a little bit more comfortable on certain targets,
> since you then don't have to fiddle with the generic-loader device.
But it still won't do the expected magic -kernel does for you on x86
or ARM or..., so it's just confusing to use the same option. We have
a command line option for "just load the binary please", and that's
the generic-loader. If you think generic-loader's syntax is a bit
tedious you could argue for a convenience option that was syntactic
sugar for it (in the same way that -hda is sugar for -drive and
-device options), but that shouldn't be limited to the null-machine.
thanks
-- PMM
next prev parent reply other threads:[~2017-02-27 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 8:40 [Qemu-devel] [PATCH] null-machine: Add support for the "-kernel" parameter Thomas Huth
2017-01-25 14:42 ` Laurent Vivier
2017-01-25 16:04 ` Thomas Huth
2017-02-27 11:43 ` Thomas Huth
2017-02-27 13:16 ` Marcel Apfelbaum
2017-02-27 17:49 ` Thomas Huth
2017-02-27 17:53 ` Peter Maydell [this message]
2017-02-27 14:00 ` Eduardo Habkost
2017-02-27 17:57 ` Thomas Huth
2017-02-27 18:00 ` Peter Maydell
2017-02-27 18:10 ` Thomas Huth
2017-02-27 19:06 ` Eduardo Habkost
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=CAFEAcA_k_7wCaUv8eRNvpNVeh7JExEMx_69De5rVs1Cu9eES+Q@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@xilinx.com \
--cc=ehabkost@redhat.com \
--cc=jcmvbkbc@gmail.com \
--cc=laurent@vivier.eu \
--cc=marcel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).