qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Paul Durrant <paul.durrant@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	qemu-devel@nongnu.org, xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [PATCH] Xen PV Device
Date: Thu, 04 Jul 2013 09:15:34 +0200	[thread overview]
Message-ID: <51D52116.8040104@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1307031700290.5067@kaball.uk.xensource.com>

Am 03.07.2013 18:37, schrieb Stefano Stabellini:
> On Wed, 3 Jul 2013, Paul Durrant wrote:
>> This patch introduces a new Xen PV PCI device which will act as a new
>> binding point for PV drivers for Xen.
>> The device has parameterized vendor-id, device-id and revision to allow to
>> be configured as a binding point for any vendor's PV drivers.
>>
>> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
>> Cc: Stefano Stabellini <stefano.stabellini@citrix.com>
>> ---
>>  hw/xen/Makefile.objs     |    1 +
>>  hw/xen/xen_pvdevice.c    |  131 ++++++++++++++++++++++++++++++++++++++++++++++
>>  include/hw/pci/pci_ids.h |    5 +-
>>  trace-events             |    4 ++
>>  4 files changed, 139 insertions(+), 2 deletions(-)
>>  create mode 100644 hw/xen/xen_pvdevice.c
>>
>> diff --git a/hw/xen/Makefile.objs b/hw/xen/Makefile.objs
>> index 2017560..fd88003 100644
>> --- a/hw/xen/Makefile.objs
>> +++ b/hw/xen/Makefile.objs
>> @@ -4,3 +4,4 @@ common-obj-$(CONFIG_XEN_BACKEND) += xen_backend.o xen_devconfig.o
>>  obj-$(CONFIG_XEN_I386) += xen_platform.o xen_apic.o
>>  obj-$(CONFIG_XEN_PCI_PASSTHROUGH) += xen-host-pci-device.o
>>  obj-$(CONFIG_XEN_PCI_PASSTHROUGH) += xen_pt.o xen_pt_config_init.o xen_pt_msi.o
>> +obj-$(CONFIG_XEN) += xen_pvdevice.o
>> diff --git a/hw/xen/xen_pvdevice.c b/hw/xen/xen_pvdevice.c
>> new file mode 100644
>> index 0000000..dbc4bf5
>> --- /dev/null
>> +++ b/hw/xen/xen_pvdevice.c
>> @@ -0,0 +1,131 @@
>> +/* Copyright (c) Citrix Systems Inc.
>> + * All rights reserved.
> 
> Like Anthony wrote before, All rights reserved contradicts what's
> written below.
> Aside from this, it looks OK to me.
> 
> I would like to see the libxl side patch.
> Also it would be nice to have an ack from Andreas or another QOM expert.

>From a QOM view it looks fine now. :) Thanks for inquiring.

Some other comments though:
* Now that it no longer depends on TARGET_PAGE_SIZE, is it possible to
use common-obj-$(CONFIG_XEN)? Then it would build only once rather than
separately for i386 and x86_64 and any future Xen platforms (e.g., arm).
* It looks as if the MMIO functions were renamed - the arguments no
longer align. That could be edited before you apply the patch to your
queue if there's nothing else - then feel free to add my Reviewed-by
independent of the other issue.
* Paolo had asked for new MemoryRegions not to include the device name -
can be renamed once they get the owner field though (not merged yet).
Don't have a better suggestion handy.

Also Paul, by my count this is [PATCH v4] - please use
--subject-prefix="PATCH v5" if you respin and include the change log
either below "---" or in a cover letter. We prefer to see it for patch
review but not in Git commit history.
Similarly, "Introduce a new Xen PV device..." would elegantly avoid
reading "This patch..." after it's been committed. ;)

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-07-04  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 11:19 [Qemu-devel] [PATCH] Xen PV Device Paul Durrant
2013-07-03 16:37 ` Stefano Stabellini
2013-07-04  7:15   ` Andreas Färber [this message]
2013-07-04  8:14     ` Paul Durrant
2013-07-04  8:17   ` Paul Durrant

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=51D52116.8040104@suse.de \
    --to=afaerber@suse.de \
    --cc=paul.durrant@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).