From: Tiejun Chen <tiejun.chen@intel.com>
To: mst@redhat.com
Cc: xen-devel@lists.xensource.com, allen.m.kay@intel.com,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/2] hw:xen:xen_pt: register isa bridge specific to IGD passthrough
Date: Thu, 21 Aug 2014 09:28:27 +0800 [thread overview]
Message-ID: <1408584508-5946-2-git-send-email-tiejun.chen@intel.com> (raw)
In-Reply-To: <1408584508-5946-1-git-send-email-tiejun.chen@intel.com>
We need this instance to passthrough some config fields of PCH.
Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
---
hw/xen/xen_pt.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
index c1bf357..bf72719 100644
--- a/hw/xen/xen_pt.c
+++ b/hw/xen/xen_pt.c
@@ -829,3 +829,24 @@ static void xen_pci_passthrough_register_types(void)
}
type_init(xen_pci_passthrough_register_types)
+
+static void xen_igd_passthrough_isa_bridge_class_init(ObjectClass *klass,
+ void *data)
+{
+ PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
+
+ k->class_id = PCI_CLASS_BRIDGE_ISA;
+};
+
+static TypeInfo xen_igd_passthrough_isa_bridge_info = {
+ .name = "xen-igd-passthrough-isa-bridge",
+ .parent = TYPE_PCI_DEVICE,
+ .class_init = xen_igd_passthrough_isa_bridge_class_init,
+};
+
+static void xen_igd_passthrough_isa_bridge_register_types(void)
+{
+ type_register_static(&xen_igd_passthrough_isa_bridge_info);
+}
+
+type_init(xen_igd_passthrough_isa_bridge_register_types);
--
1.9.1
next prev parent reply other threads:[~2014-08-21 1:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 1:28 [Qemu-devel] [PATCH 0/2] qemu:xen: implement isa bridge specific to IGD passthrough Tiejun Chen
2014-08-21 1:28 ` Tiejun Chen [this message]
2014-08-21 1:28 ` [Qemu-devel] [PATCH 2/2] xen:i386:pc_piix: create " Tiejun Chen
2014-08-21 16:16 ` [Qemu-devel] [Xen-devel] " Konrad Rzeszutek Wilk
2014-08-22 1:06 ` Chen, Tiejun
2014-08-24 11:12 ` Michael S. Tsirkin
2014-08-25 5:18 ` Chen, Tiejun
2014-08-26 2:49 ` Chen, Tiejun
2014-08-28 0:56 ` Chen, Tiejun
2014-08-29 1:28 ` Chen, Tiejun
2014-08-31 8:58 ` Michael S. Tsirkin
2014-09-01 2:50 ` Chen, Tiejun
2014-09-01 6:05 ` Michael S. Tsirkin
2014-09-01 7:49 ` Chen, Tiejun
2014-09-03 1:40 ` Kay, Allen M
2014-09-03 6:27 ` Michael S. Tsirkin
2014-09-03 15:06 ` Kay, Allen M
2014-09-28 2:59 ` Chen, Tiejun
2014-09-28 5:38 ` Chen, Tiejun
2014-10-07 7:27 ` Michael S. Tsirkin
2014-10-09 2:16 ` Chen, Tiejun
2014-09-29 10:01 ` Michael S. Tsirkin
2014-09-30 2:43 ` Chen, Tiejun
2014-10-07 1:02 ` Chen, Tiejun
2014-10-07 7:26 ` Michael S. Tsirkin
2014-10-09 5:53 ` Chen, Tiejun
2014-10-12 9:50 ` Michael S. Tsirkin
2014-10-24 7:36 ` Chen, Tiejun
2014-10-24 13:47 ` Michael S. Tsirkin
2014-10-30 7:47 ` Chen, Tiejun
2014-11-03 7:48 ` Chen, Tiejun
2014-11-03 11:35 ` Paolo Bonzini
2014-11-03 11:36 ` Chen, Tiejun
2014-11-03 11:47 ` Chen, Tiejun
2014-11-03 12:01 ` Paolo Bonzini
2014-11-03 13:10 ` Michael S. Tsirkin
2014-11-05 7:23 ` Chen, Tiejun
2014-08-22 18:23 ` [Qemu-devel] " Michael S. Tsirkin
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=1408584508-5946-2-git-send-email-tiejun.chen@intel.com \
--to=tiejun.chen@intel.com \
--cc=allen.m.kay@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).