Hi Elena/Boris: Actually, I forgot I had already made and tested AMD SVM and other changes for domU support, please find the patches.
So the only thing remaining for AMD would be iommu support and SVM vmexit for CR reads and writes which currently calls handle_mmio (which patch #3 attempted, but improperly). I believe Jan or Roger is already looking into that path, so you could start down the iommu path... the last I remember was : (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x99, fault address = 0xffffffc0, flags = 0 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x91, fault address = 0xffffffc0, flags = 0 (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x90, fault address = 0xffffffc0, flags = 0 (XEN) Xen call trace: (XEN) [<ffff82d08014d600>] parse_event_log_entry+0/0x140 (XEN) [<ffff82d08014dfdf>] iommu_read_log.constprop.6+0x8f/0x100 (XEN) [<ffff82d08014e165>] do_amd_iommu_irq+0x115/0x1f0 (XEN) [<ffff82d0801296d0>] do_tasklet_work+0x60/0xa0 (XEN) [<ffff82d080129750>] tasklet_softirq_action+0x40/0x70 (XEN) [<ffff82d080126ee5>] __do_softirq+0x65/0xa0 (XEN) [<ffff82d0802abe68>] _setup_hwdom_pci_devices+0xa8/0x190 (XEN) [<ffff82d0802abdc0>] _setup_hwdom_pci_devices+0/0x190 (XEN) [<ffff82d0801435cb>] pci_segments_iterate+0x2b/0x70 (XEN) [<ffff82d0802ac2e8>] setup_hwdom_pci_devices+0x28/0x40 (XEN) [<ffff82d0802aee00>] amd_iommu_setup_hwdom_device+0/0xc0 (XEN) [<ffff82d0802cbfab>] construct_dom0+0x247b/0x3390 (XEN) [<ffff82d0802bb810>] bootstrap_map+0/0x10c (XEN) [<ffff82d0802bf136>] __start_xen+0x35a6/0x3aa0 (XEN) [<ffff82d080100067>] __high_start+0x53/0x5c Thanks, Mukesh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
