From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH 2/2] xen: add qemu device for each pvusb backend Date: Tue, 27 Sep 2016 11:08:29 +0200 Message-ID: <1474967309.26376.12.camel@redhat.com> References: <1474893837-13010-1-git-send-email-jgross@suse.com> <1474893837-13010-3-git-send-email-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1474893837-13010-3-git-send-email-jgross@suse.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: "Qemu-devel" To: Juergen Gross Cc: anthony.perard@citrix.com, xen-devel@lists.xensource.com, sstabellini@kernel.org, qemu-devel@nongnu.org List-Id: xen-devel@lists.xenproject.org Hi, > struct usbback_info { > struct XenDevice xendev; /* must be first */ > + char id[24]; > + struct USBBACKDevice *dev; > USBBus bus; > void *urb_sring; > void *conn_sring; > @@ -116,6 +124,10 @@ struct usbback_info { > QEMUBH *bh; > }; > =20 > +typedef struct USBBACKDevice { > + DeviceState qdev; > +} USBBACKDevice; Hmm, I think the xen core needs better QOM support ... struct XenDevice should have a DeviceState element, so it can be used as device object directly instead of attaching a device object like this ... cheers, Gerd