Re: [PATCH] iommu: moving initialization earlier

2013-01-11 Thread Shuah Khan
On Fri, Jan 11, 2013 at 7:50 AM, Joerg Roedel wrote: > On Thu, Jan 10, 2013 at 01:40:17PM -0700, Shuah Khan wrote: >> I am currently debugging IO_PAGE_FAULTS on 3.6.11 (happens on all >> pre-3.7 releases). I root-caused the reason 3.7 works is because in >> 3.7 amd iommu driver moving up the

Re: [PATCH] iommu: moving initialization earlier

2013-01-11 Thread Joerg Roedel
On Thu, Jan 10, 2013 at 01:40:17PM -0700, Shuah Khan wrote: > I am currently debugging IO_PAGE_FAULTS on 3.6.11 (happens on all > pre-3.7 releases). I root-caused the reason 3.7 works is because in > 3.7 amd iommu driver moving up the early iommu initialization from > irq_remap_ops with the irq

Re: [PATCH] iommu: moving initialization earlier

2013-01-11 Thread Joerg Roedel
On Thu, Jan 10, 2013 at 01:40:17PM -0700, Shuah Khan wrote: I am currently debugging IO_PAGE_FAULTS on 3.6.11 (happens on all pre-3.7 releases). I root-caused the reason 3.7 works is because in 3.7 amd iommu driver moving up the early iommu initialization from irq_remap_ops with the irq

Re: [PATCH] iommu: moving initialization earlier

2013-01-11 Thread Shuah Khan
On Fri, Jan 11, 2013 at 7:50 AM, Joerg Roedel j...@8bytes.org wrote: On Thu, Jan 10, 2013 at 01:40:17PM -0700, Shuah Khan wrote: I am currently debugging IO_PAGE_FAULTS on 3.6.11 (happens on all pre-3.7 releases). I root-caused the reason 3.7 works is because in 3.7 amd iommu driver moving up

Re: [PATCH] iommu: moving initialization earlier

2013-01-10 Thread Shuah Khan
On Thu, Jan 10, 2013 at 1:40 PM, Shuah Khan wrote: > On Thu, Jan 10, 2013 at 10:09 AM, Joerg Roedel wrote: >> On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote: >>> The iommu_init() initializes IOMMU internal structures and data >>> required for the IOMMU API as

Re: [PATCH] iommu: moving initialization earlier

2013-01-10 Thread Shuah Khan
On Thu, Jan 10, 2013 at 10:09 AM, Joerg Roedel wrote: > On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote: >> The iommu_init() initializes IOMMU internal structures and data >> required for the IOMMU API as iommu_group_alloc(). >> It is registered as a subsys_initcall now. >>

Re: [PATCH] iommu: moving initialization earlier

2013-01-10 Thread Joerg Roedel
On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote: > The iommu_init() initializes IOMMU internal structures and data > required for the IOMMU API as iommu_group_alloc(). > It is registered as a subsys_initcall now. > > One of the IOMMU users is going to be a PCI subsystem on

Re: [PATCH] iommu: moving initialization earlier

2013-01-10 Thread Joerg Roedel
On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote: The iommu_init() initializes IOMMU internal structures and data required for the IOMMU API as iommu_group_alloc(). It is registered as a subsys_initcall now. One of the IOMMU users is going to be a PCI subsystem on POWER.

Re: [PATCH] iommu: moving initialization earlier

2013-01-10 Thread Shuah Khan
On Thu, Jan 10, 2013 at 10:09 AM, Joerg Roedel j...@8bytes.org wrote: On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote: The iommu_init() initializes IOMMU internal structures and data required for the IOMMU API as iommu_group_alloc(). It is registered as a subsys_initcall

Re: [PATCH] iommu: moving initialization earlier

2013-01-10 Thread Shuah Khan
On Thu, Jan 10, 2013 at 1:40 PM, Shuah Khan shuahk...@gmail.com wrote: On Thu, Jan 10, 2013 at 10:09 AM, Joerg Roedel j...@8bytes.org wrote: On Mon, Jan 07, 2013 at 06:51:52PM +1100, Alexey Kardashevskiy wrote: The iommu_init() initializes IOMMU internal structures and data required for the

[PATCH] iommu: moving initialization earlier

2013-01-06 Thread Alexey Kardashevskiy
The iommu_init() initializes IOMMU internal structures and data required for the IOMMU API as iommu_group_alloc(). It is registered as a subsys_initcall now. One of the IOMMU users is going to be a PCI subsystem on POWER. It discovers new IOMMU tables during the PCI scan so the logical place to

