qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Liviu Ionescu <ilg@livius.net>
Cc: Christopher Covington <cov@codeaurora.org>,
	QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] runtime configurable semihosting
Date: Thu, 13 Nov 2014 22:16:22 +0000	[thread overview]
Message-ID: <CAFEAcA8tfZoSr=ccu-VLdb0w48O-nGENoq+tLJ-_YYvDV4GTYg@mail.gmail.com> (raw)
In-Reply-To: <852EF052-BF11-46D4-B72E-D8ABB7F787B0@livius.net>

On 13 November 2014 21:51, Liviu Ionescu <ilg@livius.net> wrote:
>
> On 13 Nov 2014, at 23:38, Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> On 13 November 2014 21:23, Liviu Ionescu <ilg@livius.net> wrote:
>
>> ...I'm confused, I think. I thought 'gdb' was an option you added?
>
> that's correct, but only part of the whole image, in fact I added "-semihosting-target auto|native|gdb"; however my patch only changes the destination of the semihosting calls, not the actual behaviour.
>
>> Can you explain what the three options you're proposing do, and
>> which of them is the behaviour we have today?
>
> the behaviour is exactly the one you presented, 'auto' is the actual
> behaviour, 'native' is via qemu, 'gdb' is via... gbd. :-)

Right, but what does it mean to say 'gdb' that's different from
'auto' ? What happens in that case if you don't have a gdb
attached?

> p.s. I'm a bit puzzled by your patch submission procedure
> (the Eclipse CDT team uses Gerrit, and things are more or
> less automated), manually preparing patches and sending them
> to a mailing list seems quite tedious...

I use a flow like:
 git format-patch -o ~/my-sent-patches HEAD^
 # check that the ~/my-sent-patches/0001-whatever.patch looks ok
 git send-email --to=qemu-devel@nongnu.org ~/my-sent-patches/0001-whatever.patch

but that does require you to have set up git send-email
so it knows how to send emails.
(You can probably do it in one command but I happen to have
my main dev machine and the machine I send email from being
different, so I copy the patchfiles around in the middle.)

-- PMM

  reply	other threads:[~2014-11-13 22:16 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
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 [this message]
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='CAFEAcA8tfZoSr=ccu-VLdb0w48O-nGENoq+tLJ-_YYvDV4GTYg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=Qemu-devel@nongnu.org \
    --cc=cov@codeaurora.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 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).