| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 28 Nov 2012 12:17:30 -0800 From: "K. Y. Srinivasan" <kys@...rosoft.com> To: gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org, devel@...uxdriverproject.org Subject: drivres/hv Greg, 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. Regards, K. Y -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists