All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Liviu Ionescu <ilg@livius.net>
Cc: QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] runtime configurable semihosting
Date: Thu, 13 Nov 2014 12:48:35 -0500	[thread overview]
Message-ID: <5464EEF3.7040700@codeaurora.org> (raw)
In-Reply-To: <E1C4A373-9B89-4CC5-AB4A-BADA8B521904@livius.net>

Hi Liviu,

On 11/12/2014 02:17 PM, Liviu Ionescu wrote:
> 
>> semihosting ... be runtime configurable on this, I think.
> 
> I took a quick look at the syntax of command options and monitor commands, and I would suggest the following:
> 
> - extend the option "-semihosting" with an optional "target=native|gdb|auto", default auto
> 
> - if necessary, add a monitor command "semihosting target=native|gdb|auto", default auto
> 
> any comments?

How do these targets change the existing behavior?

Thanks,
Chris

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2014-11-13 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 19:17 [Qemu-devel] runtime configurable semihosting Liviu Ionescu
2014-11-13  9:44 ` Liviu Ionescu
2014-11-18 13:31   ` Peter Maydell
2014-11-18 16:46     ` Liviu Ionescu
2014-11-18 16:59       ` Peter Maydell
2014-11-13 17:48 ` Christopher Covington [this message]
2014-11-13 17:52   ` Peter Maydell
2014-11-13 21:23     ` Liviu Ionescu
2014-11-13 21:38       ` Liviu Ionescu
2014-11-13 21:38       ` Peter Maydell
2014-11-13 21:51         ` Liviu Ionescu
2014-11-13 22:16           ` Peter Maydell
2014-11-13 22:23             ` Liviu Ionescu
2014-11-13 23:16               ` 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=5464EEF3.7040700@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=Qemu-devel@nongnu.org \
    --cc=ilg@livius.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.