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/
Home Products Support Community News


Re: [Xen-devel] Prevent guest OSes from accessing paricular memory locat

To: limp <johnkyr83@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Prevent guest OSes from accessing paricular memory locations
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sat, 16 Oct 2010 20:30:33 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 16 Oct 2010 10:31:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <SNT111-DS215B87F8F3E458DB564A44A7580@xxxxxxx>
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>
References: <SNT111-DS215B87F8F3E458DB564A44A7580@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, Oct 16, 2010 at 03:55:37PM +0100, limp wrote:
>    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
>    [1]http://img209.imageshack.us/img209/4431/linuxmoduleaccessesproh.gif for
>    a graphical overview of what I want to achieve.
>    Any help will be much appreciated.

So I assume you're talking about Linux driver in Xen dom0 ?

How about using Xen hypervisor badpage= boot option to mark
specific memory addresses as bad?

See: http://wiki.xensource.com/xenwiki/XenHypervisorBootOptions

-- Pasi

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>