[Xen-changelog] [linux-2.6.18-xen] kexec: add parent to per-cpu regions at setup time.

["Xen patchbot-linux-2.6.18-xen" <patchbot-linux-2.6.18-xen@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1204196022 0
# Node ID 621ce063ad83394b25bb63d1684021cf565a94e1
# Parent  439fda3ac2694639fe160a482150f1016d24f9a4
kexec: add parent to per-cpu regions at setup time.

This is slightly more efficient as xen_machine_kexec_setup_resorces()
is called once (before xen_machine_kexec_register_resources()). While
xen_machine_kexec_register_resources() is called once for each EFI
memory region seen by a domain.

More cosmetic than anything else, but it seems more logical to me.

Signed-off-by: Simon Horman <horms@xxxxxxxxxxxx>
---
 drivers/xen/core/machine_kexec.c |   10 ++++------
 1 files changed, 4 insertions(+), 6 deletions(-)

diff -r 439fda3ac269 -r 621ce063ad83 drivers/xen/core/machine_kexec.c
--- a/drivers/xen/core/machine_kexec.c  Thu Feb 28 10:52:47 2008 +0000
+++ b/drivers/xen/core/machine_kexec.c  Thu Feb 28 10:53:42 2008 +0000
@@ -79,6 +79,10 @@ void __init xen_machine_kexec_setup_reso
        xen_hypervisor_res.end = range.start + range.size - 1;
        xen_hypervisor_res.flags = IORESOURCE_BUSY | IORESOURCE_MEM;
 
+       /* The per-cpu crash note resources belong to the hypervisor resource */
+       for (k = 0; k < xen_max_nr_phys_cpus; k++)
+               request_resource(&xen_hypervisor_res, xen_phys_cpus + k);
+
        /* fill in crashk_res if range is reserved by hypervisor */
 
        memset(&range, 0, sizeof(range));
@@ -106,13 +110,7 @@ void __init xen_machine_kexec_setup_reso
 
 void __init xen_machine_kexec_register_resources(struct resource *res)
 {
-       int k;
-
        request_resource(res, &xen_hypervisor_res);
-
-       for (k = 0; k < xen_max_nr_phys_cpus; k++)
-               request_resource(&xen_hypervisor_res, xen_phys_cpus + k);
-
 }
 
 static void setup_load_arg(xen_kexec_image_t *xki, struct kimage *image)

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