Re: [Xen-devel] Buffers not reachable by PCI

[Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx>]

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@xxxxxx> 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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel