From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] cpu_user_regs * to __smp_call_function_interrupt
Date: Wed, 17 Jun 2009 14:58:11 -0700 [thread overview]
Message-ID: <4A3966F3.9040904@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 130 bytes --]
Hi,
Following simple and tiny patch will help prevent many un-necessary ifdef's in
kdb, if you'll please apply.
Thanks,
Mukesh
[-- Attachment #2: patch.out --]
[-- Type: text/plain, Size: 1114 bytes --]
diff -r 55ca7ef865b4 xen/arch/x86/smp.c
--- a/xen/arch/x86/smp.c Tue Jun 16 11:01:17 2009 +0100
+++ b/xen/arch/x86/smp.c Wed Jun 17 14:55:16 2009 -0700
@@ -223,7 +223,7 @@
* Structure and data for smp_call_function()/on_selected_cpus().
*/
-static void __smp_call_function_interrupt(void);
+static void __smp_call_function_interrupt(struct cpu_user_regs *);
static DEFINE_SPINLOCK(call_lock);
static struct call_data_struct {
void (*func) (void *info);
@@ -273,7 +273,7 @@
if ( cpu_isset(smp_processor_id(), call_data.selected) )
{
local_irq_disable();
- __smp_call_function_interrupt();
+ __smp_call_function_interrupt(NULL);
local_irq_enable();
}
@@ -341,7 +341,7 @@
perfc_incr(ipis);
}
-static void __smp_call_function_interrupt(void)
+static void __smp_call_function_interrupt(struct cpu_user_regs *regs)
{
void (*func)(void *info) = call_data.func;
void *info = call_data.info;
@@ -371,5 +371,5 @@
{
ack_APIC_irq();
perfc_incr(ipis);
- __smp_call_function_interrupt();
+ __smp_call_function_interrupt(regs);
}
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2009-06-17 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 21:58 Mukesh Rathor [this message]
2009-06-18 7:34 ` [PATCH] cpu_user_regs * to __smp_call_function_interrupt Keir Fraser
2009-06-19 1:30 ` Mukesh Rathor
2009-06-19 7:28 ` Keir Fraser
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=4A3966F3.9040904@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=xen-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.