All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PCI: Memory mapped / ROM resources
Date: Wed, 26 May 2004 21:32:16 +0100	[thread overview]
Message-ID: <1085603535.4321.8.camel@sherbert> (raw)
In-Reply-To: <40B4FC37.7080601@bellard.org>

On Wed, 2004-05-26 at 21:21, Fabrice Bellard wrote:
> Hi,
> 
> Gianni Tedesco wrote:
> > I'm writing some qemu PCI devices and i'd like to know if it's possible
> > to register memory mapped I/O regions and also I'd like to be able to
> > map in a ROM device, but I guess this is missing for the same reason
> > memory mapped resources aren't currently supported. Is that to do with
> > the qemu CPU/MMU code?
> 
> Memory mapped resources are fully supported. ROM devices are not 
> supported, but it is very easy to add.

Yeah, i figred that just after I hit send my last post. (isnt that
always the way).

> > Is this going to be implemented any time soon, what are the issues if
> > any? I don't mind doing the monkey work to get it implemented, if i'm
> > pointed in the right direction. I haven't even looked at how the CPU
> > emulation parts work yet.
> 
> Which hardware do you want to add ? I can add ROM devices if it is 
> really necessary.

I'm adding a host PCI proxy layer that works under Linux, ie: make host
PCI devices appear within the emulator. Similar to 'pcidev' on bochs,
but without a custom kernel module, and some minor performance
enhancements. I ought to have a patch ready by tomorrow evening.

It's not amazingly urgent really, don't kill yourself over it, I'll
probably get around to adding it later myself.

PS. I am using mmap() on /proc/pci/bus/XX/YY.Z nodes to map PCI
registers, probably there is a nice way to allow the code generator to
generate accesses directly on to these vmas? It's probably not that much
of a win in any case, but interesting.

-- 
// Gianni Tedesco (gianni at scaramanga dot co dot uk)
lynx --source www.scaramanga.co.uk/scaramanga.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

  reply	other threads:[~2004-05-26 20:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 14:33 [Qemu-devel] PCI: Memory mapped / ROM resources Gianni Tedesco
2004-05-26 15:34 ` Gianni Tedesco
2004-05-26 20:21 ` Fabrice Bellard
2004-05-26 20:32   ` Gianni Tedesco [this message]
2004-05-26 21:45     ` Hetz Ben Hamo
2004-05-26 21:52       ` Gianni Tedesco
2004-05-26 22:50     ` Fabrice Bellard
2004-05-27  1:10       ` Gianni Tedesco

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=1085603535.4321.8.camel@sherbert \
    --to=gianni@scaramanga.co.uk \
    --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.