Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[block]: remove the old blktap1 disk pausing infrastructure
When the upgrade to blktap2 happened, we never had a chance to remove the unused code. This change: * simplifies the udev block handling, removing dependencies on blktap2.py * simplifies the migration code, which nolonger needs to worry about blktap1 backends being paused * removes complicated synchronisation logic needed by the old pause/unpause API * removes a very slow test from quicktest (the VBD pause/unpause one) * unifies PV and HVM codepaths in checkpoint, for increased reliability (HVM guests and PV guests both use the slow resume) Note in the blktap2 universe, the SM backend operations (eg vdi_snapshot) manipulate the tapdisks directly (via tap-ctl invocations). This complexity was only needed because blktap1 lacked such a direct interface. Signed-off-by: David Scott <dave.scott@eu.citrix.com>
- Loading branch information
David Scott
committed
Nov 30, 2011
1 parent
0bb53c6
commit be796c8
Showing
12 changed files
with
76 additions
and
469 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.