From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) Date: Fri, 26 Feb 2010 10:56:03 +0000 Message-ID: <4B87A8C3.9040703@eu.citrix.com> References: <25841307.20100224200810@eikelenboom.it> <20100224202009.GE2761@reaktio.net> <4B8665680200007800031406@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: 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: "Jiang, Yunhong" Cc: Sander Eikelenboom , Jeremy Fitzhardinge , "xen-devel@lists.xensource.com" , Jan Beulich List-Id: xen-devel@lists.xenproject.org Jiang, Yunhong wrote: > Hmm, this issue is caused because of changeset 18323, which extend the physdev_map_pirq strucutre. IIRC, this is mainly for SR-IOV support, that Xen can't get the MMIO BAR from the virtual device. > > However, dig into futher, I suspect if we need to change the definition of 'struct physdev_op'. Currently there is no maxium length limit, should it have something like the "pad" in struct xen_platform_op? > The padding isn't the problem; the problem is that Xen is expecting an address in there, but it's getting "garbage + {0,1}". As Jan pointed out, how is Xen supposed to distinguish an address from garbage + incorrect parameter? At any rate, I have a patch to the debian kernel I'll post in a bit. -George