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: Wed, 22 Jul 2009 12:02:51 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Jul 2009 02:03:20 -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=Nc08zqKL9C8iBIJoXJf5sDGs5C402I4XvQmomyVEe1Q=; b=b5a12tpMGK9a531sArMWl2cgIbLG1LwPxmBV3PxhsM5PcUOcYhiHgdmtYW2CiPvEtX +c4uldPByJRwEaMSElvcDtXraVhGVfFiG4nyekGwkujBdMDuBoC5ZO6bRNjvkHZsNBo7 tBqVRJsFLnCwrwyxYxBoT6bVFn3mSYJRPWwhI=
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=orNc8Hp2omzQIdxIRyhM//GG8XrFB6XvgWQOVkFJsJ5gj2fumETnzTKUjKKIHuz5PS SrEiOmbffmJz0j7kIZmBBSodEBmgxPgG66M3V7DCcdiDkeBghPO0XRZ3mfWKVK1aRVHk kXOXMVeFzlldmFkENVLuXhkn1pVnx7pHxDuDo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090722061142.GA11245@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: <8686c3cd0907200403w2a05cf1lfaf25dc8d7eb1821@xxxxxxxxxxxxxx> <20090720120459.GA31891@xxxxxxxxxxxx> <8686c3cd0907200511h68ae5ea8ia5a833cd40b12c08@xxxxxxxxxxxxxx> <20090721032302.GA13928@xxxxxxxxxxxx> <8686c3cd0907210022p78ab0125s388b66f6f177ed8@xxxxxxxxxxxxxx> <20090721101459.GC31093@xxxxxxxxxxxx> <20090722061142.GA11245@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I will try to do this this week, and give you the results (i hope i
will finish it by tomorrow).


On Wed, Jul 22, 2009 at 9:11 AM, Simon Horman<horms@xxxxxxxxxxxx> wrote:
> On Tue, Jul 21, 2009 at 08:15:00PM +1000, Simon Horman wrote:
>> On Tue, Jul 21, 2009 at 10:22:19AM +0300, Tom Rotenberg wrote:
>> > Simon,
>> >
>> > First of all, my workaround seems to work ok, so i think you should
>> > consider including it anyway (if there was an exception during state
>> > retrieval, then the state should be unknown, instead of throw an
>> > exception). Do u think you will add this patch to the multi-function
>> > code?
>> I am certainly considering adding it if we can't determine why this
>> happens. But it would be better to know why :-)
>> > I'm reproducing this, on a Lenovo T500 machine, which is different
>> > than your machine, since it also contains the 00:1a.2 device.
>> > Also, i don't specify the devices to be pass-through in the boot line,
>> > but rather, bind them to pciback after the machine boots.
>> Thanks, I'll see if binding them after boot sheds any light on the problem.
> Hi Tom,
> unfortuantely binding devices to pci-back after booting dom0 didn't
> help me to reproduce the problem.
> I'm wondering if you could run a few tests to try and isolate the problem
> 1) Try passing through the PCI devices one by one to try and
>   see which devices cause the problem that you are seeing and;
> 2) Do a bisection on the tree - say back to v3.4.1-rc6, to see
>   which changeset is causing the problem.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>