From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GmVJc-0000VI-Az for qemu-devel@nongnu.org; Tue, 21 Nov 2006 08:05:32 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GmVJY-0000T0-BL for qemu-devel@nongnu.org; Tue, 21 Nov 2006 08:05:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GmVJY-0000Sn-61 for qemu-devel@nongnu.org; Tue, 21 Nov 2006 08:05:28 -0500 Received: from [64.233.162.201] (helo=nz-out-0102.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GmVJX-0007bw-9k for qemu-devel@nongnu.org; Tue, 21 Nov 2006 08:05:27 -0500 Received: by nz-out-0102.google.com with SMTP id i11so1965320nzi for ; Tue, 21 Nov 2006 05:05:26 -0800 (PST) Message-ID: Date: Tue, 21 Nov 2006 14:05:25 +0100 From: "Alessandro Corradi" Subject: Re: [Qemu-devel] SystemC Cosimulation In-Reply-To: <4562CAC4.4010209@uab.es> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_60874_23410135.1164114325893" References: <3518719F06577C4F85DA618E3C37AB910769CC47@nimbus.ott.qnx.com> <4562CAC4.4010209@uab.es> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_60874_23410135.1164114325893 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I already did this simulation/integration between qemu/systemC. I integrate= d a simple memory writen in SystemC and it communicate with QEMU via socket . It works very fine, the os installed on qemu (debian 3.1) can communicate with it, but I didn't recognize it as a PCI device and I didn't implement irq mechanism. This because I'm not so strong in C programming (this is a work for my university and my degree's thesys). Moreover I didn't find usefull documentation, I wrote my code based only on parallel.c and serial.= c code. I don't know why it works without irq... I tried to do something but irq ar= e not "launched". If you are interested I written some emails in devel mail list with some information and question... The systemC description is a stand alone process that receive and send messagges via socket. I added a module in QEMU in order to estabilish a connection at initializzation time and send/receive data when a write/read is done. As I told, the main point that I don't understand are: -irq managing, -create a device and manage it as a pci device. Thanks, Alessandro 2006/11/21, M=E0rius Mont=F3n : > > Yes, thats the idea behind our work. > We write a module for qemu that emulates Altera PCI Core. By one side thi= s > module is 'attached' to qemu PCI bus, and for on the other side is the > systemC interface to any module you write. Then, any OS running into Qemu > sees this new PCI device, and you can develop your driver, of course. > > Actually, all this stuff must be compiled and linked together, and when > running systemC simulation, qemu is freezed, so no time considerations ca= n > be taken. > > In next version, I'll try to split into two executables: one for qemu and > one for systemC simulator, both connected using sockets or something > similar. > > we will publish this work in our website soon > > Thank for you attention, > > M=E0rius > > Doug Schaefer wrote: > > Very cool. I'm guessing that this means that you can take any SystemC > design and use qemu to develop drivers for it, yes? > > > > Cheers, > > Doug Schaefer > > > ------------------------------ > > *From:* qemu-devel-bounces+dschaefer=3Dqnx.com@nongnu.org [ > mailto:qemu-devel-bounces+dschaefer=3Dqnx.com@nongnu.org] > *On Behalf Of *M=E0rius Mont=F3n > *Sent:* Monday, November 20, 2006 1:37 PM > *To:* qemu-devel@nongnu.org > *Subject:* [Qemu-devel] SystemC Cosimulation > > > > Hi, > > As a HW researcher, me and one student at my charge have develop a device > to Qemu. This device is connecto to virtual PC as a PCI device, and its > functionality is described using SystemC. > > I'm finishing to clean the code up, and our intention is to publish all > code. Also, I will continue development of this work to add more features > (like async communications and IRQ generation). > > Thanks, > > M=E0rius Mont=F3n > > > > ------------------------------ > > _______________________________________________ > Qemu-devel mailing listQemu-devel@nongnu.orghttp://lists.nongnu.org/mailm= an/listinfo/qemu-devel > > > -- > M=E0rius Mont=F3n i Maci=E1n marius.monton@uab.cat http://cephis.ua= b.es > Hardware Engineer > CEPHIS > Centre de Prototips i Solucions Hardware-Software > Dep. Microelectr=F2nica i Sistemes Electr=F2nics > ETSE - Universitat Aut=F2noma de Barcelona (UAB) Phone: +34 935 813 534 > Fax: +34 935 813 033 > QC-2090D. ETSE. Campus UAB. > 080193 Bellaterra > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > > > > ------=_Part_60874_23410135.1164114325893 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hello,
 
I already did this simulation/integration between qemu/systemC. I inte= grated a simple memory writen in SystemC and it communicate with QEMU via s= ocket .
It works very fine, the os installed on qemu (debian 3.1) can communic= ate with it, but I didn't recognize it as a PCI device and I didn't impleme= nt irq mechanism. This because I'm not so strong in C programming (this is = a work for my university and my degree's thesys). Moreover I didn't find us= efull documentation, I wrote my code based only on=20 parallel.c and serial.c code.
I don't know why it works without irq... I tried to do something = but irq are not "launched".
 
