From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Joerg Roedel <joerg.roedel@amd•com>
Cc: FUJITA Tomonori <fujita.tomonori@lab•ntt.co.jp>,
sfr@canb•auug.org.au, davem@davemloft•net, mingo@elte•hu,
mingo@redhat•com, tglx@linutronix•de,
linux-kernel@vger•kernel.org, iommu@lists•linux-foundation.org,
bhavna.sarathy@amd•com, robert.richter@amd•com,
torvalds@linux-foundation•org, akpm@linux-foundation•org,
jbarnes@virtuousgeek•org, linux-next@vger•kernel.org
Subject: Re: [PATCH] add iommu_num_pages helper function
Date: Thu, 31 Jul 2008 08:44:14 +1000 [thread overview]
Message-ID: <1217457854.11188.348.camel@pasglop> (raw)
In-Reply-To: <20080729100233.GB4851@amd.com>
On Tue, 2008-07-29 at 12:02 +0200, Joerg Roedel wrote:
> On Tue, Jul 29, 2008 at 06:58:08PM +0900, FUJITA Tomonori wrote:
> > On Tue, 29 Jul 2008 11:50:27 +0200
> > Joerg Roedel <joerg.roedel@amd•com> wrote:
> > > do you want to work on that or should I try to do this and send it to
> > > you for review?
> >
> > I've already sent a patch that fixes the breakages in such way:
> >
> > http://marc.info/?l=linux-kernel&m=121730644704448&w=2
>
> Yes I have seen this patch. I meant the patches that introduce something
> like IOMMU_PAGE_SIZE for all architectures so that we can make this
> function generic and move it back to lib/.
That will not work in the light of some new stuff coming on powerpc in
the future. The iommu page size may/will be dynamic per instance of
iommu. IE, it will be mostly decided at runtime, I don't expect machines
to have multiple iommus of different page sizes off hand but it -can-
happen.
Ben.
next prev parent reply other threads:[~2008-07-30 22:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080725233325W.fujita.tomonori@lab.ntt.co.jp>
[not found] ` <20080726134156.GC4401@elte.hu>
[not found] ` <20080729110749.728c54e6.sfr@canb.auug.org.au>
[not found] ` <20080729104722H.fujita.tomonori@lab.ntt.co.jp>
2008-07-29 3:56 ` [PATCH] add iommu_num_pages helper function Stephen Rothwell
2008-07-29 4:38 ` FUJITA Tomonori
2008-07-29 5:26 ` David Miller
2008-07-29 5:42 ` FUJITA Tomonori
2008-07-29 5:24 ` David Miller
2008-07-29 5:42 ` FUJITA Tomonori
2008-07-29 6:45 ` Stephen Rothwell
2008-07-29 9:50 ` Joerg Roedel
2008-07-29 9:58 ` FUJITA Tomonori
2008-07-29 10:02 ` Joerg Roedel
2008-07-30 22:44 ` Benjamin Herrenschmidt [this message]
2008-07-31 2:07 ` FUJITA Tomonori
2008-07-29 10:10 ` David Miller
2008-07-29 10:26 ` Joerg Roedel
2008-07-29 10:27 ` FUJITA Tomonori
2008-07-29 10:31 ` Ingo Molnar
2008-07-29 10:33 ` David Miller
2008-07-29 12:45 ` Stephen Rothwell
2008-07-30 12:18 ` Joerg Roedel
2008-07-30 13:16 ` FUJITA Tomonori
2008-07-30 14:03 ` Joerg Roedel
2008-07-30 18:52 ` Joerg Roedel
2008-07-30 22:44 ` Benjamin Herrenschmidt
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=1217457854.11188.348.camel@pasglop \
--to=benh@kernel$(echo .)crashing.org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bhavna.sarathy@amd$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=fujita.tomonori@lab$(echo .)ntt.co.jp \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=joerg.roedel@amd$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=mingo@redhat$(echo .)com \
--cc=robert.richter@amd$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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