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


[Xen-devel] [PATCH 1/2] linux/x86: Disable all accesses to the local API

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH 1/2] linux/x86: Disable all accesses to the local APIC page
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 27 Jul 2006 16:09:13 +0100
Delivery-date: Thu, 27 Jul 2006 08:08:27 -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
While the original problem that triggered the creation of this patch was in the 
3.0-testing tree (and has not been
applicable to the -unstable one after the introduction of xenoprof), the 
cleanup done here should still be merged to
prevent other similar problems: With all the APIC related definitions left 
intact, there was no way to determine at
build time if there was actually a user of these, and if occasionally a code 
path using these then gets actually run,
the domain would oops at best. Additionally, cleanup like this manages or at 
least helps to eliminate dead code.

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

Attachment: xenlinux-x86-no-lapic.patch
Description: Text document

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH 1/2] linux/x86: Disable all accesses to the local APIC page, Jan Beulich <=