qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Re: PATCH, RFC: Generic DMA framework
Date: Tue, 28 Aug 2007 20:43:14 +0100	[thread overview]
Message-ID: <200708282043.17844.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580708281203k19068a8ag934d97f3450527b5@mail.gmail.com>

> On second thought, there is a huge difference between a write access
> originating from CPU destined for the device and the device writing to
> main memory. The CPU address could be 0xf000 1000, which may translate
> to a bus address of 0x1000, as an example. The device could write to
> main memory using the same bus address 0x1000, but this time the IOMMU
> would map this to for example 0x1234 5000, or without an IOMMU it
> would be just 0x1000.

While your concern is valid, your example is not.

You can't have the same bus address mapping onto both a device and main 
memory. Your example works if e.g. IO bus address 0x2000 1000 (or worse still 
0xf000 1000) maps onto system memory 0x1234 5000.

Conceptually you can have a separate IOMMU on every bus-bus or bus/host 
bridge, with asymmetric mappings depending where the transaction originates.

I believe some of the newer POWER machines can do this (x86 hardware with this 
capability is not generally available). The ARM PCI host bridge allows 
asymmetric mappings, thought this is simple regions rather than a full IOMMU, 
and is currently not implemented.

Paul

  reply	other threads:[~2007-08-28 19:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 19:48 [Qemu-devel] PATCH, RFC: Generic DMA framework Blue Swirl
2007-08-16 18:18 ` [Qemu-devel] " Blue Swirl
2007-08-16 19:58   ` malc
2007-08-19 17:46     ` Blue Swirl
2007-08-24 19:40 ` Blue Swirl
2007-08-24 20:18   ` Paul Brook
2007-08-24 23:33     ` Fabrice Bellard
2007-08-25  0:29       ` Paul Brook
2007-08-26 11:30         ` Fabrice Bellard
2007-08-26 17:54           ` Blue Swirl
2007-08-28 19:03             ` Blue Swirl
2007-08-28 19:43               ` Paul Brook [this message]
2007-08-29 17:00                 ` Blue Swirl
2007-08-29 20:39                   ` Paul Brook
2007-08-29 21:18                     ` Paul Brook
2007-09-08 14:07                       ` Blue Swirl
2007-09-08 14:31                         ` Paul Brook
2007-09-08 14:53                           ` Blue Swirl
2007-09-08 16:03                             ` Paul Brook
2007-09-15 16:16                               ` Blue Swirl

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=200708282043.17844.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=blauwirbel@gmail.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 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).