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

[Xen-devel] Prevent guest OSes from accessing paricular memory locations


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: limp <johnkyr83@xxxxxxxxxxx>
  • Date: Sat, 16 Oct 2010 15:55:37 +0100
  • Delivery-date: Sat, 16 Oct 2010 07:56:36 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: ActtQjGTW6guPDLgSwCONj5WtT/CFg==

Hi all,

 

This is my first post on the list so please bare with me!

 

I would like to use Xen hypervisor for running a Linux guest but I want to prohibit Linux from accessing (i.e. writing to) some physical memory locations in which registers of some x86 peripherals are located in. For instance, I would like to prevent Linux (not only the Linux kernel code but anyone who tries to access these I/O ports and memory mapped registers by e.g. writing a kernel module, etc.) from accessing I/O ports 3F8h – 3FFh (serial port 1) and HPET memory mapped registers at 0xFED00000 - 0xFED003FF.

 

Is it possible Xen to redirect these accesses to a printf displaying for instance a message saying “The access to this memory location is not allowed” or just ignore them?

 

Please have a look at http://img209.imageshack.us/img209/4431/linuxmoduleaccessesproh.gif for a graphical overview of what I want to achieve.

 

Any help will be much appreciated.

 

Kind Regards,

 

Ioannis.

 

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