qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tiejun Chen <tiejun.chen@intel.com>
To: aliguori@amazon.com, mst@redhat.com, lcapitulino@redhat.com,
	lersek@redhat.com, eblake@redhat.com, alex.williamson@redhat.com,
	pbonzini@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/1] qemu:pci-assign: try to pci-assign.c
Date: Wed, 27 Aug 2014 17:13:06 +0800	[thread overview]
Message-ID: <1409130787-625-1-git-send-email-tiejun.chen@intel.com> (raw)

As you know I'm working on supporting IGD passthrough.

Here we need load VGABIOS to work out IGD case. Obviously something may
be duplicated to kvm codes, we should unify some codes but looks its not
easy to finish that in short time. So as Michael suggestion, at least
we'd better split assigned_dev_load_option_rom to reuse on both kvm
and xen.

I don't finish all IGD stuff patches but here I'd like to post
some related codes to show how to use assigned_dev_load_option_rom()
lately.

+static int get_vgabios(XenPCIPassthroughState *s, void *ptr,
+                       XenHostPCIDevice *dev)
+{
+    int size = 0;
+
+    size = dev_load_option_rom(&s->dev, OBJECT(dev), ptr, dev->domain,
+                               dev->bus, dev->dev, dev->func);
+
+    return size;
+}
+
+int xen_pt_setup_vga(XenPCIPassthroughState *s, XenHostPCIDevice *dev)
+{
+    void *bios = NULL;
+    int bios_size = 0;
+    int rc = 0;
+
+    if (!is_vga_passthrough(dev)) {
+        return rc;
+    }
+
+    bios_size = get_vgabios(s, bios, dev);
+    if (!bios || !bios_size) {
+        XEN_PT_ERR(NULL, "VGA: getting VBIOS!\n");
+        rc = -1;
+        goto out;
+    }
...

----------------------------------------------------------------
Tiejun Chen (1):
      hw/pci-assign: split pci-assign.c

 hw/i386/kvm/pci-assign.c    | 170 +++--------------------------------------------------------------------------------------------------------------------------------------
 include/hw/pci/pci_assign.h | 204 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 207 insertions(+), 167 deletions(-)
 create mode 100644 include/hw/pci/pci_assign.h

Thanks
Tiejun

             reply	other threads:[~2014-08-27  9:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  9:13 Tiejun Chen [this message]
2014-08-27  9:13 ` [Qemu-devel] [PATCH 1/1] hw/pci-assign: split pci-assign.c Tiejun Chen
2014-08-27 13:03   ` Michael S. Tsirkin
2014-08-28  1:44     ` Chen, Tiejun
2014-08-29  1:23       ` Chen, Tiejun
2014-08-31  8:48         ` Michael S. Tsirkin
2014-09-01  2:08           ` Chen, Tiejun
2014-09-01  6:44             ` Michael S. Tsirkin
2014-08-27  9:29 ` [Qemu-devel] [PATCH 0/1] qemu:pci-assign: try to pci-assign.c Laszlo Ersek
2014-08-27  9:34   ` Chen, Tiejun
2014-08-27  9:39     ` Laszlo Ersek
2014-08-27  9:41       ` Chen, Tiejun
  -- strict thread matches above, loose matches on Subject: below --
2014-09-01  2:07 Tiejun Chen

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=1409130787-625-1-git-send-email-tiejun.chen@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=eblake@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=lersek@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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).