From: Juergen Gross <jgross@suse.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, stefano.stabellini@eu.citrix.com
Subject: Re: [Patch RFC 1/4] usb: support device specification via <bus>-<port>
Date: Fri, 17 Jul 2015 12:25:39 +0200 [thread overview]
Message-ID: <55A8D823.1050900@suse.com> (raw)
In-Reply-To: <1437128637.3689.34.camel@redhat.com>
On 07/17/2015 12:23 PM, Gerd Hoffmann wrote:
> Hi,
>
>>> device_add monitor command.
>>
>> Okay. I guess the USBDevice for the added device can be obtained
>> in USBPortOps->attach via USBPort->dev ?
>
> Yes.
>
>> Doing a quick search through the sources I couldn't find a way to
>> issue a monitor command from inside qemu. I assume I'd have to use
>> do_device_add() directly?
>
> qdev_device_add() should do it, yes.
> Why do you need to call this from inside qemu?
> Watching on xenbus and responding to new devices created there?
Exactly.
Juergen
next prev parent reply other threads:[~2015-07-17 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:47 [Patch RFC 0/4] usb, xen: add pvUSB backend Juergen Gross
2015-07-16 15:47 ` [Patch RFC 1/4] usb: support device specification via <bus>-<port> Juergen Gross
2015-07-17 6:59 ` Gerd Hoffmann
2015-07-17 7:32 ` Juergen Gross
2015-07-17 8:28 ` Gerd Hoffmann
2015-07-17 10:06 ` Juergen Gross
2015-07-17 10:23 ` Gerd Hoffmann
2015-07-17 10:25 ` Juergen Gross [this message]
2015-07-16 15:47 ` [Patch RFC 2/4] usb: add flag to USBPacket to request complete callback after isoc transfer Juergen Gross
2015-07-17 8:12 ` Gerd Hoffmann
2015-07-17 8:44 ` Juergen Gross
2015-07-17 9:23 ` Gerd Hoffmann
2015-07-17 10:14 ` Juergen Gross
2015-07-16 15:47 ` [Patch RFC 3/4] xen: introduce dummy system device Juergen Gross
2015-07-16 15:47 ` [Patch RFC 4/4] xen: add pvUSB backend Juergen Gross
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=55A8D823.1050900@suse.com \
--to=jgross@suse.com \
--cc=kraxel@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.