From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net,
ehabkost@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [v8][RESEND][PATCH 09/10] xen, gfx passthrough: register host bridge specific to passthrough
Date: Fri, 03 Jul 2015 11:11:13 +0800 [thread overview]
Message-ID: <5595FD51.8080902@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1507011656400.17378@kaball.uk.xensource.com>
>> #ifdef CONFIG_XEN
>> +static void igd_passthrough_pc_init_pci(MachineState *machine)
>> +{
>> + pc_init1(machine,
>> + TYPE_I440FX_PCI_HOST_BRIDGE,
>> + TYPE_IGD_PASSTHROUGH_I440FX_PCI_DEVICE);
>> +}
>> +
>> +static void pc_init_pci(MachineState *machine)
>> +{
>> + pc_init1(machine,
>> + TYPE_I440FX_PCI_HOST_BRIDGE,
>> + TYPE_I440FX_PCI_DEVICE);
>> +}
>> +
>> +static void pc_xen_hvm_init_pci(MachineState *machine)
>> +{
>> + if (has_igd_gfx_passthru)
>> + igd_passthrough_pc_init_pci(machine);
>> + else
>> + pc_init_pci(machine);
>> +}
>
> I don't see any value in introducing pc_init_pci and
> igd_passthrough_pc_init_pci. I would expand both of them here.
>
Agree, and what about this?
static void pc_xen_hvm_init_pci(MachineState *machine)
{
const char *pci_type = has_igd_gfx_passthru ?
TYPE_IGD_PASSTHROUGH_I440FX_PCI_DEVICE :
TYPE_I440FX_PCI_DEVICE;
pc_init1(machine,
TYPE_I440FX_PCI_HOST_BRIDGE,
pci_type);
}
Thanks
Tiejun
next prev parent reply other threads:[~2015-07-03 3:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 8:44 [Qemu-devel] [v8][RESEND][PATCH 00/10] xen: add Intel IGD passthrough Tiejun Chen
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 01/10] i440fx: make types configurable at run-time Tiejun Chen
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 02/10] pc_init1: pass parameters just with types Tiejun Chen
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 03/10] piix: create host bridge to passthrough Tiejun Chen
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 04/10] hw/pci-assign: split pci-assign.c Tiejun Chen
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 05/10] xen, gfx passthrough: basic graphics passthrough support Tiejun Chen
2015-07-01 15:45 ` Stefano Stabellini
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 06/10] xen, gfx passthrough: retrieve VGA BIOS to work Tiejun Chen
2015-07-01 15:51 ` Stefano Stabellini
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 07/10] igd gfx passthrough: create a isa bridge Tiejun Chen
2015-06-05 8:44 ` [Qemu-devel] [v8][RESEND][PATCH 08/10] xen, gfx passthrough: register " Tiejun Chen
2015-07-01 15:55 ` Stefano Stabellini
2015-07-03 1:51 ` Chen, Tiejun
2015-06-05 8:45 ` [Qemu-devel] [v8][RESEND][PATCH 09/10] xen, gfx passthrough: register host bridge specific to passthrough Tiejun Chen
2015-07-01 15:58 ` Stefano Stabellini
2015-07-03 3:11 ` Chen, Tiejun [this message]
2015-06-05 8:45 ` [Qemu-devel] [v8][RESEND][PATCH 10/10] xen, gfx passthrough: add opregion mapping Tiejun Chen
2015-07-01 16:01 ` Stefano Stabellini
2015-07-01 1:39 ` [Qemu-devel] [v8][RESEND][PATCH 00/10] xen: add Intel IGD passthrough Chen, Tiejun
2015-07-01 16:03 ` Stefano Stabellini
2015-07-03 3:17 ` Chen, Tiejun
2015-07-02 6:22 ` 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=5595FD51.8080902@intel.com \
--to=tiejun.chen@intel.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).