qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH,RFC]: PCI Host Proxy v0.1
Date: Tue, 01 Jun 2004 01:12:36 +0100	[thread overview]
Message-ID: <1086048756.21922.39.camel@sherbert> (raw)
In-Reply-To: <1086048281.21903.33.camel@sherbert>

On Tue, 2004-06-01 at 01:04 +0100, Gianni Tedesco wrote:
> On Mon, 2004-05-31 at 18:16 +0100, Gianni Tedesco wrote:
> > Current limitations:
> >  o Memory resources are not mapped in yet.
> 
> Fabrice,
> 
> Will the following work for PCI memory spaces? (I don't have any setups
> which do MMIO atm to test on).
> 
> for (i=addr; i < addr + len; i+=4)
>     cpu_register_io_memory(i, pciproxy_readl, pciproxy_writel);

erm, i mean, actually i do:

#define IOMEM_PCIPROXY (5 << IO_MEM_SHIFT)

cpu_register_io_memory(IOMEM_PCIPROXY >> IO_MEM_SHIFT,
                       pciproxy_readl,
                       pciproxy_writel);

cpu_register_phys_mem(addr, len, IOMEM_PCIPROXY);

And can i still make the change to cpu_register_io_memory to pass down
an opaque pointer? Actually this would be nicer on the
cpu_register_phys_mem, but that'd be an impact on hot-paths i guess so
I'll just have to work around it in pciproxy.

-- 
// 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-06-01  0:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 17:16 [Qemu-devel] [PATCH,RFC]: PCI Host Proxy v0.1 Gianni Tedesco
2004-05-31 18:48 ` Kyle Hayes
2004-06-01  0:04 ` Gianni Tedesco
2004-06-01  0:12   ` Gianni Tedesco [this message]
2004-06-01  0:22     ` 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=1086048756.21922.39.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).