WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Possible bug with pass-through hot-plug?

To: Simon Horman <horms@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Possible bug with pass-through hot-plug?
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Sun, 18 Oct 2009 07:20:05 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 17 Oct 2009 22:20:36 -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; bh=otPlf/dFhqNYyr9+AgRU7eQI+VbjZ35cYhKV5KPlfHc=; b=SQCUdejBm7PiIrA0pKfXz9minh4CEMHkGhc+StdyXS9713G8SZj6qnIPynv99CTPiR QiE1ChvXpSCi4b6m9Dyk4K911eTX2WcoFmRstYdezc63pxGgpeQoe4oj1S80lxILXLr9 3Z9xL+mJ9FBo3xSP6IDe81sFw0Kwqv9fbFZ74=
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; b=sJGk1+N2kqQMZVzQ8IKNXyMtxgIzF6ko9pu+4XBy0jumBr2pyM635r6N64cTH2O2ZX dE+tSs4u4ACKmBSO5FHWMmaVnDgeEGT5yAW2MKSwO+aonrP/6lazvMT2I9vEj2NPmGA+ pdKg6gK5CCF+cHn/8q8WJDcujgfMTtF7iWRJw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091016074352.GA17063@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: <20091010014127.GB22324@xxxxxxxxxxxx> <20091012223616.GC9072@xxxxxxxxxxxx> <8686c3cd0910130208k7b9b0feva576864c9d819737@xxxxxxxxxxxxxx> <20091013094345.GA16712@xxxxxxxxxxxx> <8686c3cd0910130252m6a57388cv8b4d5211a14a4998@xxxxxxxxxxxxxx> <20091015093107.GA11293@xxxxxxxxxxxx> <8686c3cd0910150238h3d79d81dse8ee1ecb8f5350f2@xxxxxxxxxxxxxx> <20091015110632.GA14946@xxxxxxxxxxxx> <8686c3cd0910150702l542f75cbq6ffeee9c1ea47057@xxxxxxxxxxxxxx> <20091016074352.GA17063@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Simon,

Just checked what u propsed, and it works.
So, i'm pretty sure, that the problem is with the ASL code. I thought
of an implementaion change of the ASL code, which will make it work:
we will change it from:
...
if ( slt == 0x1 )
else if (slt == 0x2)
...
else if (slt == 0x20)
.,..

to the following (just as an example):
if ( slt < 0x10 )
{
    if (slt == 0x1)
...
} else {
    if ( slt == 0x11)
...
}

What do u think about this?


On Fri, Oct 16, 2009 at 9:43 AM, Simon Horman <horms@xxxxxxxxxxxx> wrote:
> On Thu, Oct 15, 2009 at 04:02:59PM +0200, Tom Rotenberg wrote:
>> Well, i don't have a patch for it, as i'm not that skilled with
>> writing ASL code for the DSDT.
>> When i tried to change the levle interrupt to edge, it didn't work,
>> although i though it should work, so it might be a bug i wrote.
>>
>> Bottom line, if you are skilled enough to write a "smarter" device
>> search code for the DSDT - you should try it. I think that will solve
>> it. If you don't think you'll be able to pull it off, i can try to
>> prepare a patch, but it's not my sepciality... :)
>>
>> What do u think we should do to solve it?
>
> I did think of a check that might help.
>
> It is to simply move slot 8 (which is the lowest numbered slot
> that fails for me) up to be the first if clause. That should
> exercise your timing theory without having to get too involved
> in how to write better ASL (which frankly seems a bit painful to me).
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel