On Wed, Nov 28, 2012 at 12:17:30PM -0800, K. Y. Srinivasan wrote: > > Greg, You are writing the most unhelpful Subject: lines lately, please be more descriptive in the future. > I recently discovered that the Hyper-V host allocates mmio > memory for some synthetic devices like the virtual framebuffer. > We are currently in the process of implementing this virtual > framebuffer device. As part of the offer message from the host > we are given the mmio region size that needs to be allocatted to > the device. I am told in the current implementation of the firmware, > this mmio resource shows up in the PCI space. What is the best way to > allocate this mmio space for this driver. I don't understand, does the guest os think this really is mmio memory and the host just set up up? Or is the memory being used to pass data back and forth? Or something else? And what do you mean "firmware"? That usually means UEFI/BIOS to me, not a hyperv host. And finally, what does the guest os see as far as the PCI resource space shows it? Shouldn't it just think it is a normal PCI device and access it properly that way? thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
