All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH/RFC: PCI memory mapping
Date: Fri, 3 Apr 2009 15:28:45 +0000	[thread overview]
Message-ID: <200904031628.45716.paul@codesourcery.com> (raw)
In-Reply-To: <1238771149.28860.75.camel@nibbler.dlib.indiana.edu>

> So, for example, a cirrus vga device on bus 1 when calling:
>
> cpu_register_physical_memory(addr, s->vram_size,
> s->cirrus_linear_io_addr);

Ah, that's a different (but somewhat related) problem. This is for accesses 
from the CPU to the device. Most current IOMMU effect device->CPU 
accesses[1].

Paul

[1] For practical purposes assume the the CPU and system ram are on the same 
bus.

  reply	other threads:[~2009-04-03 15:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 14:57 [Qemu-devel] PATCH/RFC: PCI memory mapping Brian Wheeler
2009-04-02 15:18 ` [Qemu-devel] " Tristan Gingold
2009-04-02 17:23   ` Brian Wheeler
2009-04-02 17:32 ` [Qemu-devel] " Blue Swirl
2009-04-02 17:42   ` Brian Wheeler
2009-04-02 22:40 ` Paul Brook
2009-04-03 15:05   ` Brian Wheeler
2009-04-03 15:28     ` Paul Brook [this message]
2009-04-03 16:01       ` Brian Wheeler

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=200904031628.45716.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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.