From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: ehabkost@redhat.com, stefano.stabellini@eu.citrix.com,
mst@redhat.com, "Kay, Allen M" <allen.m.kay@intel.com>,
qemu-devel@nongnu.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [v10][PATCH 03/10] piix: create host bridge to passthrough
Date: Tue, 9 Feb 2016 18:56:59 +0100 [thread overview]
Message-ID: <56BA286B.2050603@redhat.com> (raw)
In-Reply-To: <20160209104332.775b88f8@t450s.home>
On 09/02/2016 18:43, Alex Williamson wrote:
> Tiejun's email bounced, so adding Allen for comment. Host bridge
> registers 52h, a4h, and a8h seem to be for versions of IGD prior to
> SandyBridge or just wrong. Even the GMCH (50h) doesn't seem to be
> necessary for the VM host bridge, so I'm thinking about dropping all of
> these for vfio-based IGD assignment. Do we know which guest drivers
> have specific dependencies on which host bridge and LPC bridge
> registers? It would even be nice to document the standard
> registers for future maintainability. Thanks,
I remember asking Tiejun for the same, but that was a year ago or more. :(
Paolo
next prev parent reply other threads:[~2016-02-09 17:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 5:37 [Qemu-devel] [v10][PATCH 00/10] xen: add Intel IGD passthrough Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 01/10] i440fx: make types configurable at run-time Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 02/10] pc_init1: pass parameters just with types Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 03/10] piix: create host bridge to passthrough Tiejun Chen
2016-02-09 3:32 ` Alex Williamson
2016-02-09 17:43 ` Alex Williamson
2016-02-09 17:56 ` Paolo Bonzini [this message]
2016-02-09 19:47 ` Kay, Allen M
2016-02-09 21:32 ` Alex Williamson
2016-02-10 3:40 ` Kay, Allen M
2016-02-10 6:00 ` Alex Williamson
2016-02-11 2:25 ` Kay, Allen M
2016-02-11 6:07 ` Alex Williamson
2016-02-15 11:28 ` Gerd Hoffmann
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 04/10] hw/pci-assign: split pci-assign.c Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 05/10] xen, gfx passthrough: basic graphics passthrough support Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 06/10] xen, gfx passthrough: retrieve VGA BIOS to work Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 07/10] igd gfx passthrough: create a isa bridge Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 08/10] xen, gfx passthrough: register " Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 09/10] xen, gfx passthrough: register host bridge specific to passthrough Tiejun Chen
2015-07-15 5:37 ` [Qemu-devel] [v10][PATCH 10/10] xen, gfx passthrough: add opregion mapping Tiejun Chen
2015-07-15 11:46 ` [Qemu-devel] [v10][PATCH 00/10] xen: add Intel IGD passthrough Stefano Stabellini
2015-07-15 12:01 ` Michael S. Tsirkin
2015-07-15 12:38 ` Stefano Stabellini
2015-07-15 13:27 ` 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=56BA286B.2050603@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefano.stabellini@eu.citrix.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).