From: Sheng Yang <sheng@linux.intel.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Anthony Liguori <anthony@codemonkey.ws>,
Sheng Yang <sheng@linux.intel.com>,
Allen Kay <allen.m.kay@intel.com>
Subject: [PATCH 3/7] Figure out device capability
Date: Wed, 11 Feb 2009 16:12:05 +0800 [thread overview]
Message-ID: <1234339929-3345-4-git-send-email-sheng@linux.intel.com> (raw)
In-Reply-To: <1234339929-3345-1-git-send-email-sheng@linux.intel.com>
Try to figure out device capability in update_dev_cap(). Now we are only care
about MSI capability.
The function pci_find_cap_offset original function wrote by Allen for Xen.
Notice the function need root privilege to work. This depends on libpci to work.
Signed-off-by: Allen Kay <allen.m.kay@intel.com>
Signed-off-by: Sheng Yang <sheng@linux.intel.com>
---
qemu/hw/device-assignment.c | 29 +++++++++++++++++++++++++++++
qemu/hw/device-assignment.h | 1 +
2 files changed, 30 insertions(+), 0 deletions(-)
diff --git a/qemu/hw/device-assignment.c b/qemu/hw/device-assignment.c
index f14f971..76369ed 100644
--- a/qemu/hw/device-assignment.c
+++ b/qemu/hw/device-assignment.c
@@ -219,6 +219,35 @@ static void assigned_dev_ioport_map(PCIDevice *pci_dev, int region_num,
(r_dev->v_addrs + region_num));
}
+static uint8_t pci_find_cap_offset(struct pci_dev *pci_dev, uint8_t cap)
+{
+ int id;
+ int max_cap = 48;
+ int pos = PCI_CAPABILITY_LIST;
+ int status;
+
+ status = pci_read_byte(pci_dev, PCI_STATUS);
+ if ((status & PCI_STATUS_CAP_LIST) == 0)
+ return 0;
+
+ while (max_cap--) {
+ pos = pci_read_byte(pci_dev, pos);
+ if (pos < 0x40)
+ break;
+
+ pos &= ~3;
+ id = pci_read_byte(pci_dev, pos + PCI_CAP_LIST_ID);
+
+ if (id == 0xff)
+ break;
+ if (id == cap)
+ return pos;
+
+ pos += PCI_CAP_LIST_NEXT;
+ }
+ return 0;
+}
+
static void assigned_dev_pci_write_config(PCIDevice *d, uint32_t address,
uint32_t val, int len)
{
diff --git a/qemu/hw/device-assignment.h b/qemu/hw/device-assignment.h
index f216bb0..f8b8e65 100644
--- a/qemu/hw/device-assignment.h
+++ b/qemu/hw/device-assignment.h
@@ -29,6 +29,7 @@
#define __DEVICE_ASSIGNMENT_H__
#include <sys/mman.h>
+#include <pci/pci.h>
#include "qemu-common.h"
#include "sys-queue.h"
#include "pci.h"
--
1.5.4.5
next prev parent reply other threads:[~2009-02-11 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 8:12 [PATCH 0/7][v2] Userspace support for MSI enabling Sheng Yang
2009-02-11 8:12 ` [PATCH 1/7] kvm: Replace force type convert with container_of() Sheng Yang
2009-02-11 8:12 ` [PATCH 2/7] Make device assignment depend on libpci Sheng Yang
2009-02-11 8:12 ` Sheng Yang [this message]
2009-02-11 8:12 ` [PATCH 4/7] Support for device capability Sheng Yang
2009-02-11 8:12 ` [PATCH 5/7] kvm: user interface for MSI type irq routing Sheng Yang
2009-02-11 8:12 ` [PATCH 6/7] kvm: libkvm: allocate unused gsi for " Sheng Yang
2009-02-11 8:12 ` [PATCH 7/7] kvm: expose MSI capability to guest Sheng Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1234339929-3345-4-git-send-email-sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=allen.m.kay@intel.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.