WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Accessing PCI BAR space directly from XEN hypervisor

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Accessing PCI BAR space directly from XEN hypervisor
From: veerasena reddy <veeruyours@xxxxxxxxx>
Date: Mon, 13 Jun 2011 14:24:59 +0530
Delivery-date: Mon, 13 Jun 2011 01:57:45 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=yfvFOiCv6x/YPRP0kAX3KOKlqqxV69+uOxLvJNh6oP8=; b=ppOJHkGpKZYkr5NvUzQcJVfFaVGJMV/VRb99fRcGyTzny5IuLWbtnd1GllLmRvl1on MQgqs66IyDV1B96/+CQ/cdsQrq7KGPbULYANjLO+D8ty+KIGkvWl4Rd8c11VZGF65RcY SY/ABXBy7EunHt7mQ8Kq3zon1xPcqzBZU6aXA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CUrXRGo8SM+qWLlRZxUFaz36xYP3vuwAkgakPN47ohfPt3SN2wvikk4Xpex8eDaGRE 3vKiksarG5HWlR+FTniewYVjf0T4sIpGJ9BNW9ZgB6pD7dWXTRasJyAnAS3NwrRYhPlB Z7JWXsKzAGI4a/qkEgJ2a4sLpRtbZntQEPfso=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

I am doing an experiment to see if I can get more throughput by moving the Tx ring update and doorbell ring mechanism to hypervisor and provide a hypercall to HVM Guest. When there is a Tx packet ready, the HVM guest invokes the hypercall along with the packet address as argument. The hypercall function will write the packet address to the Tx ring and rings the doorbell directly without involving dom0.

AS part of this, i need to access IO Memory BAR region of the PCI network device from XEN hypervisor (hypercall handler). For this, i tried converting the BAR Physical address (captured from lspci as shown below) of the PCI device to MFN, but got all F's (invalid entry). Even pfn_valid(0xf0904000) failed on this address. Where as I could successfully map a dom0 page (allocated using vmalloc()) and access in hypervisor using map_domain_page(mfn).

Could any one please suggest how to access the BAR regions of a PCI device from hypervisor? how to do mapping and read/write operations?

Also, Could you please explain the difference between mapping locally allocated pages and PCI BAR memory of dom0 in hypervisor?

Thanks in advance.

Regards,
VSR.
==========================
[root@fc13 xen]# lspci -vvs 09:00.0
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
    Subsystem: Lenovo Device 2131
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 1247
    Region 0: I/O ports at 4000 [size=256]
    Region 2: Memory at f0904000 (64-bit, prefetchable) [size=4K]
    Region 4: Memory at f0900000 (64-bit, prefetchable) [size=16K]
    [virtual] Expansion ROM at f0920000 [disabled] [size=128K]
===========================
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>