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

[Xen-devel] can xc_translate_foreign_address() always work for kernel va under x86_64 PV?


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: weiming <zephyr.zhao@xxxxxxxxx>
  • Date: Thu, 20 Mar 2008 08:20:16 -0400
  • Delivery-date: Thu, 20 Mar 2008 05:20:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type; b=MxsMKP22HsQb25T0NkYleidw6JUlrO0g+9+7YhOJXu/FoImzDUCCnDTxQVhpLv6aUdHrcwMNAZo6QaCwxlvmNwLJ8LFSMMPiHaSsSNeV9t6BciDD26r/BhsC3LeUbrrCNe939Tq2koI8f2oQjTndWN4SKc24XoExoMQAtUES2Xc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,
In xc_translate_foreign_address(), the page directory address comes from vcpu's cr3.

when the domains is running a user application, the cr3 should contain the app's page table.

Under x86_64 PV, kernel and user space are both under ring 3 and protection is implemented via page protection, which means app's page table has no kernel space mappings.

So my question is: given a kernel's virtual address, can this function always return a valid mfn?

Thanks,
Weiming
_______________________________________________
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®.