From: Matt Mackall <mpm@selenic.com>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Jeff Moyer <jmoyer@redhat.com>,
linux-kernel@vger.kernel.org, Stelian Pop <stelian@popies.net>,
jgarzik@pobox.com
Subject: Re: [patch] fix netconsole hang with alt-sysrq-t
Date: Thu, 12 Aug 2004 19:21:22 -0500 [thread overview]
Message-ID: <20040813002122.GG16310@waste.org> (raw)
In-Reply-To: <20040812213936.GC17907@granada.merseine.nu>
On Fri, Aug 13, 2004 at 12:39:36AM +0300, Muli Ben-Yehuda wrote:
> On Thu, Aug 12, 2004 at 05:32:21PM -0400, Jeff Moyer wrote:
> > ==> Regarding Re: [patch] fix netconsole hang with alt-sysrq-t; Muli Ben-Yehuda <mulix@mulix.org> adds:
> >
> > mulix> On Thu, Aug 12, 2004 at 05:01:18PM -0400, Jeff Moyer wrote:
> > >> So how do you want to deal with this case? We could do something like:
> > >>
> > >> int cpu = smp_processor_id();
> >
> > mulix> That doesn't look right, unless I'm missing something, you could get
> > mulix> preempted here (between the smp_processor_id() and the
> > mulix> local_irq_save() and end up with 'cpu' pointing to the wrong CPU.
> >
> > Would a preempt_disable() be too hideous? Other suggestions?
>
> Maybe, but we could hide it in get_cpu() / put_cpu() ;-)
Yes, let's. I'll have to think about this general approach a bit more though.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-08-13 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 19:29 [patch] fix netconsole hang with alt-sysrq-t Jeff Moyer
2004-08-06 19:52 ` Matt Mackall
2004-08-06 20:01 ` Jeff Moyer
2004-08-06 20:26 ` Matt Mackall
2004-08-12 21:01 ` Jeff Moyer
2004-08-12 21:18 ` Muli Ben-Yehuda
2004-08-12 21:32 ` Jeff Moyer
2004-08-12 21:39 ` Muli Ben-Yehuda
2004-08-13 0:21 ` Matt Mackall [this message]
2004-08-13 0:29 ` Matt Mackall
2004-08-16 18:41 ` Jeff Moyer
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=20040813002122.GG16310@waste.org \
--to=mpm@selenic.com \
--cc=jgarzik@pobox.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=stelian@popies.net \
/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.