All of lore.kernel.org
 help / color / mirror / Atom feed
From: jerome Arbez-Gindre <jerome.arbez-gindre@laposte.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] need advice on PCI board emulation
Date: Fri, 08 Dec 2006 18:06:19 +0100	[thread overview]
Message-ID: <1165597579.9321.21.camel@bibi> (raw)
In-Reply-To: <200612081522.15548.paul@codesourcery.com>

On Fri, 2006-12-08 at 15:22 +0000, Paul Brook wrote:
> > I'm working on a modem PCI board emulation inside Qemu.
> 
> I misread "modem PCI board" as "modern PCI board" in your original post. The 
> correct response is much shorter:

I've replied to your former message before reading this one, sorry !

> 
> >  - to emulate demodulated incoming data, I launch one thread waiting
> > with blocking reads on a UDP socket.
> 
> You should use the existing serial devices.

I need demodulated data in my board emulation.
The aim of my project is to emulate a PCI board which does not exist at
this time, to help working on the driver.
I hope it will just work when i'll receive the first real board
prototype.

> 
> > So, my question is :
> > 	Is it reasonable to use threads to emulate parallel behaviors ?
> 
> No. You should copy how the existing devices (eg. serial ports) work.

As said, in my previsous message, I'll go deeper in the read of Qemu
sources.

> 
> You don't need parallel operation. Modems are low-bandwith devices, so you're 
> not going to get any performance benefit from using multiple threads.

The modem should handle 30 Mb/s.
I'm looking for realistic behaviour, performances is not a priority

Jérôme

      reply	other threads:[~2006-12-08 17:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 10:52 [Qemu-devel] need advice on PCI board emulation jerome Arbez-Gindre
2006-12-08 15:07 ` Paul Brook
2006-12-08 16:57   ` jerome Arbez-Gindre
2006-12-08 15:22 ` Paul Brook
2006-12-08 17:06   ` jerome Arbez-Gindre [this message]

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=1165597579.9321.21.camel@bibi \
    --to=jerome.arbez-gindre@laposte.net \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.