From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/8] Remove unused pte_offset variable
Date: Wed, 27 Feb 2008 19:04:51 +1100 [thread overview]
Message-ID: <1204099491.15052.227.camel@pasglop> (raw)
In-Reply-To: <180c3c87682d05b1d58e50df77f99478f98d9b30.1204097262.git.michael@ellerman.id.au>
On Wed, 2008-02-27 at 18:28 +1100, Michael Ellerman wrote:
> The cell IOMMU code no longer needs to save the pte_offset variable
> separately, it is incorporated into tbl->it_offset.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> ---
Do this work on spider ?
There is a subtle difference with spider is that the 0x80000000 you give
to devices disappears when reaching the iommu (so isn't to be catered
in the iommu offset).
It's a bit like the offset you have to add to the direct mapping on
axon, in fact (the 0x8000060000000000 or so ...)
Ben.
> arch/powerpc/platforms/cell/iommu.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/arch/powerpc/platforms/cell/iommu.c b/arch/powerpc/platforms/cell/iommu.c
> index 4e75919..555d264 100644
> --- a/arch/powerpc/platforms/cell/iommu.c
> +++ b/arch/powerpc/platforms/cell/iommu.c
> @@ -123,7 +123,6 @@ struct iommu_window {
> struct cbe_iommu *iommu;
> unsigned long offset;
> unsigned long size;
> - unsigned long pte_offset;
> unsigned int ioid;
> struct iommu_table table;
> };
> @@ -475,13 +474,11 @@ cell_iommu_setup_window(struct cbe_iommu *iommu, struct device_node *np,
> window->size = size;
> window->ioid = ioid;
> window->iommu = iommu;
> - window->pte_offset = pte_offset;
>
> window->table.it_blocksize = 16;
> window->table.it_base = (unsigned long)iommu->ptab;
> window->table.it_index = iommu->nid;
> - window->table.it_offset = (offset >> IOMMU_PAGE_SHIFT) +
> - window->pte_offset;
> + window->table.it_offset = (offset >> IOMMU_PAGE_SHIFT) + pte_offset;
> window->table.it_size = size >> IOMMU_PAGE_SHIFT;
>
> iommu_init_table(&window->table, iommu->nid);
next prev parent reply other threads:[~2008-02-27 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 7:28 [PATCH 1/8] Clearup cell IOMMU fixed mapping terminology Michael Ellerman
2008-02-27 7:28 ` [PATCH 2/8] Use it_offset not pte_offset in cell IOMMU code Michael Ellerman
2008-02-27 7:28 ` [PATCH 3/8] Remove unused pte_offset variable Michael Ellerman
2008-02-27 8:04 ` Benjamin Herrenschmidt [this message]
2008-02-27 8:11 ` Michael Ellerman
2008-02-27 8:18 ` Benjamin Herrenschmidt
2008-02-27 7:28 ` [PATCH 5/8] Split setup of IOMMU stab and ptab, allocate dynamic/fixed ptabs separately Michael Ellerman
2008-02-27 7:28 ` [PATCH 4/8] Move allocation of cell IOMMU pad page Michael Ellerman
2008-02-27 7:28 ` [PATCH 6/8] Cell IOMMU: n_pte_pages is in 4K page units, not IOMMU_PAGE_SIZE Michael Ellerman
2008-02-27 7:28 ` [PATCH 7/8] Allow for different IOMMU page sizes in cell IOMMU code Michael Ellerman
2008-02-27 7:28 ` [PATCH 8/8] Convert the cell IOMMU fixed mapping to 16M IOMMU pages Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2008-02-29 7:33 [PATCH 1/8] Clearup cell IOMMU fixed mapping terminology Michael Ellerman
2008-02-29 7:33 ` [PATCH 3/8] Remove unused pte_offset variable Michael Ellerman
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=1204099491.15052.227.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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.