On Wed, 6 Jan 2010, Simon Horman wrote:
> > BTW: actually I found the pci passthrough code in xend had become very
> > complex and hacky now... Things are easily broken when new changes are
> > made, e.g. Stefano added the pci passthrough support in the stubdomain
> > case and the code broke non-stubdomain case for weeks and the
> > msi-translate is still broken even till now.
>
> Yes, I found that that too. It was very difficult for me to make changes too.
>
Xend is definitely very difficult to work with; hacky code paths
started to appear long ago unfortunately.
Few changes some months ago tried to simplify the code but broke stubdoms
even more.
Then it was very difficult for me to fix stubdoms and at the same time
keep the normal case working.
The whole thing needs to be re-architectured from scratch and that is
what libxenlight is for.
> >
> > It would be really great somebody can help to re-organize/cleanup the
> > code some time. :-)
>
> Is the ocaml replacement for xend still being worked on?
> Refactoring the current (python) code is incredibly painful
> in my experience.
>
Take a look a libxenlight: the idea is to have a common low level
library to take care of these things in the future.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel