From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sebastian Hetze <s.hetze@linux-ag.com>
Subject: PCI capabilities support for assigned devices
Date: Wed, 10 Mar 2010 14:52:30 +0100
Message-ID: <20100310135230.5DA9B30301EB@mail.linux-ag.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from ironport.linux-ag.com ([62.245.157.240]:6036 "EHLO
	ironport.linux-ag.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932254Ab0CJOCK (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 10 Mar 2010 09:02:10 -0500
Received: from localhost (mail.linux-ag.de [62.245.157.206])
	by mail.linux-ag.de (Postfix) with ESMTP id 5DA9B30301EB
	for <kvm@vger.kernel.org>; Wed, 10 Mar 2010 14:52:30 +0100 (CET)
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi *,

in qemu-kvm/hw/device-assignment.c assigned_device_pci_cap_init()
appearently only PCI_CAP_ID_MSI and PCI_CAP_ID_MSIX are exposed
to the guest.

Linux Broadcom bnx2 and tg3 drivers expect PCI_CAP_ID_PM to be present.

Are there any plans to implement this and possibly other PCI capability
features for assigned devices?

If not, is there a list of network cards known to work with PCI
assignment in KVM?

Best Regards,

  Sebastian