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

[Xen-devel] [PATCH 0/3] MSI-X adjustments

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 0/3] MSI-X adjustments
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Mon, 12 Jul 2010 10:32:39 +0100
Delivery-date: Mon, 12 Jul 2010 02:33:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
While putting together a prototype patch to address the security issues
connected to granting guests write access to MSI-X table and pending
bit array I cam across a few other MSI-X related issues. Since I don't
have any MSI-X capable devices (or drivers thereof), I can't really test
those changes, so review of the changes before applying is required.

1) prevent simultaneous use of MSI and MSI-X
2) allow the MSI-X table to reside beyond 4G even on 32-bit systems
3) consolidate MSI-X related definitions

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH 0/3] MSI-X adjustments, Jan Beulich <=