From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5892 invoked by alias); 25 Dec 2008 18:45:59 -0000 Received: (qmail 5879 invoked by uid 22791); 25 Dec 2008 18:45:56 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_50,J_CHICKENPOX_36,KAM_MX,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 25 Dec 2008 18:45:09 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id mBPIj7Q7003868 for ; Thu, 25 Dec 2008 13:45:07 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id mBPIj7Uv014320 for ; Thu, 25 Dec 2008 13:45:07 -0500 Received: from ton.toronto.redhat.com (ton.yyz.redhat.com [10.15.16.15]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id mBPIj6L9000849; Thu, 25 Dec 2008 13:45:07 -0500 Received: from ton.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by ton.toronto.redhat.com (8.13.1/8.13.1) with ESMTP id mBPIj60L013036; Thu, 25 Dec 2008 13:45:06 -0500 Received: (from fche@localhost) by ton.toronto.redhat.com (8.13.1/8.13.1/Submit) id mBPIj6Vl013035; Thu, 25 Dec 2008 13:45:06 -0500 Date: Thu, 25 Dec 2008 18:45:00 -0000 From: "Frank Ch. Eigler" To: Shamik Datta Cc: sid@sources.redhat.com Subject: Re: Error Building SID.. Message-ID: <20081225184505.GF4195@redhat.com> References: <239b036a0812111328r2ed15cc6le385c17a20a19dc@mail.gmail.com> <20081211234936.GA1200@redhat.com> <239b036a0812121037p534a4ca1t759ea754c7ebad62@mail.gmail.com> <20081212195729.GB1200@redhat.com> <239b036a0812130700v2ba9e054yb63be621c223b769@mail.gmail.com> <239b036a0812150100h1330ba92nb89c0597268a8c01@mail.gmail.com> <20081215175754.GA7910@redhat.com> <239b036a0812151202y5ed2a0a4y486ce4905503de67@mail.gmail.com> <20081215203852.GB7910@redhat.com> <239b036a0812211557h2d73685pf3ccd01a5ac3d6da@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <239b036a0812211557h2d73685pf3ccd01a5ac3d6da@mail.gmail.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Mailing-List: contact sid-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sourceware.org X-SW-Source: 2008-q4/txt/msg00015.txt.bz2 Hi - On Mon, Dec 22, 2008 at 05:27:53AM +0530, Shamik Datta wrote: > [...] > What SID essentially provides is the low level API for the components > to talk to each other, the pin, the bus and the attribute interface. > The config file inter-connects all the components through their these > interfaces. During the simulation instances are created, at any > activity on these interfaces, the appropriate function is called, eg, > pin.driven. I presume for these set of APIs the calling bridge is > setup in tcl, or something like that?, which enables writing > components in tcl directly. hopefully more or less correct till now. Right. > I see for all the components there are class definitions and > implementations. Again what SID provides here is the set of .h files > in the ./sid/include directory which implement some basic and some > utility functions, for these aforementioned interfaces. The rest of > the design is completely open. SID provides no infrastructure or asks > for any protocol here. It is left to the designer to define his > classes (modules) and functions (interfaces), so as to mimic the > actual hardware. Right. > So, for 'bochs' which was an existing emulation of the x86 processor, > with SID, you have created its bus, pin and attribute interface and > now other components can exchange data as well as use the existing > processor emulation. Right. - FChE