From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Consuming PCI device in PV kernel Date: Fri, 18 Jul 2014 15:09:42 -0400 Message-ID: <20140718190942.GG15947@laptop.dumpdata.com> References: <524794479.20140703121338@gmail.com> <20140703180957.GD13710@konrad-lan.dumpdata.com> <1376452421.20140707092147@gmail.com> <1083121389.20140707122233@gmail.com> <623751089.20140718153713@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <623751089.20140718153713@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Simon Martin Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Fri, Jul 18, 2014 at 03:37:13PM +0100, Simon Martin wrote: > Hello Simon, > > Monday, July 7, 2014, 12:22:33 PM, you wrote: > > > Found the code in mini-os. Implementing now. > > I now have a working implementation of my own pcifront based on the > mini-os implementation, however I can't seem to find any examples or > documentation anywhere on how to discover and map the PCI device into > my PV memory map. Not sure what 'PV memory map' means? You mean the BAR values and such? > > Checking the Linux pcifront driver it seems to be doing IO via the > pciback driver. This won't work in my situation, I need raw access to > the PCI device memory. As in to the configuration registers (which would also have the BAR values)? > > Looking at the GPLPV drivers as well to see if I can decipher from > them how to do this. > > Any suggestions on how to implement direct access to the PCI device? > > -- > Best regards, > Simon mailto:furryfuttock@gmail.com >