[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Dom I/O Mappings


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Eric Benton" <benton71@xxxxxxxxx>
  • Date: Mon, 6 Nov 2006 16:57:10 +0200
  • Delivery-date: Mon, 06 Nov 2006 06:57:29 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=fF9EwaHrSaDXxgXKl80LgVD5jl/ar6uz90fY/gCW5wloU2gAvswIK2ZhpJupX/tZQvDIb+NBxrJGMd3BYZ6KxoIuEAPbg1hlSeg9JfwiYH1vBPUb6KPnQ0HJ6Eb267gO9kQXvy0VEkGUGEsl3DmwMG3f7Ls4dDC+1YDEwm/LYo8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I saw that all the I/O regions which are marked as E820_RAM are being mapped to dom_io as writeable pages, I don't know the architecture exactly but I was wondering about these things.

1. How share_xen_page_with_guest() works? does it maps those pages the same pseudo physical addresses or the virtual ones? would you mind to explain like what kind of addresses the e820 contains? are they real machine addresses?

2. What pieces of code are running in the dom_io context? or else, why would we want to map those addresses??

Thanks,
Eric.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.