lkml.org 
[lkml]   [2012]   [Nov]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 13/46] x86, mm: use pfn_range_is_mapped() with gart
    Date
    We are going to map ram only, so under max_low_pfn_mapped,
    between 4g and max_pfn_mapped does not mean mapped at all.

    Use pfn_range_is_mapped() directly.

    Signed-off-by: Yinghai Lu <yinghai@kernel.org>
    ---
    arch/x86/kernel/amd_gart_64.c | 5 ++---
    1 files changed, 2 insertions(+), 3 deletions(-)

    diff --git a/arch/x86/kernel/amd_gart_64.c b/arch/x86/kernel/amd_gart_64.c
    index e663112..b574b29 100644
    --- a/arch/x86/kernel/amd_gart_64.c
    +++ b/arch/x86/kernel/amd_gart_64.c
    @@ -768,10 +768,9 @@ int __init gart_iommu_init(void)
    aper_base = info.aper_base;
    end_pfn = (aper_base>>PAGE_SHIFT) + (aper_size>>PAGE_SHIFT);

    - if (end_pfn > max_low_pfn_mapped) {
    - start_pfn = (aper_base>>PAGE_SHIFT);
    + start_pfn = PFN_DOWN(aper_base);
    + if (!pfn_range_is_mapped(start_pfn, end_pfn))
    init_memory_mapping(start_pfn<<PAGE_SHIFT, end_pfn<<PAGE_SHIFT);
    - }

    pr_info("PCI-DMA: using GART IOMMU.\n");
    iommu_size = check_iommu_size(info.aper_base, aper_size);
    --
    1.7.7


    \
     
     \ /
      Last update: 2012-11-12 23:41    [W:2.447 / U:0.016 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site