From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60037) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xp3d8-000724-2U for Qemu-devel@nongnu.org; Thu, 13 Nov 2014 18:16:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xp3d3-00056Y-M1 for Qemu-devel@nongnu.org; Thu, 13 Nov 2014 18:16:46 -0500 Received: from mail-lb0-f174.google.com ([209.85.217.174]:33062) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xp3d3-00056U-Ek for Qemu-devel@nongnu.org; Thu, 13 Nov 2014 18:16:41 -0500 Received: by mail-lb0-f174.google.com with SMTP id w7so3316000lbi.33 for ; Thu, 13 Nov 2014 15:16:40 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <5464EEF3.7040700@codeaurora.org> <2BE0AD4F-301B-4777-91F2-17200A8BF5B0@livius.net> <852EF052-BF11-46D4-B72E-D8ABB7F787B0@livius.net> From: Peter Maydell Date: Thu, 13 Nov 2014 23:16:20 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] runtime configurable semihosting List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liviu Ionescu Cc: Christopher Covington , QEMU Developers On 13 November 2014 22:23, Liviu Ionescu wrote: > > On 14 Nov 2014, at 00:16, Peter Maydell 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