From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9033 invoked by alias); 28 Mar 2005 17:56:53 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 8950 invoked from network); 28 Mar 2005 17:56:47 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 28 Mar 2005 17:56:47 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j2SHukue017358 for ; Mon, 28 Mar 2005 12:56:46 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j2SHukO20525; Mon, 28 Mar 2005 12:56:46 -0500 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id j2SHukqH030073; Mon, 28 Mar 2005 12:56:46 -0500 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 27EF980004E; Mon, 28 Mar 2005 12:56:46 -0500 (EST) Received: from toenail.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by toenail.toronto.redhat.com (8.13.1/8.12.5) with ESMTP id j2SHujpL001417; Mon, 28 Mar 2005 12:56:45 -0500 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.13.1/8.13.1/Submit) id j2SHujsS001416; Mon, 28 Mar 2005 12:56:45 -0500 Date: Mon, 28 Mar 2005 17:56:00 -0000 From: "Frank Ch. Eigler" To: kobi maller Cc: sid@sources.redhat.com Subject: Re: Future of SID Message-ID: <20050328175644.GF30517@redhat.com> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XCIqNWEteo88hZlY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2005-q1/txt/msg00030.txt.bz2 --XCIqNWEteo88hZlY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 1925 Hi - > I was wondering what are the future plans for SID. > [...] > But I need to make more complex designs, an N-way SMP for example [...] Some degree of SMP modelling is straightforward: just instantiate N CPU components, and wire them up in a sid configuration file in whatever way is appropriate. Some of the flexibility can be expressed using the C++ configuration frontend's command line options. > [...] I looked for components such as a TLB that I could plug on the > bus, A complex TLB may be pretty hard to model as an isolated sid component, because of the interconnection with a typical MMU's page-table-fetching logic. > or DMA controller that I can use to generate IO traffic, but could > not find any. If you're not sure what flavour controller you'd like, then invent a very simple one, and perhaps script it in tcl. Or use a secondary general purpose processor with DMA-only "firmware". > [...] Are you planning to add examples for setting various type of > boards ? [...] Can you suggest an example to help me see what you mean? In some cases, supporting a "board" just means assembling a configuration from existing components, which is relatively simple. In others, it requires writing new components, which can span the whole spectrum of complexity. > What about the support for 'bochs' (x86). Are you going to continue > work on that when new 'bochs' is released? [...] The bottom > question is what are you planning for the next couple of years for > SID. [...] Red Hat is contracted to continue development of SID-based simulator ports, some of which are made public on an ongoing basis. These are generally focused efforts toward particular customers' requirements, though occasionally create nice general-purpose components. There are no plans at present to dedicate manpower to improving SID for its own sake. We would of course be happy to help users help themselves. - FChE --XCIqNWEteo88hZlY Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCSEVcVZbdDOm/ZT0RAj8GAJ9WVYIlUYwBtdpLEkFUGW//vzubPwCdE4Vv FvAjUDxl1vjVMd8qVlTxvgw= =ntd1 -----END PGP SIGNATURE----- --XCIqNWEteo88hZlY--