All of lore.kernel.org
 help / color / mirror / Atom feed
From: Noboru Iwamatsu <n_iwamatsu@jp.fujitsu.com>
To: james.harper@bendigoit.com.au
Cc: xen-devel@lists.xensource.com
Subject: Re: bug in usbback
Date: Mon, 27 Jul 2009 14:13:17 +0900	[thread overview]
Message-ID: <4A6D376D.6000808@jp.fujitsu.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D016DDE5B@trantor>

Hi,

James Harper wrote:
> Also, a question on behaviour:
> 
> When we receive a reconfigure event, I assume that we should then read
> 'num-ports' and scan through each of the port-n values in xenstore. Is
> there any guarantee that a device hasn't been unplugged and replugged
> from the same port during the reconfiguration window? How should I
> detect such a thing if the value of port-n hasn't changed? Should I then
> probe each device? I'm doing this under Windows which is a bit more
> picky and much less flexible...

"num-ports" is only read in creating the hcd. This value is unchanged
during reconfiguring state.

Reconfiguring is called from usb probe and disconnect callbacks.
So, reconfiguring is called every time unplugging and plugging are
detected.

However, connecting and disconnecting the devices at the same time
or frequent operations were not tested enough.

Do you think it's good idea that the method for the notification
of hotplug is switched from xenbus to RING (like pv network's rx_ring)?

Regards,
Noboru

  reply	other threads:[~2009-07-27  5:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 10:01 bug in usbback James Harper
2009-07-25 10:12 ` Keir Fraser
2009-07-26  1:26   ` James Harper
2009-07-27  5:13     ` Noboru Iwamatsu [this message]
2009-07-27  9:16       ` James Harper
2009-07-28  2:41         ` Noboru Iwamatsu
2009-07-28  4:32           ` James Harper
2009-07-28  9:32             ` Noboru Iwamatsu
2009-07-27  1:18 ` Noboru Iwamatsu
2009-07-27  1:23   ` James Harper

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=4A6D376D.6000808@jp.fujitsu.com \
    --to=n_iwamatsu@jp.fujitsu.com \
    --cc=james.harper@bendigoit.com.au \
    --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.