From: "James (song wei)" <jsong@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH] del xend entry when destroy pv usb host controller of a guest os with no pv-frontend driver
Date: Thu, 25 Mar 2010 23:31:29 -0700 (PDT) [thread overview]
Message-ID: <28038630.post@talk.nabble.com> (raw)
delete xend entry when destroying pv usb host controller of a guest os which
has no pv-frontend driver loaded.
-James (Song Wei)
Signed-off-by: James (Song Wei) <jsong@novell.com>
diff -r f42ff98a2cdc tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py Thu Mar 25 09:32:21 2010
+0000
+++ b/tools/python/xen/xend/XendDomainInfo.py Fri Mar 26 13:27:25 2010
+0800
@@ -1305,8 +1305,15 @@
frontpath =
self.getDeviceController(deviceClass).frontendPath(dev)
backpath = xstransact.Read(frontpath, "backend")
thread.start_new_thread(self.getDeviceController(deviceClass).finishDeviceCleanup,
(backpath, path))
-
- rc = self.getDeviceController(deviceClass).destroyDevice(devid,
force)
+ if deviceClass =='vusb':
+ dev =
self.getDeviceController(deviceClass).convertToDeviceNumber(devid)
+ state =
self.getDeviceController(deviceClass).readBackend(dev, 'state')
+ if state == '1':
+ rc =
self.getDeviceController(deviceClass).destroyDevice(devid, True)
+ else:
+ rc =
self.getDeviceController(deviceClass).destroyDevice(devid, force)
+ else:
+ rc =
self.getDeviceController(deviceClass).destroyDevice(devid, force)
if not force and rm_cfg:
# The backend path, other than the device itself,
# has to be passed because its accompanied frontend
http://old.nabble.com/file/p28038630/del_usb_xend_entry.patch
del_usb_xend_entry.patch
--
View this message in context: http://old.nabble.com/-PATCH--del-xend-entry-when-destroy-pv-usb-host-controller-of-a-guest-os-with-no-pv-frontend-driver-tp28038630p28038630.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
reply other threads:[~2010-03-26 6:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=28038630.post@talk.nabble.com \
--to=jsong@novell.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).