From: Benjamin LaHaise <bcrl@kvack.org>
To: "Màrius Montón" <Marius.Monton@uab.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 'virtual HW' into kernel (SystemC)
Date: Wed, 7 Sep 2005 10:16:51 -0400 [thread overview]
Message-ID: <20050907141651.GA10075@kvack.org> (raw)
In-Reply-To: <431EC16B.2040604@uab.es>
On Wed, Sep 07, 2005 at 12:31:07PM +0200, Màrius Montón wrote:
> At this point, we plan to develop a pci device driver to act as a bridge
> between kernel PCI subsystem and SystemC simulator (in user space).
>
> Do you think this implementation is fine? Maybe it's better to register
> a new bus
> subsystem and link to a daemon to user space to run SystemC simulations?
> We are open to any idea or suggestion about it.
That's actually quite a difficult approach to take as you aren't able to
fully simulate how the hardware interacts with the system, making concerns
like timing very difficult to accurately model. A better approach is to
tie into a full system simulator -- qemu makes it very easy to add a new
pci device into the system. This way your hardware simulator doesn't have
to worry about the complexities of kernel programming, and the resulting
device drivers doesn't need hooks for the simulator as it would see the
pci device as if it were installed in a system.
Btw, do you know of any inexpensive ways to be introduced SystemC
development on FPGAs? Cheers,
-ben
next prev parent reply other threads:[~2005-09-07 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 10:31 'virtual HW' into kernel (SystemC) Màrius Montón
2005-09-07 11:40 ` Jeff Garzik
2005-09-07 11:54 ` Muli Ben-Yehuda
2005-09-07 12:02 ` Eric Piel
2005-09-07 12:07 ` Jeff Garzik
2005-09-07 13:26 ` Màrius Montón
2005-09-07 14:16 ` Benjamin LaHaise [this message]
2005-09-07 14:59 ` linux-os (Dick Johnson)
2005-09-07 15:12 ` Màrius Montón
2005-09-07 17:01 ` Alan Cox
[not found] <BFECAF9E178F144FAEF2BF4CE739C66801B76517@exmail1.se.axis.com>
2005-09-07 16:38 ` Màrius Montón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050907141651.GA10075@kvack.org \
--to=bcrl@kvack.org \
--cc=Marius.Monton@uab.es \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox