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 2/2] linux/x86: Disable all accesses to the IO-APIC p

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 2/2] linux/x86: Disable all accesses to the IO-APIC pages
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 27 Jul 2006 16:11:15 +0100
Delivery-date: Thu, 27 Jul 2006 08:10:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Similar to the local APIC changes, the IO-APIC access mechanisms should also be 
restricted to the Xen-specific ones
(other than for the local APIC, where the access mechanisms must be entirely 
suppressed). A nice side effect of this is
that the fixmap area shrinks quite a bit, allowing 32-bits to use a little more 
low memory.

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

Attachment: xenlinux-x86-no-ioapic-base.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH 2/2] linux/x86: Disable all accesses to the IO-APIC pages, Jan Beulich <=