On Tue, Jun 28, 2016 at 01:28:55PM +0200, Alexander Gordeev wrote: > On Tue, Jun 28, 2016 at 01:18:15PM +0200, Andrew Jones wrote: > > On Tue, Jun 28, 2016 at 12:54:51PM +0200, Alexander Gordeev wrote: > > > On Mon, Jun 06, 2016 at 07:11:09PM +0200, Andrew Jones wrote: > > > > I'd like to either have this resolved, or at least understood it > > > > before we accept the series. If you drop your pci-testdev > > > > implementation (patch 11/12) into x86/vmexit.c, in order to replace > > > > the implementation there, does pci-testdev still work? I.e. have > > > > you checked if x86 works both with its current implementation and > > > > yours? > > > > > > What if I post for inclusion updated patches 1-10/12 and continue > > > working on barriers/io/pci-testdev? > > > > Hmm.. the only way I can test the early patches without pci-testdev > > is to dump the data structures, but that doesn't really test anything > > other than the DT parsing. I'd rather we wait. > > It also involves what would be PCI configuration space cycles: PCI bus > scanning and PCI devices inquiring and parsing. Not only DT. But how do I know any of that stuff is working? > > > Thanks, > > drew > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
