From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48715)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1XoyZN-0002jQ-Pd
	for Qemu-devel@nongnu.org; Thu, 13 Nov 2014 12:52:38 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1XoyZI-0005hd-IR
	for Qemu-devel@nongnu.org; Thu, 13 Nov 2014 12:52:33 -0500
Received: from mail-la0-f47.google.com ([209.85.215.47]:48007)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <peter.maydell@linaro.org>) id 1XoyZI-0005hO-Ai
	for Qemu-devel@nongnu.org; Thu, 13 Nov 2014 12:52:28 -0500
Received: by mail-la0-f47.google.com with SMTP id gd6so13375151lab.20
	for <Qemu-devel@nongnu.org>; Thu, 13 Nov 2014 09:52:26 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <5464EEF3.7040700@codeaurora.org>
References: <E1C4A373-9B89-4CC5-AB4A-BADA8B521904@livius.net>
	<5464EEF3.7040700@codeaurora.org>
From: Peter Maydell <peter.maydell@linaro.org>
Date: Thu, 13 Nov 2014 17:52:06 +0000
Message-ID: <CAFEAcA-dPHhJ-xJMJSu7DkUeZDyXVh4GT6HCfoJjkOYTZN2kPw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] runtime configurable semihosting
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Christopher Covington <cov@codeaurora.org>
Cc: Liviu Ionescu <ilg@livius.net>, QEMU Developers <Qemu-devel@nongnu.org>

On 13 November 2014 17:48, Christopher Covington <cov@codeaurora.org> wrote:
> 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?

Our current behaviour is "auto", which means "send semihosting
commands via gdb if and only if the gdbstub has a gdb connected
when the first semihosting command is made by the guest". "native"
would mean "handle semihosting ourselves even if there's a gdb
connected". I'm not sure how useful "gdb" is as distinct from
"auto" (what do you do with the semihosting requests if no
gdb is connected in this case?).

-- PMM