All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jose Renato Santos <jsantos@hpl.hp.com>
Cc: xen-ia64-devel <xen-ia64-devel@lists.xensource.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: [Xen-changelog] [xen-unstable] Add RCU support to Xen.
Date: Wed, 07 Feb 2007 12:57:27 -0600	[thread overview]
Message-ID: <1170874647.28013.11.camel@basalt> (raw)
In-Reply-To: <200701272100.l0RL0V30031431@xenbits2.xensource.com>

On Sat, 2007-01-27 at 13:00 -0800, Xen patchbot-unstable wrote:

> # HG changeset patch
> # User kaf24@localhost.localdomain
> # Date 1169836476 0
> # Node ID 32fd32bbf78d094e96027e3cea05fcbd92fee7a5
> # Parent  19a600376688577f0692eac022f05bc6df30ce93
> Add RCU support to Xen.

...

> @@ -658,6 +659,8 @@ void __init __start_xen(multiboot_info_t
> 
>      trap_init();
> 
> +    rcu_init();
> +    
>      timer_init();
> 
>      early_time_init();

This patch only added the rcu_init() call for x86. When the call is
omitted (on ia64 and powerpc), do_softirq() crashes trying to call a
null function pointer.

In cases like this where you *know* you're going to break the non-x86
architectures, please email xen-ppc-devel and xen-ia64-devel to let us
know what we'll need to do in the future, rather than force us to
reverse-engineer the crash.

Thanks!

-- 
Hollis Blanchard
IBM Linux Technology Center

           reply	other threads:[~2007-02-07 18:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200701272100.l0RL0V30031431@xenbits2.xensource.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1170874647.28013.11.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=jsantos@hpl.hp.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    --cc=xen-ppc-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.