WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [Xen-devel] [PATCH][XEN] __trap_to_gdb should return something diffe

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][XEN] __trap_to_gdb should return something different
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Mon, 25 Sep 2006 09:27:15 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 25 Sep 2006 06:27:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C13B2B13.1A8A%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C13B2B13.1A8A%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On Sep 23, 2006, at 1:18 PM, Keir Fraser wrote:

On 22/9/06 4:07 pm, "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx> wrote:

--text follows this line--

This patch allows the caller to find out if the gdbstub actually did
anything.

Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>

What different actions do you envisage the caller will take? If they are reasonable, perhaps they should be explicitly specified in a return- code
enumeration?

Currently there are two failure cases:
  1) GDB had no transport available for its use (UART or otherwise)
2) "unexpected trap", usually another trap occurs while gdb is in control

I suppose we could have (1) -EIO and (2) -EBUSY.
My logic was that either gdb was available or not and that I needed to continue as if gdb was not enabled at all.

-JX


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel