* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
@ 2008-03-04 16:13 rubisher
2008-03-05 2:56 ` FUJITA Tomonori
0 siblings, 1 reply; 11+ messages in thread
From: rubisher @ 2008-03-04 16:13 UTC (permalink / raw)
To: fujita.tomonori
Cc: tomof, kyle, linux-kernel, linux-parisc, tomof, kyle, matthew,
grundler, akpm, fujita.tomonori, rubisher
[snip]
> > Can you try the following patch? It's on the top of the patchset.
> >
> Good catch: now this first testing system (I mean the b2k) is up and running ;-)
>
> I will now try the ccio_dma driver on a d380 ...
>
Yes, it works too on a d380 boxe running a 32bit up kernel.
Btw (it was a long time ago), I also resurrect my 64 config for the b2k model
and it also works fine.
Many tx again,
r.
> hth,
> r.
>
> > Thanks,
> >
> > diff --git a/drivers/parisc/ccio-dma.c b/drivers/parisc/ccio-dma.c
> > index 2f3b364..d0855a1 100644
> > --- a/drivers/parisc/ccio-dma.c
> > +++ b/drivers/parisc/ccio-dma.c
> > @@ -366,8 +366,8 @@ ccio_alloc_range(struct ioc *ioc, struct device *dev,
> size_t size)
> > ** ggg sacrifices another 710 to the computer gods.
> > */
> >
> > - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
> > - boundary_size >>= IOVP_SHIFT;
> > + boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
> > + 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
> >
> > if (pages_needed <= 8) {
> > /*
> > diff --git a/drivers/parisc/sba_iommu.c b/drivers/parisc/sba_iommu.c
> > index e834127..bdbe780 100644
> > --- a/drivers/parisc/sba_iommu.c
> > +++ b/drivers/parisc/sba_iommu.c
> > @@ -341,8 +341,8 @@ sba_search_bitmap(struct ioc *ioc, struct device *dev,
> > unsigned long shift;
> > int ret;
> >
> > - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
> > - boundary_size >>= IOVP_SHIFT;
> > + boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
> > + 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
> >
> > #if defined(ZX1_SUPPORT)
> > BUG_ON(ioc->ibase & ~IOVP_MASK);
> > --
---
Scarlet One, ADSL 6 Mbps + Telephone, from EUR 29,95...
http://www.scarlet.be/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
2008-03-04 16:13 [PATCH -mm 0/3] fix iommu segment boundary problems (parisc) rubisher
@ 2008-03-05 2:56 ` FUJITA Tomonori
0 siblings, 0 replies; 11+ messages in thread
From: FUJITA Tomonori @ 2008-03-05 2:56 UTC (permalink / raw)
To: rubisher
Cc: fujita.tomonori, tomof, kyle, linux-kernel, linux-parisc, kyle,
matthew, grundler, akpm
On Tue, 4 Mar 2008 17:13:55 +0100
"rubisher" <rubisher@scarlet.be> wrote:
> [snip]
> > > Can you try the following patch? It's on the top of the patchset.
> > >
> > Good catch: now this first testing system (I mean the b2k) is up and running ;-)
> >
> > I will now try the ccio_dma driver on a d380 ...
> >
> Yes, it works too on a d380 boxe running a 32bit up kernel.
Great, thanks a lot for testing both IOMMUs!
> Btw (it was a long time ago), I also resurrect my 64 config for the b2k model
> and it also works fine.
Nice, and sorry about the bug on 32bits boxes.
Thanks again,
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
2008-03-05 15:45 ` Grant Grundler
@ 2008-03-06 0:19 ` John David Anglin
0 siblings, 0 replies; 11+ messages in thread
From: John David Anglin @ 2008-03-06 0:19 UTC (permalink / raw)
To: Grant Grundler
Cc: fujita.tomonori, linux-kernel, linux-parisc, tomof, kyle,
matthew, grundler, akpm
> And thanks to Joel Soete (rubisher) for testing. I tried to test the
> sba_iommu code on my local box but had issues with the unpatched kernel
> (using kyle's parisc-2.6.git tree) that I have yet to resolve (could be
> HW problems).
I built two kernels today using kyle's parisc-2.6.git tree (UP 32 bit
and SMP 64 bit). Aside from some section mismatch warnings, they both
seem to work fine.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
2008-03-02 6:10 FUJITA Tomonori
2008-03-02 17:13 ` Kyle McMartin
@ 2008-03-05 15:45 ` Grant Grundler
2008-03-06 0:19 ` John David Anglin
1 sibling, 1 reply; 11+ messages in thread
From: Grant Grundler @ 2008-03-05 15:45 UTC (permalink / raw)
To: FUJITA Tomonori
Cc: linux-kernel, linux-parisc, tomof, Kyle McMartin, Matthew Wilcox,
Grant Grundler, Andrew Morton
On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> This patchset is another sequel to my patchset to fix iommu segment
> boundary problems, IOMMUs allocate memory areas without considering a
> low level driver's segment boundary limits:
>
> http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
>
> This patchset fixes the PARISC IOMMU code (sbc and ccio).
>
> There are three patches in this patchset. The first patch is for the
> IOMMU helper (lib/iommu-helper.c) to enable PARISC IOMMUs use it.
>
> The second and third patches are for PARISC IOMMUs, the second one is
> preparation for the third patch, which fixes the IOMMU segment
> boundary problem.
>
> The third patch assumes that ioc->ibase is on IOVP_SIZE boundary. If
> not, please let me know. I'll fix the patch.
Please add
Acked-by: Grant Grundler <grundler@parisc-linux.org>
This includes the 4th patch posted on march 3, 2008.
Thanks for posting this series. I've reviewed the code and it looks fine
to me as well (kyle already acked it).
And thanks to Joel Soete (rubisher) for testing. I tried to test the
sba_iommu code on my local box but had issues with the unpatched kernel
(using kyle's parisc-2.6.git tree) that I have yet to resolve (could be
HW problems).
thanks,
grant
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
2008-03-02 17:13 ` Kyle McMartin
@ 2008-03-05 3:54 ` FUJITA Tomonori
0 siblings, 0 replies; 11+ messages in thread
From: FUJITA Tomonori @ 2008-03-05 3:54 UTC (permalink / raw)
To: kyle
Cc: fujita.tomonori, linux-kernel, linux-parisc, tomof, kyle,
matthew, grundler, akpm
On Sun, 2 Mar 2008 12:13:11 -0500
Kyle McMartin <kyle@mcmartin.ca> wrote:
> On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> > This patchset is another sequel to my patchset to fix iommu segment
> > boundary problems, IOMMUs allocate memory areas without considering a
> > low level driver's segment boundary limits:
> >
> > http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
> >
>
> This looks fine. Are you able to test this? If not, we can set you up
> with an account on a machine with remote console and all that jazz, if
> you'd like to.
Thanks for the offer!
I don't have any parisc hardware. If -mm kernels are tested well with
parisc, I'd be happy to leave it in your guys' hands since I've never
used parisc and the patches seem to work (with the bug fix for 32bits
boxes).
I'd like to try if there are not people who try -mm kernels with
parisc or a bug that I can't fix easily will be found.
Thanks,
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
@ 2008-03-03 14:43 rubisher
0 siblings, 0 replies; 11+ messages in thread
From: rubisher @ 2008-03-03 14:43 UTC (permalink / raw)
To: tomof
Cc: kyle, fujita.tomonori, linux-kernel, linux-parisc, tomof, kyle,
matthew, grundler, akpm, fujita.tomonori, rubisher
> On Mon, 3 Mar 2008 12:04:00 +0100
> "rubisher" <rubisher@scarlet.be> wrote:
>
> > > On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> > > > This patchset is another sequel to my patchset to fix iommu segment
> > > > boundary problems, IOMMUs allocate memory areas without considering a
> > > > low level driver's segment boundary limits:
> > > >
> > > > http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
> > > >
> > >
> > > This looks fine. Are you able to test this? If not, we can set you up
> > > with an account on a machine with remote console and all that jazz, if
> > > you'd like to.
> > >
> > > cheers, Kyle
> > > --
[snip]
> Thanks a lot for testing!
>
Always welcome ;-)
> Really sorry about the bug.
Don't worry, those boxes are there for my fun...
> Can you try the following patch? It's on the top of the patchset.
>
Good catch: now this first testing system (I mean the b2k) is up and running ;-)
I will now try the ccio_dma driver on a d380 ...
hth,
r.
> Thanks,
>
> diff --git a/drivers/parisc/ccio-dma.c b/drivers/parisc/ccio-dma.c
> index 2f3b364..d0855a1 100644
> --- a/drivers/parisc/ccio-dma.c
> +++ b/drivers/parisc/ccio-dma.c
> @@ -366,8 +366,8 @@ ccio_alloc_range(struct ioc *ioc, struct device *dev,
size_t size)
> ** ggg sacrifices another 710 to the computer gods.
> */
>
> - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
> - boundary_size >>= IOVP_SHIFT;
> + boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
> + 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
>
> if (pages_needed <= 8) {
> /*
> diff --git a/drivers/parisc/sba_iommu.c b/drivers/parisc/sba_iommu.c
> index e834127..bdbe780 100644
> --- a/drivers/parisc/sba_iommu.c
> +++ b/drivers/parisc/sba_iommu.c
> @@ -341,8 +341,8 @@ sba_search_bitmap(struct ioc *ioc, struct device *dev,
> unsigned long shift;
> int ret;
>
> - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
> - boundary_size >>= IOVP_SHIFT;
> + boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
> + 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
>
> #if defined(ZX1_SUPPORT)
> BUG_ON(ioc->ibase & ~IOVP_MASK);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
---
Scarlet One, ADSL 6 Mbps + Telephone, from EUR 29,95...
http://www.scarlet.be/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
2008-03-03 11:04 rubisher
@ 2008-03-03 12:22 ` FUJITA Tomonori
0 siblings, 0 replies; 11+ messages in thread
From: FUJITA Tomonori @ 2008-03-03 12:22 UTC (permalink / raw)
To: rubisher
Cc: kyle, fujita.tomonori, linux-kernel, linux-parisc, tomof, kyle,
matthew, grundler, akpm, fujita.tomonori
On Mon, 3 Mar 2008 12:04:00 +0100
"rubisher" <rubisher@scarlet.be> wrote:
> > On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> > > This patchset is another sequel to my patchset to fix iommu segment
> > > boundary problems, IOMMUs allocate memory areas without considering a
> > > low level driver's segment boundary limits:
> > >
> > > http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
> > >
> >
> > This looks fine. Are you able to test this? If not, we can set you up
> > with an account on a machine with remote console and all that jazz, if
> > you'd like to.
> >
> > cheers, Kyle
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> Sorry for bad news but using a kernel known to work fine on my b2k (kyle's
> parisc-2.6.git date 2008_02_21) against which I applied those patches, this
> new kernel 32bit up failled to boot with this panic message:
>
> Linux Tulip driver version 1.1.15 (Feb 27, 2007)
> ------------[ cut here ]------------
> Kernel BUG at 1029520c [verbose debug info unavailable]
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001001111111100001110 Not tainted
> r00-03 0004ff0e 1054c010 1029e774 80000000
> r04-07 1fc2b020 00000100 00000000 00000001
> r08-11 1fc1d454 1fc2c000 00000000 80000000
> r12-15 00000001 00000001 1fc10858 0001a000
> r16-19 00000011 104a23d0 00000000 ffffffff
> r20-23 00001000 00000000 1fdb6a00 00000000
> r24-27 00000000 00000001 00000100 10507010
> r28-31 00000100 00100000 1fc205c0 00000000
> sr00-03 00000000 00000000 00000000 00000000
> sr04-07 00000000 00000000 00000000 00000000
> IASQ: 00000000 00000000 IAOQ: 1029520c 10295210
> IIR: 03ffe01f ISR: 1024003f IOR: 0802056c
> CPU: 0 CR30: 1fc20000 CR31: 11111111
> ORIG_R28: 0000000f
> IAOQ[0]: iommu_is_span_boundary+0x28/0x30
> IAOQ[1]: iommu_is_span_boundary+0x2c/0x30
> RP(r2): sba_alloc_range+0x23c/0x4f8
Thanks a lot for testing!
Really sorry about the bug. Can you try the following patch? It's on
the top of the patchset.
Thanks,
diff --git a/drivers/parisc/ccio-dma.c b/drivers/parisc/ccio-dma.c
index 2f3b364..d0855a1 100644
--- a/drivers/parisc/ccio-dma.c
+++ b/drivers/parisc/ccio-dma.c
@@ -366,8 +366,8 @@ ccio_alloc_range(struct ioc *ioc, struct device *dev, size_t size)
** ggg sacrifices another 710 to the computer gods.
*/
- boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
- boundary_size >>= IOVP_SHIFT;
+ boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
+ 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
if (pages_needed <= 8) {
/*
diff --git a/drivers/parisc/sba_iommu.c b/drivers/parisc/sba_iommu.c
index e834127..bdbe780 100644
--- a/drivers/parisc/sba_iommu.c
+++ b/drivers/parisc/sba_iommu.c
@@ -341,8 +341,8 @@ sba_search_bitmap(struct ioc *ioc, struct device *dev,
unsigned long shift;
int ret;
- boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1, 1 << IOVP_SHIFT);
- boundary_size >>= IOVP_SHIFT;
+ boundary_size = ALIGN((unsigned long long)dma_get_seg_boundary(dev) + 1,
+ 1ULL << IOVP_SHIFT) >> IOVP_SHIFT;
#if defined(ZX1_SUPPORT)
BUG_ON(ioc->ibase & ~IOVP_MASK);
^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
@ 2008-03-03 11:04 rubisher
2008-03-03 12:22 ` FUJITA Tomonori
0 siblings, 1 reply; 11+ messages in thread
From: rubisher @ 2008-03-03 11:04 UTC (permalink / raw)
To: kyle
Cc: fujita.tomonori, linux-kernel, linux-parisc, tomof, kyle,
matthew, grundler, akpm, rubisher
> On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> > This patchset is another sequel to my patchset to fix iommu segment
> > boundary problems, IOMMUs allocate memory areas without considering a
> > low level driver's segment boundary limits:
> >
> > http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
> >
>
> This looks fine. Are you able to test this? If not, we can set you up
> with an account on a machine with remote console and all that jazz, if
> you'd like to.
>
> cheers, Kyle
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Sorry for bad news but using a kernel known to work fine on my b2k (kyle's
parisc-2.6.git date 2008_02_21) against which I applied those patches, this
new kernel 32bit up failled to boot with this panic message:
Linux Tulip driver version 1.1.15 (Feb 27, 2007)
------------[ cut here ]------------
Kernel BUG at 1029520c [verbose debug info unavailable]
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001110 Not tainted
r00-03 0004ff0e 1054c010 1029e774 80000000
r04-07 1fc2b020 00000100 00000000 00000001
r08-11 1fc1d454 1fc2c000 00000000 80000000
r12-15 00000001 00000001 1fc10858 0001a000
r16-19 00000011 104a23d0 00000000 ffffffff
r20-23 00001000 00000000 1fdb6a00 00000000
r24-27 00000000 00000001 00000100 10507010
r28-31 00000100 00100000 1fc205c0 00000000
sr00-03 00000000 00000000 00000000 00000000
sr04-07 00000000 00000000 00000000 00000000
IASQ: 00000000 00000000 IAOQ: 1029520c 10295210
IIR: 03ffe01f ISR: 1024003f IOR: 0802056c
CPU: 0 CR30: 1fc20000 CR31: 11111111
ORIG_R28: 0000000f
IAOQ[0]: iommu_is_span_boundary+0x28/0x30
IAOQ[1]: iommu_is_span_boundary+0x2c/0x30
RP(r2): sba_alloc_range+0x23c/0x4f8
Backtrace:
[<10107938>] show_regs+0x2c8/0x450
[<10107c64>] die_if_kernel+0x98/0x1b0
[<101083a0>] handle_interruption+0x624/0x6b4
[<1010b078>] intr_check_sig+0x0/0x34
[<1015d07c>] rmqueue_bulk+0x44/0x9c
[<1015e778>] __alloc_pages+0xc4/0x388
[<1015ea74>] __get_free_pages+0x38/0x74
[<1029ed64>] sba_alloc_consistent+0x60/0xd4
[<105852f0>] tulip_init_one+0x2ac/0xd10
[<1029acb0>] pci_device_probe+0x70/0xa8
[<102dad50>] driver_probe_device+0xa4/0x1bc
[<102db01c>] __driver_attach+0x60/0xf4
[<102da1dc>] bus_for_each_dev+0x58/0xa0
[<102da978>] bus_add_driver+0xd4/0x1e0
[<102db34c>] driver_register+0x48/0x108
[<10565880>] kernel_init+0x120/0x33c
Backtrace:
[<10107c6c>] die_if_kernel+0xa0/0x1b0
[<101083a0>] handle_interruption+0x624/0x6b4
[<1010b078>] intr_check_sig+0x0/0x34
[<1015d07c>] rmqueue_bulk+0x44/0x9c
[<1015e778>] __alloc_pages+0xc4/0x388
[<1015ea74>] __get_free_pages+0x38/0x74
[<1029ed64>] sba_alloc_consistent+0x60/0xd4
[<105852f0>] tulip_init_one+0x2ac/0xd10
[<1029acb0>] pci_device_probe+0x70/0xa8
[<102dad50>] driver_probe_device+0xa4/0x1bc
[<102db01c>] __driver_attach+0x60/0xf4
[<102da1dc>] bus_for_each_dev+0x58/0xa0
[<102da978>] bus_add_driver+0xd4/0x1e0
[<102db34c>] driver_register+0x48/0x108
[<10565880>] kernel_init+0x120/0x33c
[<1010ac5c>] ret_from_kernel_thread+0x1c/0x24
Kernel panic - not syncing: Attempted to kill init!
(I haven't a lot a spare time right now, but I will do my best to help as much
as I can).
r.
---
Scarlet One, ADSL 6 Mbps + Telephone, from EUR 29,95...
http://www.scarlet.be/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
@ 2008-03-03 10:36 rubisher
0 siblings, 0 replies; 11+ messages in thread
From: rubisher @ 2008-03-03 10:36 UTC (permalink / raw)
To: kyle
Cc: fujita.tomonori, linux-kernel, linux-parisc, tomof, kyle,
matthew, grundler, akpm, rubisher
> On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> > This patchset is another sequel to my patchset to fix iommu segment
> > boundary problems, IOMMUs allocate memory areas without considering a
> > low level driver's segment boundary limits:
> >
> > http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
> >
>
> This looks fine. Are you able to test this? If not, we can set you up
> with an account on a machine with remote console and all that jazz, if
> you'd like to.
>
> cheers, Kyle
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Dear *,
I have access to 3 kind of boxes which needed one of those drivers: a b2k and
mainly a c110 and a d380 for which I hope a lot of this patch ;-)
I will so try the patch asap and let you know the results.
hth,
r.
---
Scarlet One, ADSL 6 Mbps + Telephone, from EUR 29,95...
http://www.scarlet.be/
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
2008-03-02 6:10 FUJITA Tomonori
@ 2008-03-02 17:13 ` Kyle McMartin
2008-03-05 3:54 ` FUJITA Tomonori
2008-03-05 15:45 ` Grant Grundler
1 sibling, 1 reply; 11+ messages in thread
From: Kyle McMartin @ 2008-03-02 17:13 UTC (permalink / raw)
To: FUJITA Tomonori
Cc: linux-kernel, linux-parisc, tomof, Kyle McMartin, Matthew Wilcox,
Grant Grundler, Andrew Morton
On Sun, Mar 02, 2008 at 03:10:25PM +0900, FUJITA Tomonori wrote:
> This patchset is another sequel to my patchset to fix iommu segment
> boundary problems, IOMMUs allocate memory areas without considering a
> low level driver's segment boundary limits:
>
> http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
>
This looks fine. Are you able to test this? If not, we can set you up
with an account on a machine with remote console and all that jazz, if
you'd like to.
cheers, Kyle
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH -mm 0/3] fix iommu segment boundary problems (parisc)
@ 2008-03-02 6:10 FUJITA Tomonori
2008-03-02 17:13 ` Kyle McMartin
2008-03-05 15:45 ` Grant Grundler
0 siblings, 2 replies; 11+ messages in thread
From: FUJITA Tomonori @ 2008-03-02 6:10 UTC (permalink / raw)
To: linux-kernel
Cc: linux-parisc, tomof, Kyle McMartin, Matthew Wilcox,
Grant Grundler, Andrew Morton
This patchset is another sequel to my patchset to fix iommu segment
boundary problems, IOMMUs allocate memory areas without considering a
low level driver's segment boundary limits:
http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11919.html
This patchset fixes the PARISC IOMMU code (sbc and ccio).
There are three patches in this patchset. The first patch is for the
IOMMU helper (lib/iommu-helper.c) to enable PARISC IOMMUs use it.
The second and third patches are for PARISC IOMMUs, the second one is
preparation for the third patch, which fixes the IOMMU segment
boundary problem.
The third patch assumes that ioc->ibase is on IOVP_SIZE boundary. If
not, please let me know. I'll fix the patch.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2008-03-06 0:19 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-04 16:13 [PATCH -mm 0/3] fix iommu segment boundary problems (parisc) rubisher
2008-03-05 2:56 ` FUJITA Tomonori
-- strict thread matches above, loose matches on Subject: below --
2008-03-03 14:43 rubisher
2008-03-03 11:04 rubisher
2008-03-03 12:22 ` FUJITA Tomonori
2008-03-03 10:36 rubisher
2008-03-02 6:10 FUJITA Tomonori
2008-03-02 17:13 ` Kyle McMartin
2008-03-05 3:54 ` FUJITA Tomonori
2008-03-05 15:45 ` Grant Grundler
2008-03-06 0:19 ` John David Anglin
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).