Re: [PATCH] iommu: moving initialization earlier

2013-01-06 Thread Joerg Roedel
On Fri, Jan 04, 2013 at 07:21:34PM +1100, Alexey Kardashevskiy wrote: > On 16/12/12 22:20, Joerg Roedel wrote: > >Please resend the patch when the merge-window is closed. > > is it closed now? not sure I entirely understand what window you > kept in mind :) Yes, it is closed now :-) The

Re: [PATCH] iommu: moving initialization earlier

2013-01-06 Thread Joerg Roedel
On Fri, Jan 04, 2013 at 07:21:34PM +1100, Alexey Kardashevskiy wrote: On 16/12/12 22:20, Joerg Roedel wrote: Please resend the patch when the merge-window is closed. is it closed now? not sure I entirely understand what window you kept in mind :) Yes, it is closed now :-) The merge-window

[PATCH] iommu: moving initialization earlier

2013-01-06 Thread Alexey Kardashevskiy
The iommu_init() initializes IOMMU internal structures and data required for the IOMMU API as iommu_group_alloc(). It is registered as a subsys_initcall now. One of the IOMMU users is going to be a PCI subsystem on POWER. It discovers new IOMMU tables during the PCI scan so the logical place to

Re: [PATCH] iommu: moving initialization earlier

2013-01-04 Thread Alexey Kardashevskiy
On 16/12/12 22:20, Joerg Roedel wrote: Alexey, On Thu, Dec 13, 2012 at 08:48:55AM -0700, Alex Williamson wrote: Probably a good idea to CC the iommu list and maintainer... On Thu, 2012-12-13 at 17:28 +1100, Alexey Kardashevskiy wrote: Signed-off-by: Alexey Kardashevskiy Please resend the

Re: [PATCH] iommu: moving initialization earlier

2013-01-04 Thread Alexey Kardashevskiy
On 16/12/12 22:20, Joerg Roedel wrote: Alexey, On Thu, Dec 13, 2012 at 08:48:55AM -0700, Alex Williamson wrote: Probably a good idea to CC the iommu list and maintainer... On Thu, 2012-12-13 at 17:28 +1100, Alexey Kardashevskiy wrote: Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru

Re: [PATCH] iommu: moving initialization earlier

2012-12-16 Thread Joerg Roedel
Alexey, On Thu, Dec 13, 2012 at 08:48:55AM -0700, Alex Williamson wrote: > Probably a good idea to CC the iommu list and maintainer... > > On Thu, 2012-12-13 at 17:28 +1100, Alexey Kardashevskiy wrote: > > Signed-off-by: Alexey Kardashevskiy Please resend the patch when the merge-window is

Re: [PATCH] iommu: moving initialization earlier

2012-12-16 Thread Joerg Roedel
Alexey, On Thu, Dec 13, 2012 at 08:48:55AM -0700, Alex Williamson wrote: Probably a good idea to CC the iommu list and maintainer... On Thu, 2012-12-13 at 17:28 +1100, Alexey Kardashevskiy wrote: Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru Please resend the patch when the

Re: [PATCH] iommu: moving initialization earlier

2012-12-13 Thread Alex Williamson
Probably a good idea to CC the iommu list and maintainer... On Thu, 2012-12-13 at 17:28 +1100, Alexey Kardashevskiy wrote: > The iommu_init() call initializes IOMMU internal structures and data > required for the API to function such as iommu_group_alloc(). > It is registered as a

Re: [PATCH] iommu: moving initialization earlier

2012-12-13 Thread Alex Williamson
Probably a good idea to CC the iommu list and maintainer... On Thu, 2012-12-13 at 17:28 +1100, Alexey Kardashevskiy wrote: The iommu_init() call initializes IOMMU internal structures and data required for the API to function such as iommu_group_alloc(). It is registered as a subsys_initcall.

[PATCH] iommu: moving initialization earlier

2012-12-12 Thread Alexey Kardashevskiy
The iommu_init() call initializes IOMMU internal structures and data required for the API to function such as iommu_group_alloc(). It is registered as a subsys_initcall. One of the IOMMU users is a PCI subsystem on POWER which discovers new IOMMU tables during the PCI scan so the most logical

[PATCH] iommu: moving initialization earlier

2012-12-12 Thread Alexey Kardashevskiy
The iommu_init() call initializes IOMMU internal structures and data required for the API to function such as iommu_group_alloc(). It is registered as a subsys_initcall. One of the IOMMU users is a PCI subsystem on POWER which discovers new IOMMU tables during the PCI scan so the most logical