From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: Buffers not reachable by PCI
Date: Wed, 14 Dec 2011 15:11:48 -0400
Message-ID: <20111214191148.GA17432@andromeda.dapyr.net>
References: <3E243B26F475504B9BB0BCC9728B0DA629E16E01@USILMS110A.ca.com>
	<20111209203010.GA14412@andromeda.dapyr.net>
	<3E243B26F475504B9BB0BCC9728B0DA629E17AEA@USILMS110A.ca.com>
	<20111213001912.GA2730@konrad-lan>
	<3E243B26F475504B9BB0BCC9728B0DA629E184FA@USILMS110A.ca.com>
	<20111213232759.GA8702@konrad-lan>
	<3E243B26F475504B9BB0BCC9728B0DA629E18564@USILMS110A.ca.com>
	<4EE8785A0200007800067A16@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <4EE8785A0200007800067A16@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xensource.com>, Leonid Kalev <Leonid.Kalev@ca.com>, Tushar N Dave <tushar.n.dave@intel.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, Dec 14, 2011 at 09:20:10AM +0000, Jan Beulich wrote:
> >>> On 14.12.11 at 01:38, "Taylor, Neal E" <Neal.Taylor@ca.com> wrote:
> > [    0.000000] MFN 0x7f7f->0x7f00
> 
> This is clearly indicating the last chunk ends well below the 4G boundary.
> 
> > [    0.000000] Placing 64MB software IO TLB between d832cf00 - dc32cf00
> > [    0.000000] software IO TLB at phys 0x1832cf00 - 0x1c32cf00
> > [    0.000000] software IO TLB at bus 0x1c0f00 - 0x120fdff00
> 
> Consequently, the question is how you got to this value, or what
> changed between the first and last quoted printouts.

<nods>

Neal, I would also strongly recommend you try v3.0.6 - as there are a
couple of important fixes in it:

310fef9 xen/e820: if there is no dom0_mem=, don't tweak extra_pages.
0208b80 xen: use maximum reservation to limit amount of usable RAM
d63c8a0 mm: sync vmalloc address space page tables in alloc_vm_area()
0b129e1 xen/smp: Warn user why they keel over - nosmp or noapic and what
to use instead.
1f51b5d xen: x86_32: do not enable iterrupts when returning from
exception in interrupt context

Especially the dom0_mem - which I think you are using but the values are not
latching on. This is seperate from the issue you are hitting but I do
wonder if they might have an impact.