WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] asterisk, ztdummy, and usb (and HZ = 100 under xen ???)

To: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] asterisk, ztdummy, and usb (and HZ = 100 under xen ???)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 22 May 2005 08:08:40 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Delivery-date: Sun, 22 May 2005 07:11:08 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D7A0B9D@xxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D7A0B9D@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 22 May 2005, at 03:15, James Harper wrote:

Just on that subject, under what conditions would a domain with
permissions to access a pci device be able to bring down the machine if
I did something stupid in the kernel driver?

Assuming you have restricted the domain to just accessing registers and IRQs belonging to the device it controls, I think the only way would be by programming the device to wreak havoc on its behalf (by DMAing arbitrary memory). It also has control of an interrupt line, so if that is shared it might be possible for the domain to arrange an interrupt storm that either you mask, affecting servicing of other devices on that line, or you end up in interrupt livelock. This could be fixed by masking the interrupt, terminating the domain, clearing the enable bits in the device's PCI space, then unmasking the interrupt. In any case, legacy interrupts are on their way out, replaced with message-based interrupts.

 -- Keir


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