[Xen-ia64-devel] Notes about driver domains

[Tristan Gingold <Tristan.Gingold@xxxxxxxx>]

Hi,

I have started to work on driver domains.  Here are a few notes on the issues:

* pci backend compiles without any change (good !)

* pci frontend integration is not easy.  From my understanding, linux/ia64 pci 
code really wants its own 'struct pci_controller', while pcifront.h provides 
its own.  I have slightly changes pcifront.h and pci_op.c to use the ia64 
pci.h  This makes a very few #ifdef __ia64__ (2 in fact).  I don't know how 
to improve this, I am definitly not a linux/ia64-pci expert!

* Memory attributes have to be handled (if you want to avoid mca!).  The 
current method (dom0 uses its attribute, domU always use WB) doesn't work 
anymore.  Xen has to merge domain attributes with MADT attributes.

* Currently any domain can do ioremap.  Access checks have to be done.

* IO port entry should be added in the MADT of every domain.  Access checks 
have to be performed.  I don't know wether we should use a per page control, 
a global control (yes/no) or a per port control (slow!).  Disabled port 
should either crash the domain or be silently rejected.  This issue has 
already been discussed and silent rejection was agreed.

* IRQ should be access controled.

* memory mapped IO pages should belongs to dom_io pseudo-domain.  At least 
work is required here to avoid crash when a domain is destroyed.

* More issues ?

At this time I was able to see an ethernet card in a domU.

Tristan.

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel