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

RE: [Xen-devel] EPS Signature


  • To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>, "Xen devel list" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx>
  • Date: Sat, 10 Feb 2007 17:33:03 -0800
  • Delivery-date: Sat, 10 Feb 2007 17:34:41 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdG/Nc6FhN5E7LwEduJCgAX8io7RQAASYugAHRDoLABK2G7Pw==
  • Thread-topic: [Xen-devel] EPS Signature


I get following Error..

496: error: `isa_virt_to_bus_is_UNSUPPORTED' undeclared (first use in this 
function)

Is it truely unsupported or I am missing proper includes..

I suspect later but "UNSUPPORTED" makes me uncomfortable.

Please advise.

-Kaushik



-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx on behalf of Ian Pratt
Sent: Sun 2/4/2007 6:52 PM
To: Kaushik Barde; Xen devel list
Subject: RE: [Xen-devel] EPS Signature 
 
> We want to access the EBDA Entry Point Signature at 40:0E for our
DOM-0
> through a driver,
> We noticed that driver is trying to read from a pseudo physical
location
> and not the physical machine RAM location. Hence it's not getting the
> proper value. But if we have to read from the machine RAM location we
can
> use ( virt_to_bus or bus_to_virt) per dev_list comments.
> 
> But this area is under the control of hypervisor. I do not know if we
can
> ioremap these pages ( those which belong to hypervisor).
> 
> I am trying to see if we can be able to get to the 40:0E address. And
get
> the correct EPS signature

Dom0 already has the bottom 1MB of physical ram mapped. You can use the
poorly named isa_bus_to_virt()

Ian



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


_______________________________________________
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®.