CP-8320: Initial commit for xs64bit

Changes based on sm.hg tip 29f9f9595fb7

Signed-off-by: Chandrika Srinivasan <chandrika.srinivasan@citrix.com>
Reviewed-by: Germano Percossi <germano.percossi@citrix.com>

CONTRIB

@@ -0,0 +1,43 @@
+How to submit changes
+=====================
+
+Please try to follow the guidelines below. They will make things
+easier on the maintainers. Not all of these guidelines matter for every
+trivial patch so apply some common sense.
+
+If you are unsure about something written here, ask on the mailing list
+xen-api@lists.xen.org
+
+0. Before starting a big project, discuss it on the list first :-)
+
+1. Always test your changes, however small, by both targetted
+      manual testing and by running the unit tests.
+
+2. When adding new functionality, include test cases for any
+      * important; or
+      * difficult to manually test; or
+      * easy to break
+      new code.
+
+3. All submissions must be made under the terms of the "Developer's
+      Certificate of Origin" (DCO) and should include a Signed-off-by:
+      line.
+
+4. Make your patch(es) available by creating one or more github pull
+      requests. Each pull request should be separately reviewable and
+      mergable. Only patches which must be committed together should be
+      in the same pull request.
+
+5. Each patch should include a descriptive commit comment that helps
+      understand why the patch is necessary and why it works. This will
+      be used both for initial review and for new people to understand
+      how the code works later.
+
+6. For bonus points, ensure the project still builds in between every
+      patch in a set: this helps hunt down future regressions with 'bisect'.
+
+7. Make sure you have the right to submit any changes you make. If you
+      do changes at work you may find your employer owns the patches
+      instead of you.
+
+

INSTALL

@@ -0,0 +1 @@
+Currently building this package outside of the XenServer build environment is somewhat broken. The goal is to replace it with a simple "make"/"make install" process.

MAINTAINERS

@@ -0,0 +1,7 @@
+Maintainers list
+----------------
+
+* Vineeth Thampi <vineeth.thampi@citrix.com>
+* Germano Percossi <germano.percossi@citrix.com>
+* Thanos Makatos <thanos.makatos@citrix.com>
+* Chandrika Srinivasan <chandrika.srinivasan@citrix.com>

Makefile

@@ -70,9 +70,7 @@ SM_STAMP := $(MY_OBJ_DIR)/.staging_stamp
 
 .PHONY: build
 	make -C dcopy 
-	make -C snapwatchd
 	make -C mpathroot
-	make -C diskdatatest
 
 .PHONY: install
 install: 
@@ -87,8 +85,6 @@ install:
 	for i in $(SM_LIBS); do \
 	  install -m 755 drivers/$$i.py \
 	    $(SM_STAGING)$(SM_DEST); done
-	install -m 755 drivers/mpathHBA \
-	  $(SM_STAGING)$(SM_DEST)
 	for i in $(SM_DRIVERS); do \
 	  install -m 755 drivers/$${i}SR.py \
 	    $(SM_STAGING)$(SM_DEST); done
@@ -120,13 +116,10 @@ install:
 	$(MAKE) -C dcopy install DESTDIR=$(SM_STAGING)
 	$(MAKE) -C snapwatchd install DESTDIR=$(SM_STAGING)
 	$(MAKE) -C mpathroot install DESTDIR=$(SM_STAGING)
-	$(MAKE) -C diskdatatest
 	ln -sf $(SM_DEST)blktap2.py $(SM_STAGING)$(BIN_DEST)/blktap2
 	install -m 755 -d $(SM_STAGING)$(CRON_DEST)
 	install -m 644 $(CRON_JOBS:%=etc/cron.d/%) -t $(SM_STAGING)$(CRON_DEST)
 	ln -sf $(SM_DEST)lcache.py $(SM_STAGING)$(BIN_DEST)tapdisk-cache-stats
-	cp -rf XenCert $(SM_STAGING)$(DEBUG_DEST)
-	cp -rf diskdatatest/diskdatatest $(SM_STAGING)$(DEBUG_DEST)/XenCert/diskdatatest
 
 .PHONY: clean
 clean:

README.md

@@ -0,0 +1,6 @@
+Storage Manager for XenServer
+=============================
+
+This repository contains the code which forms the Storage Management layer for XenSever. It consists of a series of "plug-ins" to xapi (the Xen management layer) which are written primarily in python.
+
+