From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Error getting mfn
Date: Thu, 20 Sep 2012 17:28:24 -0400
Message-ID: <20120920212823.GE27312@konrad-lan.dumpdata.com>
References: <CAJ75kXZm-BqWdL2O41XkSE1VCdd4ruW=+CqDmR1b3=701RnXmw@mail.gmail.com>
	<20120918133650.GC12053@phenom.dumpdata.com>
	<CAJ75kXZEaCj4Jqs_qm46d7U-s1C2hkAONs8c5Audrw2c3X=nBA@mail.gmail.com>
	<20120920134851.GB1998@localhost.localdomain>
	<CAJ75kXZ0depUJF_h0yok-r4aL0TBGnqTpW_PKT4Q7P1_6R4X2A@mail.gmail.com>
	<20120920162337.GB8912@reaktio.net>
	<CAJ75kXaXbitBvosYp8Sv_548XbvdxU=M_NSSHTb_5d56=-n4nA@mail.gmail.com>
	<20120920163525.GC8912@reaktio.net>
	<CAJ75kXZnb82GnssNWxyGMHjTYiRQCRsNdPeYdEb-tsvkshpfEg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <CAJ75kXZnb82GnssNWxyGMHjTYiRQCRsNdPeYdEb-tsvkshpfEg@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: William Dauchy <wdauchy@gmail.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Thu, Sep 20, 2012 at 07:08:51PM +0200, William Dauchy wrote:
> Hi Konrad,
> 
> I finally got what you asked, xen output with dom0 included. sorry for
> the previous noise, there was some issues with my console redirection.

Ah. OK. so lets deal with one issue at hand. The CONFIG_NUMA - you said
you applied I posted for it some time ago? Is it this one?

http://lkml.indiana.edu/hypermail/linux/kernel/1205.3/03619.html

For the non-NUMA case - can you try to compile a kernel without
NUMA enabled and also include 'earlyprintk=xen' on your Linux command
line? That should give me a good approximation of what/where
it is being hit.