From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: [PATCH 0/3] MSI-X adjustments
Date: Mon, 12 Jul 2010 10:32:39 +0100
Message-ID: <4C3AFD57020000780000AB4A@vpn.id2.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

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@novell.com>