>>> On 18.02.15 at 01:31, <suravee.suthikulpa...@amd.com> wrote: > On 2/17/2015 4:35 PM, Suravee Suthikulanit wrote: >> Ok, now that I look at the arch/arm/physdev.c, I don't think the code >> for supporting any of the PHYSDEVOP_xxx is there. That's probably why >> Xen complains. In contrast, arch/x86/physdev.c has most PHYSDEVOP_xxx >> already supported. >> >> My question is, are we supposed to be adding code to put the support in >> here? > > My guess is yes, and that would mean we need to enable building > drivers/pci.c when building arm code, which then open up a can of worms > with re-factoring MSI support code from x86 and etc.
As you said later, that's pass-through related, i.e. not immediately needed. Right now - to get rid of those messages - you'd have to simply stub out the respective physdevop-s as much as is necessary to no longer emit log messages and no longer return an error on valid input. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
