From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem Date: Sun, 3 Oct 2010 15:08:57 +0300 Message-ID: <20101003120857.GP2804@reaktio.net> References: <20101001211111.GA18244@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Bruce Edge Cc: xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Sat, Oct 02, 2010 at 10:46:45PM -0700, Bruce Edge wrote: > > > > and your devel/xen-pcifront-0.6 forces a config restart: > > > > 0 %> make oldconfig > > scripts/kconfig/conf --oldconfig arch/x86/Kconfig > > * > > * Restart config... > > * > > * > > * General setup > > * > > Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y > > Cross-compiler tool prefix (CROSS_COMPILE) [] (NEW) ^Cmake[1]: *** > > [oldconfig] Interrupt > > make: *** [oldconfig] Interrupt > > > > Is there a trick to avoiding the config restart? > > Found the problem here - I was using a .config from a 2.6.32 kernel. > There's something in the 2.6.36 config parsing that declares it > invalid and starts over. > Starting with a clean 'make defconfig' and editing that works fine. > > I had never see this behavior in kernel builds before. I thought the > .config files were always compatible between versions. > You need to do "make oldconfig" to adapt/merge the 2.6.32 config to 2.6.36. -- Pasi