If you are interested I written some emails in devel mail list with so= me information and question...
 
The systemC description is a stand alone process that receive and= send messagges via socket. I added a module in QEMU in order to estabilish= a connection at initializzation time and send/receive data when a write/re= ad is done.
As I told, the main point that I don't understand are:
-irq managing,
-create a device and manage it as a pci device.
 
Thanks,
 
Alessandro

 
2006/11/21, M=E0rius Mont=F3n <marius.monton@uab.es>:
Yes, thats the idea behind our wo= rk.
We write a module for qemu that emulates Altera PCI Core. By one si= de this module is 'attached' to qemu PCI bus, and for on the other side is = the systemC interface to any module you write. Then, any OS running into Qe= mu sees this new PCI device, and you can develop your driver, of course.

Actually, all this stuff must be compiled and linked together, and = when running systemC simulation, qemu is freezed, so no time considerations= can be taken.

In next version, I'll try to split into two executab= les: one for qemu and one for systemC simulator, both connected using socke= ts or something similar.

we will publish this work in our website soon

Thank for you = attention,

M=E0rius

Doug Schaefer wrote:=20

Very cool. I'm guessing that this m= eans that you can take any SystemC design and use qemu to develop drivers f= or it, yes?

 

Cheers,

Doug Schaefer

 

From= : qemu-= devel-bounces+dschaefer=3Dqnx.com@nongnu.org [ mailto:qemu-devel-bounces+dschaefer=3Dqnx.com@nongnu.org] On Behalf Of M=E0rius Mont=F3n
Sent: Monday, November 20, 2006 1= :37 PM
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] SystemC Cosimulation

 

Hi,

As a HW researc= her, me and one student at my charge have develop a device to Qemu. This de= vice is connecto to virtual PC as a PCI device, and its functionality is de= scribed using SystemC.

I'm finishing to clean the code up, and our intention is to publish= all code. Also, I will continue development of this work to add more featu= res (like async communications and IRQ generation).

Thanks,

M=E0rius Mont=F3n

 

_______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://list= s.nongnu.org/mailman/listinfo/qemu-devel

--
M=E0rius Mont=F3n i Maci=E1n   marius.monton@ua= b.cat    http://cephis.uab.es
Hardware Engineer
CEPHIS
Centre de Prototips i Solucions Hardware-Software
Dep. Microelectr=F2nic= a i Sistemes Electr=F2nics
ETSE - Universitat Aut=F2noma de Barcelona (U= AB) 		Phone: +34 935 813 534<= br>Fax: +34 935 813 = 033
QC-2090D. ETS= E. Campus UAB.
080193 Bellaterr= a

______________= _________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel



------=_Part_60874_23410135.1164114325893--