| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH] Re-enable MSI support
|
To: |
Espen Skoglund <espen.skoglund@xxxxxxxxxxxxx> |
|
Subject: |
RE: [Xen-devel] [PATCH] Re-enable MSI support |
|
From: |
Espen Skoglund <espen.skoglund@xxxxxxxxxxxxx> |
|
Date: |
Wed, 10 Dec 2008 17:41:32 +0000 |
|
Cc: |
"wei.wang2@xxxxxxx" <wei.wang2@xxxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
|
Delivery-date: |
Wed, 10 Dec 2008 09:42:11 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<18751.62957.797341.541925@xxxxxxxxxxxxxxxxxx> |
|
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: |
<E2263E4A5B2284449EEBD0AAB751098401C31CA5E9@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <18751.43300.900610.363039@xxxxxxxxxxxxxxxxxx> <0A882F4D99BBF6449D58E61AAFD7EDD601E23C88@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <18751.56590.620965.388937@xxxxxxxxxxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401C31CAD86@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <18751.62957.797341.541925@xxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
[Espen Skoglund]
>> Also, as for the reference to pci_dev, do you have plan to add such
>> support? For example, I'm not sure if we can return fail for
>> pci_remove_device if there is still reference to it? Will dom0
>> support such failure?
> The reason I opted for a pdev->spinlock rather than refcount was
> that removing a pdev with a refcount is kind of messy. The pdev is
> not an anonymous struct that can be released by, e.g., an RCU like
> mechanism. It is intrinsically tied with a BDF, and we can not
> create a new pdev for that BDF until the previous pdev struct has
> been completely purged.
> [...me rambling on...]
Forget what I just said about rw_lock ordering. I forgot about the
write_lock on list insert/delete.
eSk
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH] Re-enable MSI support, Jiang, Yunhong
- Re: [Xen-devel] [PATCH] Re-enable MSI support, Espen Skoglund
- RE: [Xen-devel] [PATCH] Re-enable MSI support, Tian, Kevin
- RE: [Xen-devel] [PATCH] Re-enable MSI support, Jiang, Yunhong
- RE: [Xen-devel] [PATCH] Re-enable MSI support, Espen Skoglund
- RE: [Xen-devel] [PATCH] Re-enable MSI support, Jiang, Yunhong
- Re: [Xen-devel] [PATCH] Re-enable MSI support, Keir Fraser
- RE: [Xen-devel] [PATCH] Re-enable MSI support, Espen Skoglund
- RE: [Xen-devel] [PATCH] Re-enable MSI support,
Espen Skoglund <=
- Re: [Xen-devel] [PATCH] Re-enable MSI support, Keir Fraser
- RE: [Xen-devel] [PATCH] Re-enable MSI support, Jiang, Yunhong
|
|
|
| |
|
Home