From: George Dunlap <george.dunlap@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686)
Date: Fri, 26 Feb 2010 10:55:54 +0000 [thread overview]
Message-ID: <4B87A8BA.9010600@eu.citrix.com> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD9265125E7FC8782@shzsmsx501.ccr.corp.intel.com>
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
next prev parent reply other threads:[~2010-02-26 10:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 18:47 Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686) George Dunlap
2010-02-24 19:08 ` Sander Eikelenboom
2010-02-24 20:20 ` Pasi Kärkkäinen
2010-02-24 23:57 ` George Dunlap
2010-02-25 6:50 ` Jiang, Yunhong
2010-02-25 10:48 ` George Dunlap
2010-02-25 10:56 ` Jan Beulich
2010-02-25 11:46 ` George Dunlap
2010-02-25 12:13 ` George Dunlap
2010-02-25 13:07 ` Jan Beulich
2010-02-25 13:19 ` Sander Eikelenboom
2010-02-25 13:24 ` Pasi Kärkkäinen
2010-02-25 13:43 ` Jan Beulich
2010-02-25 14:05 ` Pasi Kärkkäinen
2010-02-25 13:28 ` George Dunlap
2010-02-26 11:05 ` George Dunlap
2010-02-26 11:14 ` Sander Eikelenboom
2010-02-26 11:21 ` George Dunlap
2010-02-26 12:04 ` Pasi Kärkkäinen
2010-02-26 12:26 ` Sander Eikelenboom
2010-02-26 1:42 ` Jiang, Yunhong
2010-02-26 10:55 ` George Dunlap [this message]
2010-02-26 10:56 ` George Dunlap
2010-02-25 13:10 ` Jan Beulich
2010-02-25 9:16 ` Jan Beulich
2010-02-25 9:28 ` Jiang, Yunhong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B87A8BA.9010600@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).