From: Arun Sharma <arun.sharma@intel.com>
To: Xen-devel@lists.xensource.com
Subject: Re: [PATCH] fix-multiple-vmxon.patch
Date: Wed, 20 Apr 2005 17:59:00 -0700 [thread overview]
Message-ID: <4266FAD4.3020905@intel.com> (raw)
In-Reply-To: <mailman.1114041406.25371@unix-os.sc.intel.com>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
On 4/20/2005 5:01 PM, Arun Sharma wrote:
> --- xen/arch/x86/smpboot.c~fix-multiple-vmxon 2005-04-11 08:52:26.293486000 -0700
> +++ xen-askeshav/arch/x86/smpboot.c 2005-04-11 08:58:58.513486000 -0700
The patch doesn't apply with -p1. The attached patch should be better.
-Arun
[-- Attachment #2: fix-multiple-vmxon.patch --]
[-- Type: text/plain, Size: 638 bytes --]
__vmxon() is called twice for the boot cpu, because identify_cpu() is called
twice. This patch ensures that identify_cpu() and hence __vmxon() is called
exactly once for the boot CPU.
Signed-off-by: Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>
--- a/xen/arch/x86/smpboot.c~fix-multiple-vmxon 2005-04-11 08:52:26.293486000 -0700
+++ b/xen/arch/x86/smpboot.c 2005-04-11 08:58:58.513486000 -0700
@@ -114,7 +114,8 @@ void __init smp_alloc_memory(void)
void __init smp_store_cpu_info(int id)
{
cpu_data[id] = boot_cpu_data;
- identify_cpu(&cpu_data[id]);
+ if (id != 0)
+ identify_cpu(&cpu_data[id]);
}
/*
_
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next parent reply other threads:[~2005-04-21 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1114041406.25371@unix-os.sc.intel.com>
2005-04-21 0:59 ` Arun Sharma [this message]
2005-04-21 0:01 [PATCH] fix-multiple-vmxon.patch Arun Sharma
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=4266FAD4.3020905@intel.com \
--to=arun.sharma@intel.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.