From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: "Michael S. Tsirkin" <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] [v3][PATCH 3/4] xen:hw:pci-host:piix: create host bridge to passthrough
Date: Wed, 06 Aug 2014 14:22:46 +0800 [thread overview]
Message-ID: <53E1C9B6.7090203@intel.com> (raw)
In-Reply-To: <20140804135020.GC17674@redhat.com>
On 2014/8/4 21:50, Michael S. Tsirkin wrote:
> On Thu, Jul 31, 2014 at 08:09:33PM +0800, Tiejun Chen wrote:
>> Implement a pci host bridge specific to passthrough. Actually
>> this just inherits the standard one.
>>
>> This is based on http://patchwork.ozlabs.org/patch/363810/.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
>> ---
>> hw/pci-host/piix.c | 41 +++++++++++++++++++++++++++++++++++++++++
>> include/hw/i386/pc.h | 2 ++
>> 2 files changed, 43 insertions(+)
>>
>> v3:
>>
>> * Rebase
>>
>> v2:
>>
>> * Just add prefix with XEN_IGD_PASSTHROUGH/xen_igd_passthrough
>>
>> diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
>> index 0cd82b8..26ba1e5 100644
>> --- a/hw/pci-host/piix.c
>> +++ b/hw/pci-host/piix.c
>> @@ -93,6 +93,9 @@ typedef struct PIIX3State {
>> #define I440FX_PCI_DEVICE(obj) \
>> OBJECT_CHECK(PCII440FXState, (obj), TYPE_I440FX_PCI_DEVICE)
>>
>> +#define XEN_IGD_PASSTHROUGH_I440FX_PCI_DEVICE(obj) \
>> + OBJECT_CHECK(PCII440FXState, (obj), TYPE_XEN_IGD_PASSTHROUGH_I440FX_PCI_DEVICE)
>> +
>> struct PCII440FXState {
>> /*< private >*/
>> PCIDevice parent_obj;
>> @@ -303,6 +306,16 @@ static int i440fx_initfn(PCIDevice *dev)
>> return 0;
>> }
>>
>> +static int xen_igd_passthrough_i440fx_initfn(PCIDevice *dev)
>> +{
>> + PCII440FXState *d = XEN_IGD_PASSTHROUGH_I440FX_PCI_DEVICE(dev);
>> +
>> + dev->config[I440FX_SMRAM] = 0x02;
>> +
>> + cpu_smm_register(&i440fx_set_smm, d);
>> + return 0;
>> +}
>> +
>
> This is exactly i440fx_initfn.
> Don't copy and paste code like this, reuse existing functions.
>
We can't reuse i440fx_initfn() simply after we introduce
XEN_IGD_PASSTHROUGH_I440FX_PCI_DEVICE(). But with a further concern I
think we also pass type into I440FX_PCI_DEVIC() to index different
objects here. Please see next version.
Thanks
Tiejun
next prev parent reply other threads:[~2014-08-06 6:22 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 [this message]
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 ` [Qemu-devel] [Xen-devel] [v3][PATCH 0/5] xen: " Chen, Tiejun
2014-08-04 13:51 ` [Qemu-devel] " 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=53E1C9B6.7090203@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).