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-ia64-devel

Re: [Xen-ia64-devel] [patch 04/16] IA64 Kexec/kdump

To: Alex Williamson <alex.williamson@xxxxxx>
Subject: Re: [Xen-ia64-devel] [patch 04/16] IA64 Kexec/kdump
From: Horms <horms@xxxxxxxxxxxx>
Date: Thu, 20 Sep 2007 13:46:19 +0900
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 19 Sep 2007 23:53:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1189633099.6287.30.camel@lappy>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070912082834.175658477@xxxxxxxxxxxx> <20070912083044.397222326@xxxxxxxxxxxx> <1189633099.6287.30.camel@lappy>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: mutt-ng/devel-r804 (Debian)
On Wed, Sep 12, 2007 at 03:38:19PM -0600, Alex Williamson wrote:
> On Wed, 2007-09-12 at 17:28 +0900, Simon Horman wrote:
> > plain text document attachment (ia64-kexec.patch)
> 
> > Changes and updates.
> > 
> > 1. Remove fake rendz path and related code according to discuss with Khalid 
> > Aziz.
> > 2. fc.i offset fix in relocate_kernel.S.
> > 3. iospic shutdown code eoi and mask race fix from Fujitsu.
> > 4. Warm boot hook in machine_kexec to SN SAL code from Jack Steiner.
> > 5. Send slave to SAL slave loop patch from Jay Lan.
> > 6. Kdump on non-recoverable MCA event patch from Jay Lan
> > 7. Use CTL_UNNUMBERED in kdump_on_init sysctl.
> > 
> 
>    Couple general issues:
> 
>       * This would be easier to consume as two patches.  One as a port
>         of the upstream patch, the second with the xen-ification.
>       * Tabs and spaces are mixed in this patch.  As a linux patch, this
>         should use only tab indenting.  kdump_find_rsvd_region() has a
>         particularly odd style.

I believe that most of the bizzare indentation just reflects the
state of the code in Linux, but I'll double check to make sure
that I'm not adding additional weirdness.

I'll try splitting the patch as you suggest. This should make it obvious
what is coming straight from Linux, and what crazy things have been
added by my hand.

> 
> And a specific one below...
>  
> > +#ifdef CONFIG_KEXEC
> > +   /* crashkernel=size@offset specifies the size to reserve for a crash
> > +    * kernel.(offset is ingored for keep compatibility with other archs)
> > +    * By reserving this memory we guarantee that linux never set's it
> > +    * up as a DMA target.Useful for holding code to do something
> > +    * appropriate after a kernel panic.
> > +    */
> > +   {
> > +           char *from = strstr(saved_command_line, "crashkernel=");
> > +#ifndef CONFIG_XEN
> > +           unsigned long base, size;
> > +           if (from) {
> > +                   size = memparse(from + 12, &from);
> > +                   if (size) {
> > +                           sort_regions(rsvd_region, n);
> > +                           base = kdump_find_rsvd_region(size,
> > +                           rsvd_region, n);
> > +                           if (base != ~0UL) {
> > +                                   rsvd_region[n].start =
> > +                                           (unsigned long)__va(base);
> > +                                   rsvd_region[n].end =
> > +                                           (unsigned long)__va(base + 
> > size);
> > +                                   n++;
> > +                                   crashk_res.start = base;
> > +                                   crashk_res.end = base + size - 1;
> > +                           }
> > +                   }
> > +           }
> > +#else /* CONFIG_XEN */
> > +           if (from)
> > +                   printk("Ignoring crashkernel command line, "
> > +                          "parameter will be supplied by xen\n");
> > +           xen_machine_kexec_setup_resources();
> > +#endif /* CONFIG_XEN */
> 
>    This doesn't look transparent paravirtualization safe.  I'll note
> this in a few other places too, but I'm sure I've missed some.  A
> CONFIG_XEN kernel should be able to boot on bare metal too.  Thanks,

I wasn't aware of that, I'll try and fix it up and also look for other
problem areas elsewhere.

-- 
Horms
  H: http://www.vergenet.net/~horms/
  W: http://www.valinux.co.jp/en/


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