This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: Xen 3.4 multi-function pass-through tree, isn't wor

To: Simon Horman <horms@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Xen 3.4 multi-function pass-through tree, isn't working...
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Mon, 27 Jul 2009 11:53:12 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 27 Jul 2009 01:53:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0HbibL2AsXp+NncAIg8yZGYTBYZjvKpW9oNsQ/qOCdw=; b=tHRT4A9quruq+pd7V+X7eKpfor1hGR2E6FOXIryDY5B+4uEDWSsNJ2YeSOgCL+hL8X oH5Ifcbi9T1U0KTtKfOTfBVxUmYgBEvc9WfN9S0dX4cPg1upTTzieGeZepXrsk9OKylk LFlAxholAO+vk/t6Oqremcg4BvXCEYF4f2PUM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LAJSrH8HP/1N6Aq+gpYZPqj5cZyZ/4RTnYqRhqZUphTYnEr5f84b5bivcvJMbxTt4/ sUxZC0q5fb/DNoYax4u+P32zWSqvf5K3B4hNQ6nZjIevReQjzQ/qmnpC1Bj5rd7qwb9Z 3zx01YQHY9AS/Ec5B+N24pUV7uKuvn3DrRr+U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090727083809.GA18950@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <8686c3cd0907200511h68ae5ea8ia5a833cd40b12c08@xxxxxxxxxxxxxx> <8686c3cd0907210022p78ab0125s388b66f6f177ed8@xxxxxxxxxxxxxx> <20090721101459.GC31093@xxxxxxxxxxxx> <20090722061142.GA11245@xxxxxxxxxxxx> <8686c3cd0907220335w78a136d7g7856c53bfe53c3c3@xxxxxxxxxxxxxx> <20090724090539.GA32268@xxxxxxxxxxxx> <8686c3cd0907260301i39b2a813yc7182eff51c6080b@xxxxxxxxxxxxxx> <20090727015821.GB28221@xxxxxxxxxxxx> <8686c3cd0907270103t7ffcd926u2eeada47ac8dc07d@xxxxxxxxxxxxxx> <20090727083809.GA18950@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

About the xenstore implementation - i have no clew about it, so i
guess i'm using the default implementation.
So, you will post a fix patch for it?


On Mon, Jul 27, 2009 at 11:38 AM, Simon Horman<horms@xxxxxxxxxxxx> wrote:
> On Mon, Jul 27, 2009 at 11:03:19AM +0300, Tom Rotenberg wrote:
>> Simon,
>> Thanks for investing the time to solve the bugs i'm reporting.
>> I must say, that the second problem i reported (the complete machine
>> freeze), is much important in my opinion, so i also hope, that someone
>> from the community, will give it a look, it's certainly blocking me,
>> and i don't know from where to start on this issue. Anyway, i'm
>> waiting for your inputs about the second problem.
> I suspect you are correct. I'll try and spend some time on it very soon.
>> On Mon, Jul 27, 2009 at 4:58 AM, Simon Horman<horms@xxxxxxxxxxxx> wrote:
>> > On Sun, Jul 26, 2009 at 01:01:02PM +0300, Tom Rotenberg wrote:
>> >> Simon,
>> >>
>> >> (BTW - Did you see my other mail, about a problem, which causes the
>> >> machine to freeze? i suspect that this might be due to the multi-fn
>> >> pass-through code. Can u please give your opinion about it?)
>> >
>> > Its quite likely that the problem that you are seeing is caused by
>> > multi-function.  Especially as a) you are probably the only person to
>> > exercise the code in this way so far and b) the PCI pass-through code is
>> > in my opinion very fragile.
>> >
>> > I haven't looked closely into the problem yet - I was kind of hoping
>> > someone else would while I was tracking down the cause of the
>> > other problems that you have reported.
>> >
>> >> Here is the resulting log:
>> >
>> > [snip]
>> >
>> >> [2009-07-26 05:59:12 4286] INFO (XendDomainInfo:2146) Created PCI device 
>> >> 0000:00:1a.0 at index 0 with state None
>> >> [2009-07-26 05:59:12 4286] INFO (XendDomainInfo:2146) Created PCI device 
>> >> 0000:00:1d.0 at index 1 with state None
>> >
>> > Thanks, that is very interesting. It looks like 0000:00:1a.0 is
>> > being inserted into xenstore twice, which is invalid. I'll hunt
>> > further to see if I can work out why that is occurring.
> On closer examination 0000:00:1a.0 != 0000:00:1d.0, so my comment
> immediately above is wrong.
> What I now think is happening is that for some reason on your system
> when _createDevices() initialises the devices in xenstore using
> _createDevice() then end up with no state entry. Whereas on my system
> then end up with state 3=Initialised.
> It seems to me that actually the behaviour of your system
> is correct and my system is bogus. I really don't know why
> that is the case - are you using the stock xenstore implementation
> in C, or the Ocaml version?
> In any case, it seems to be that your original work-around was more or less
> correct. I'll just tweak it a bit to handle the case where cleanupDevices()
> is shuffling entries because one or more have been deleted and repost it.

Xen-devel mailing list