From: Ryan Harper <ryanh@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
David F Barrera <dfbp@us.ibm.com>,
xen-devel@lists.xensource.com
Subject: Re: x86_64 SLES 9 SP2 build break
Date: Fri, 19 Aug 2005 13:26:58 -0500 [thread overview]
Message-ID: <20050819182658.GC5523@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304ED1349@scsmsx402.amr.corp.intel.com>
* Nakajima, Jun <jun.nakajima@intel.com> [2005-08-19 13:12]:
> Ryan Harper wrote:
> > * Nakajima, Jun <jun.nakajima@intel.com> [2005-08-19 12:14]:
> >> Ian Pratt wrote:
> >>>> Fixing this particular one looks easy, but I realized that
> >>>> cpu hotplug suff is missing in x86_64 xenlinux. I'm making a
> >>>> patch for that.
> >>>
> >>> Please co-ordinate with Ryan Harper -- he's already working on this.
> >>>
> >>> Thanks,
> >>> Ian
> >>
> >> Ryan, Hi
> >>
> >> If you are already working on it, I just add the missing
> >> hypercall(s) to fix the build problems (and test reboot things).
> >>
> >> If there is anything that we can help, please let me know. We need
> >> the code ASAP.
> >
> > You need x86_64 to run ASAP, not HOTPLUG_CPU for x86_64 smp, correct?
>
> No, we _do_ need HOTPLUG_CPU for x86_64 smp. The build problem is not a
> big deal.
Ah. OK. I don't think it will be a problem for Xen, but currently in
plain linux-2.6.13-rc6 (which has x86_64 HOTPLUG_CPU support),
support is non-functional, at least on my two-way Opteron box. I can
remove a cpu (echo 0 > /sys/devices/system/cpu/cpu1/online) fine, but
when I try to restore (echo 1), the processor fails to come back. Part
of this is that they are integrating the physical hotplug support which
requires a full reboot of the processor (a second run through
do_boot_cpu()) since it would have been physically removed. I really
wanted to see HOTPLUG_CPU work on plain Linux before bringing the code
into XenLinux, but the issues may be tied up in code that Xen doesn't
need. The hypervisor will have to support physical hotplug before
XenLinux will need it.
There are some other subtle differences in HOTPLUG_CPU in the newer
2.6.13 series for x86_64 compared to the level of HOTPLUG_CPU we have
patched into the 2.6.12 tree.
I'll go ahead and work up a patch that brings in HOTPLUG_CPU for x86_64
and share that so we both can work on getting it working.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2005-08-19 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 18:11 x86_64 SLES 9 SP2 build break Nakajima, Jun
2005-08-19 18:26 ` Ryan Harper [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 20:03 Ian Pratt
2005-08-19 18:41 Nakajima, Jun
2005-08-19 19:30 ` David F Barrera
2005-08-19 20:06 ` David F Barrera
2005-08-19 18:20 Nakajima, Jun
2005-08-19 18:17 Ian Pratt
2005-08-19 17:43 Nakajima, Jun
2005-08-19 17:29 Ian Pratt
2005-08-19 17:13 Nakajima, Jun
2005-08-19 18:07 ` Ryan Harper
2005-08-19 16:43 Ian Pratt
2005-08-19 16:20 Nakajima, Jun
2005-08-19 15:01 David F Barrera
2005-08-19 16:31 ` Steven Smith
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=20050819182658.GC5523@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=dfbp@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.