All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trent Piepho <tpiepho@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	"maillist.kernel" <maillist.kernel@gmail.com>
Subject: Re: How to support 3GB pci address?
Date: Thu, 11 Dec 2008 20:07:06 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0812111957470.28806@t2.domain.actdsltmp> (raw)
In-Reply-To: <41706FC0-B740-42C0-BA2B-B9E4B5839477@kernel.crashing.org>

On Thu, 11 Dec 2008, Kumar Gala wrote:
> On Dec 11, 2008, at 6:04 AM, maillist.kernel wrote:
>> In the system, the total PCI address needed is about 3GB, so I want to know 
>> how to support it in linux. mpc8548 has 36-bit real address, and can 
>> support 32GB PCIE address space, but in linux, there is only 1GB kernel 
>> space, how to map the 3GB pci address to kernel? Is the  36-bit real 
>> address only used to support large memory(>4GB) for muti-threads?
>
> The 36-bit support is current (in tree) in complete.  Work is in progress to 
> add swiotlb support to PPC which will generically enable what you want to 
> accomplish.

Don't the ATMU windows in the pcie controller serve as a IOMMU, making swiotlb
unnecessary and wasteful?

  reply	other threads:[~2008-12-12  4:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 12:04 How to support 3GB pci address? maillist.kernel
2008-12-11 16:13 ` Kumar Gala
2008-12-12  4:07   ` Trent Piepho [this message]
2008-12-12  5:08     ` Kumar Gala
2008-12-12  9:04       ` Trent Piepho
2008-12-12 14:17         ` Kumar Gala
2008-12-12 17:13           ` Scott Wood
2008-12-12 20:34           ` Trent Piepho
2008-12-13  4:56             ` maillist.kernel
2008-12-13 22:11               ` Trent Piepho

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=Pine.LNX.4.64.0812111957470.28806@t2.domain.actdsltmp \
    --to=tpiepho@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=maillist.kernel@gmail.com \
    /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.