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

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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Possible bug with pass-through hot-plug?
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Wed, 7 Oct 2009 11:00:10 +0200
Delivery-date: Wed, 07 Oct 2009 02:00:38 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=V82Zbpf2w3PRuyKbbqvcBQxsJMg93xOSwBgg7aoyhcc=; b=oeQGxvxtnx4JlDeFcXYSUwElZQ8TkvrWooZ8HiWxp4WorS/lW87GrJ2UfYzZa8zldG 4h/XN0VltIG6mFMJCGLzNhvgHeljevlB7JRt6au3wZPT2a55njIzw7LrFExkr87jEIe0 kTf4rdX9RPq0etIMnuQe1G7rBe2yesibJd+IA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=tusX58QH9md+RnaO8+TJAY9NxBx/s4StID4RbSXhh6E+hOW+EkrKC3HdXHTDlDZ3iI YeSjhC+loCngKs0bpqd5g3yDCdCbQaLLCvGnPCV/z6+PujqaK6au4LPnd/6VAmadMUXO E4jNRZrvLeLmQJmsK6D1uH5bvss2YxALyvPFg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I'm testing the pass-through code, and trying to hot-plug & hot-remove
a PCI device which is in PT, and i think there is a bug in the
hot-plug code.
If i put the pass-through device on a "low" slot number, such as:
00:02.0 - then the hot-plug & hot-remove works, but if i use a "high"
slot number, such as: 00:1b.0, the hot-plug & hot-remove doesn't work.

>From looking at the qemu logs, it looks like the gpe event is "stuck"
and isn't finishing. I suspect, that it's because the gpe eventrelated
procedure in the DSDT, is level triggered (_L03), and thus, if the OS
doesn't handle it fast enough, it keeps getting the interrupt, and is
in kind of  "gpe storm" (that's why a "low" slot number, is working,
because it has less lines of the _L03 function in the DSDT to
evaluate).

Does anyone knows something about it? knows how to fix it?

Tom

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