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 23:16:20 +0000 [thread overview]
Message-ID: <CAFEAcA8ZPfgwHSw6FqA6xF-DvfJozWsJZO72w-8cqApAohLnmA@mail.gmail.com> (raw)
In-Reply-To: <E7D7E6F6-980F-49A2-A36F-0B320211A7C8@livius.net>
On 13 November 2014 22:23, Liviu Ionescu <ilg@livius.net> wrote:
>
> On 14 Nov 2014, at 00:16, Peter Maydell <peter.maydell@linaro.org> wrote:
>
>> Right, but what does it mean to say 'gdb' that's different from
>> 'auto' ?
>
> auto sends either to gdb or qemu, gdb always sends to gdb, native always to qemu.
>
>> What happens in that case if you don't have a gdb
>> attached?
>
> according to my tests, nothing.
Oh, I see now. gdb_do_syscall() will return doing nothing if
gdbserver_state is NULL (so "gdb" will throw away semihosting
requests until a gdb is eventually connected, at which point
we start to honour them). Yes, that makes sense as a behaviour
(though 'auto' and 'native' are going to be the major uses).
>> I use a flow like: ...
>
> thank you, I'm trying to figure out the details (Signed-off-by,
> cover letter, etc)
The Signed-off-by is just a matter of putting that line in your
commit message. It's pretty much the only thing we absolutely
have to insist on, since it's a statement that you're happy
for the code to go in and have the legal right to contribute it.
Most other things we can fix up formatting details if needed.
You don't need a cover letter unless you're submitting a series
with more than one patch in it.
-- PMM
prev parent reply other threads:[~2014-11-13 23: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
2014-11-13 22:23 ` Liviu Ionescu
2014-11-13 23:16 ` Peter Maydell [this message]
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=CAFEAcA8ZPfgwHSw6FqA6xF-DvfJozWsJZO72w-8cqApAohLnmA@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).