From: ebiederm@xmission.com (Eric W. Biederman)
To: hari@in.ibm.com
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
r3pek@r3pek.homelinux.org, fastboot@lists.osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Re: kexec "problem" [and patch updates]
Date: 07 Mar 2004 17:32:00 -0700 [thread overview]
Message-ID: <m17jxwuqkf.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20040304130310.GA7741@in.ibm.com>
Hariprasad Nellitheertha <hari@in.ibm.com> writes:
> Hello,
>
> I recreated this on a UNI system running an SMP kernel as well.
>
> The problem is because we now initialize cpu_vm_mask for init_mm with
> CPU_MASK_ALL (from 2.6.3 onwards) which makes all bits in cpumask 1.
> Hence BUG_ON(!cpus_equal(cpumask,tmp) fails. The change to set
> cpu_vm_mask to CPU_MASK_ALL was done to remove tlb flush optimizations
> for ppc64. On UNI kernels, CPU_MASK_ALL is 1 and hence the problem
> does not occur.
So the problem is that CPU_MASK_ALL includes cpus that are not currently
online. So it has gone from being wrong by including too few cpus
to being wrong by including too many cpus.
> I made a small patch which fixes this problem. The change is, essentially,
> to use "tmp" instead of "cpumask". This ensures that only the (other) online
> cpus are sent the IPI.
>
> I have done some testing with this patch. Kexec loads fine and I haven't seen
> anything untoward.
>
> Comments please.
Any chance we can fix this right and get a proper value in cpu_vm_mask
for init_mm? All that needs to happen is that each cpu as it is
started up is included in cpu_vm_mask.
The reason kexec sees this is that it is possibly the only generic
modifier of init_mm.
If fixing this needs to be kexec specific we need to simply remove
using init_mm.
Eric
next prev parent reply other threads:[~2004-03-08 4:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 16:03 Latest AIO patchset Suparna Bhattacharya
2004-02-24 11:02 ` kexec "problem" Carlos Silva
2004-02-24 17:10 ` Randy.Dunlap
2004-02-24 17:24 ` Carlos Silva
2004-02-27 0:54 ` kexec "problem" [and patch updates] Randy.Dunlap
2004-02-27 8:00 ` [Fastboot] " Eric W. Biederman
2004-02-27 19:32 ` Randy.Dunlap
2004-02-28 10:41 ` Eric W. Biederman
2004-03-04 13:03 ` Hariprasad Nellitheertha
2004-03-08 0:32 ` Eric W. Biederman [this message]
2004-03-08 18:35 ` Randy.Dunlap
2004-02-25 18:45 ` Latest AIO patchset Hayim Shaul
2004-02-26 0:27 ` Benjamin LaHaise
2004-02-26 13:30 ` Hayim Shaul
2004-02-26 16:45 ` Daniel McNeil
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=m17jxwuqkf.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=hari@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r3pek@r3pek.homelinux.org \
--cc=rddunlap@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®