From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-16481-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 11476 invoked by alias); 4 Dec 2003 21:05:50 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 11451 invoked from network); 4 Dec 2003 21:05:49 -0000
Received: from unknown (HELO mail.pune.nevisnetworks.com) (203.124.166.107)
  by sources.redhat.com with SMTP; 4 Dec 2003 21:05:49 -0000
Received: from nevis_pune_xchg.pune.nevisnetworks.com (nevis_pune_xchg.pune.nevisnetworks.com [192.168.2.7])
	by mail.pune.nevisnetworks.com (8.12.5/8.12.5) with ESMTP id hB4LIkpX018680
	for <gdb@sources.redhat.com>; Fri, 5 Dec 2003 02:48:47 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: GDB for Multiprocessor Architecture
Date: Thu, 04 Dec 2003 21:05:00 -0000
Message-ID: <36993D449C7FA647BF43568E0793AB3E32A603@nevis_pune_xchg.pune.nevisnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Nitin Gupta" <nitin.gupta@nevisnetworks.com>
To: "Andrew Cagney" <cagney@gnu.org>
Cc: "Daniel Jacobowitz" <drow@mvista.com>,
   "Ian Lance Taylor" <ian@wasabisystems.com>, <gdb@sources.redhat.com>
X-SW-Source: 2003-12/txt/msg00088.txt.bz2


> CPU's can be modeled using GDB's thread framework.  However,=20
> at present=20
> the model doesn't extend as far as modeling separate memory=20
> regions for=20
> each CPU (something that needs to be fixed).
>=20
I need this feature for my model and I am ready to enhance this feature
in GDB.
However, I have some queries. GDB remote protocol does not have a field
that can tell me about the processor (thread) id. This means that can I
on-the-fly switch from one thread to another? I feel this has to be
incorporated in the protocol. Hence it will be comething like every
message actually coming with the processor id attached with it.
I plan to extend the GDB remote protocol and make changes in remote.c
file. Roghly how big this enhancemet will be?
Has anybody done work on this earlier? Where can I find some more
documents on the remote protocol. The code obviously is the best doc.

Nitin Gupta