From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Nick Piggin <npiggin@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/pat] generic-ipi: Allow cpus not yet online to call smp_call_function with irqs disabled
Date: Tue, 25 Aug 2009 10:56:53 -0700 [thread overview]
Message-ID: <1251223013.2612.11.camel@sbs-t61> (raw)
In-Reply-To: <20090825042956.GU25721@wotan.suse.de>
On Mon, 2009-08-24 at 21:29 -0700, Nick Piggin wrote:
> On Mon, Aug 24, 2009 at 01:15:43PM -0700, Suresh B wrote:
> > On Sun, 2009-08-23 at 22:40 -0700, Nick Piggin wrote:
> > > Also, I would say that we should just restrict this to wait==1 case
> > > because in that case the stack can trivially be used for data. In
> > > the wait==0 case, it is more complex. In the current implementation
> > > it should be OK (it uses per-cpu data), but we've used kmalloc
> > > there in the past, which probably wouldn't work either.
> >
> > In future if we add any kmalloc, we already have checks in kmalloc()
> > that can be easily caught. I would like to make this change as generic
> > as possible.
>
> Why? You think there will be much demand for it?
In the current mtrr case, we currently use wait==0
Also unless there are issues, I would like to keep it open. So that it
will encourage more usages and expose any other bugs that we perhaps
overlooked.
With all the recent generic-ipi changes, even for online cpu's, we
should be able to allow smp_call_function() with interrupts disabled for
wait==0 case, right?
thanks,
suresh
prev parent reply other threads:[~2009-08-25 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-269c861baa2fe7c114c3bc7831292758d29eb336@git.kernel.org>
2009-08-24 5:40 ` [tip:x86/pat] generic-ipi: Allow cpus not yet online to call smp_call_function with irqs disabled Nick Piggin
2009-08-24 20:15 ` Suresh Siddha
2009-08-25 4:29 ` Nick Piggin
2009-08-25 17:56 ` Suresh Siddha [this message]
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=1251223013.2612.11.camel@sbs-t61 \
--to=suresh.b.siddha@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=npiggin@suse.de \
--cc=tglx@linutronix.de \
/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