All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@suse.cz>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: RFC [PATCH] x86/pci: reserve extra page to avoid error caused by P2P pref DMA reads
Date: Wed, 27 Aug 2008 17:40:40 +1000	[thread overview]
Message-ID: <1219822840.13162.184.camel@pasglop> (raw)
In-Reply-To: <1219822159-17245-1-git-send-email-yhlu.kernel@gmail.com>

On Wed, 2008-08-27 at 00:29 -0700, Yinghai Lu wrote:
> Diag guys, found one system when loading is high, will have gart wark error.
> root cause is P2P bridge try to prefetch for several intel e1000 under
> it. and that skb is near GART iommu area.
> 
> try to reserve page in the boundary at first.
> last page near TOM2, and last page near MMIO
> also gart first and last page.
> 
> need one better way for all arch support PCI and memory with a lot of holes etc.

Sounds like a similar problem for which we don't unmap GART pages,
just map them read-only and route them to a dummy page. In that
case, the right approach is to write the last page of the GART
to the dummy page as well and mark it occupied. That shouldn't
involve actually reserving memory.

I'm not familiar with the x86 PCI DMA code but afaik, it's fairly
similar to ours (powerpc) in that area.

Ben.
 
> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
> Cc: Pavel Machek <pavel@suse.cz>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Jesse Barnes<jbarnes@virtuousgeek.org>
> 
> ---
>  arch/x86/kernel/pci-dma.c     |   28 ++++++++++++++++++++++++++++
>  arch/x86/kernel/pci-gart_64.c |    6 ++++++
>  2 files changed, 34 insertions(+)
> 
> Index: linux-2.6/arch/x86/kernel/pci-dma.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/pci-dma.c
> +++ linux-2.6/arch/x86/kernel/pci-dma.c
> @@ -72,12 +72,40 @@ static int __init parse_dma32_size_opt(c
>  }
>  early_param("dma32_size", parse_dma32_size_opt);
>  
> +static void __init reserve_last_page(unsigned long pfn)
> +{
> +	unsigned long phys;
> +	void *ptr;
> +
> +	phys = (pfn - 1)<<PAGE_SHIFT;
> +	ptr = __alloc_bootmem_nopanic(PAGE_SIZE, PAGE_SIZE, phys);
> +
> +	if (!ptr || virt_to_phys(ptr) != phys)
> +		printk(KERN_WARNING "Can not hold last page near %lx for workaround P2P pref DMA reads!\n", phys);
> +	else
> +		printk(KERN_WARNING "Last page is reserved near %lx for workaround P2P pref DMA reads!\n", phys);
> +}
>  void __init dma32_reserve_bootmem(void)
>  {
>  	unsigned long size, align;
> +
> +	/*
> +	 * try to reserve last page to workaround P2P bridge pref DMA reads
> +	 * normally don't need to reserve the page near mmio,
> +	 * because always has acpi etc sit there.
> +	 * but some system has that acpi in the middle of ram below 4g
> +	 * so just reserve it.
> +	 */
> +	if (max_low_pfn_mapped < max_pfn_mapped)
> +		reserve_last_page(max_low_pfn_mapped);
> +
> +	/* less than 4G, don't need iommu */
>  	if (max_pfn <= MAX_DMA32_PFN)
>  		return;
>  
> +	/* try to reserve last page to workaround P2P bridge pref DMA reads */
> +	reserve_last_page(max_pfn);
> +
>  	/*
>  	 * check aperture_64.c allocate_aperture() for reason about
>  	 * using 512M as goal
> Index: linux-2.6/arch/x86/kernel/pci-gart_64.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/pci-gart_64.c
> +++ linux-2.6/arch/x86/kernel/pci-gart_64.c
> @@ -826,6 +826,9 @@ void __init gart_iommu_init(void)
>  	 */
>  	set_bit_string(iommu_gart_bitmap, 0, EMERGENCY_PAGES);
>  
> +	/* reserve one page at tail, for P2P bridge pref DMA reads */
> +	set_bit_string(iommu_gart_bitmap, iommu_pages - 1, 1);
> +
>  	agp_memory_reserved = iommu_size;
>  	printk(KERN_INFO
>  	       "PCI-DMA: Reserving %luMB of IOMMU area in the AGP aperture\n",
> @@ -870,6 +873,9 @@ void __init gart_iommu_init(void)
>  	for (i = EMERGENCY_PAGES; i < iommu_pages; i++)
>  		iommu_gatt_base[i] = gart_unmapped_entry;
>  
> +	/* we need set unmapped on head too, for P2P bridge pref DMA reads */
> +	iommu_gatt_base[0] = gart_unmapped_entry;
> +
>  	flush_gart();
>  	dma_ops = &gart_dma_ops;
>  }


  parent reply	other threads:[~2008-08-27  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  7:29 RFC [PATCH] x86/pci: reserve extra page to avoid error caused by P2P pref DMA reads Yinghai Lu
2008-08-27  7:37 ` Ingo Molnar
2008-08-27  7:40 ` Benjamin Herrenschmidt [this message]
2008-08-27  7:45   ` Yinghai Lu

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=1219822840.13162.184.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@suse.cz \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /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.