qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: mst@redhat.com
Cc: pbonzini@redhat.com, xen-devel@lists.xensource.com,
	qemu-devel@nongnu.org, stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [Xen-devel] [v3][PATCH 0/5] xen: introduce new machine for IGD passthrough
Date: Mon, 04 Aug 2014 13:39:23 +0800	[thread overview]
Message-ID: <53DF1C8B.3030404@intel.com> (raw)
In-Reply-To: <1406808574-19728-1-git-send-email-tiejun.chen@intel.com>

On 2014/7/31 20:09, Tiejun Chen wrote:
> v3:
>
> * Drop patch #4
> * Add one patch #1 from Michael
> * Rebase
>
> v2:
>
> * Fix some coding style
> * New patch to separate i440fx_init
> * Just add prefix with XEN_IGD_PASSTHROUGH/xen_igd_passthrough
> * Based on patch #2 to regenerate
> * Unify prefix with XEN_IGD_PASSTHROUGH/xen_igd_passthrough like patch #3
> * Test: boot with a preinstalled ubuntu 14.04
>    ./i386-softmmu/qemu-system-i386 -hda test.img -m 2560 -boot c -machine pc

In plus, ./i386-softmmu/qemu-system-i386 -hda winxp-32.img -m 2560 -boot 
c -machine pc

Thanks
Tiejun

>
> As we discussed we need to create a separate machine to support current
> IGD passthrough.
>
> ----------------------------------------------------------------
> Tiejun Chen (4):
>        i440fx: make types configurable at run-time
>        hw:i386:pc_piix: split pc_init1()
>        xen:hw:pci-host:piix: create host bridge to passthrough
>        xen:hw:i386:pc_piix: introduce new machine for IGD passthrough
>
>   hw/i386/pc_piix.c    | 227 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------
>   hw/pci-host/piix.c   |  50 ++++++++++++++++++++++++++++++++++----
>   include/hw/i386/pc.h |   8 ++++++-
>   3 files changed, 254 insertions(+), 31 deletions(-)
>
> Thanks
> Tiejun
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

  parent reply	other threads:[~2014-08-04  5:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 12:09 [Qemu-devel] [v3][PATCH 0/5] xen: introduce new machine for IGD passthrough Tiejun Chen
2014-07-31 12:09 ` [Qemu-devel] [v3][PATCH 1/4] i440fx: make types configurable at run-time Tiejun Chen
2014-08-04 13:48   ` Michael S. Tsirkin
2014-08-06  6:18     ` Chen, Tiejun
2014-07-31 12:09 ` [Qemu-devel] [v3][PATCH 2/4] hw:i386:pc_piix: split pc_init1() Tiejun Chen
2014-08-04 13:48   ` Michael S. Tsirkin
2014-08-06  6:19     ` Chen, Tiejun
2014-07-31 12:09 ` [Qemu-devel] [v3][PATCH 3/4] xen:hw:pci-host:piix: create host bridge to passthrough Tiejun Chen
2014-08-04 13:50   ` Michael S. Tsirkin
2014-08-06  6:22     ` Chen, Tiejun
2014-07-31 12:09 ` [Qemu-devel] [v3][PATCH 4/4] xen:hw:i386:pc_piix: introduce new machine for IGD passthrough Tiejun Chen
2014-08-04  5:39 ` Chen, Tiejun [this message]
2014-08-04 13:51 ` [Qemu-devel] [v3][PATCH 0/5] xen: " Michael S. Tsirkin
2014-08-06  6:26   ` Chen, Tiejun

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=53DF1C8B.3030404@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --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).