qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Christopher Covington <christopher.covington@linaro.org>
Subject: Re: [Qemu-devel] arm: semihosting: Preliminary AArch64 support
Date: Mon, 30 Mar 2015 12:44:34 +0100	[thread overview]
Message-ID: <55193722.3060909@imgtec.com> (raw)
In-Reply-To: <EB0286DC-3719-4499-BB07-D142155971F9@livius.net>

On 27/03/2015 17:33, Liviu Ionescu wrote:
> 
>> On 27 Mar 2015, at 19:15, Leon Alrae <leon.alrae@imgtec.com> wrote:
>>
>> ... introducing separate "-semihosting-arg" option to pass input arguments
> 
> if we'll ever go for this solution, I would call it "-semihosting-cmdline", since it should include the entire command line, starting with argv[0].
> 
>> ... but basically it makes the life easier.
> 
> this was my opinion too, and my first patches implemented this solution.
> 
>> On 27 Mar 2015, at 19:21, Peter Maydell <peter.maydell@linaro.org> wrote:
>> ... The
>> problem with extra ad-hoc top level command line arguments
>> is that they don't fit in with the structure we're trying
>> to impose on new QEMU options, which is that they should
>> have a particular syntax and sit inside option groups
>> (in this case, -semihosting-config).
> 
> this is also true, and, although a bit more complicated to use, I implemented this solution.

Avoiding top level ad-hoc arguments sounds reasonable. Unfortunately the
QEMU parser doesn't seem to support the same sub-argument used multiple
times (always the last value is used):
-semihosting-config arg="argument 1",arg="argument 2",arg="argument 3"
I may look into it to see how much is missing to make it work.

The reason I chose "arg" is because it naturally translates into argv[]
for the guest program. As far as "cmdline" option goes -- wouldn't "arg"
be more flexible so that you could use it to assemble cmdline?

Leon

  reply	other threads:[~2015-03-30 11:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 16:22 [Qemu-devel] arm: semihosting: Preliminary AArch64 support Christopher Covington
2015-03-27 16:22 ` [Qemu-devel] [PATCH 1/3] arm: semihosting: Improve debug prints Christopher Covington
2015-03-27 16:25   ` Peter Maydell
2015-03-27 16:22 ` [Qemu-devel] [PATCH 2/3] arm: semihosting: Create unsupported call function Christopher Covington
2015-03-27 16:41   ` Peter Maydell
2015-03-27 16:22 ` [Qemu-devel] [PATCH 3/3] arm: semihosting: Wire up A64 HLT 0xf000 Christopher Covington
2015-03-27 16:40   ` Peter Maydell
2015-03-28 12:27     ` Christopher Covington
2015-03-31 11:22       ` Peter Maydell
2015-03-27 16:57 ` [Qemu-devel] arm: semihosting: Preliminary AArch64 support Liviu Ionescu
2015-03-27 17:05   ` Peter Maydell
2015-03-27 17:15     ` Leon Alrae
2015-03-27 17:21       ` Peter Maydell
2015-03-27 17:33       ` Liviu Ionescu
2015-03-30 11:44         ` Leon Alrae [this message]
2015-03-30 12:27           ` Liviu Ionescu

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=55193722.3060909@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=christopher.covington@linaro.org \
    --cc=ilg@livius.net \
    --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).