public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "H. Peter Anvin" <hpa@kernel.org>, Dave Jones <davej@redhat.com>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123	send_IPI_mask_bitmask+0xc3/0xe0()
Date: Thu, 21 Aug 2008 23:24:56 -0700	[thread overview]
Message-ID: <48AE5BB8.5080701@zytor.com> (raw)
In-Reply-To: <20080822022841.GG23334@one.firstfloor.org>

Andi Kleen wrote:
>> You may want to see if this patch fixes the problem; it does *NOT* have 
>> the correct error behaviour (some of the intervening layers don't 
>> propagate errors), but it should make the fault go away.
> 
> The alternative would be to just take out those msr_on_cpu() 
> interfaces again. Right now they are useless in the kernel,
> but still cause problems.
> 
> They were only added for OpenVZ's vCPUs which they back then
> promised me would hit mainline soon. But that was some time
> ago and there wasn't much progress on this.
> 
> -Andi

We still need the equivalent functionality, though.  The midlayer 
(msr_on_cpu) may be pointless, but that doesn't change the fact that 
putting this functionality in the lower layer (smp_call_function_single) 
makes more sense.

	-hpa

  reply	other threads:[~2008-08-22  6:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 19:51 latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0() Vegard Nossum
2008-08-20  1:39 ` Andi Kleen
2008-08-20  6:26   ` Vegard Nossum
2008-08-22  0:36     ` Dave Jones
2008-08-22  2:13       ` H. Peter Anvin
2008-08-22  2:28         ` Andi Kleen
2008-08-22  6:24           ` H. Peter Anvin [this message]
2008-08-22  9:35             ` Andi Kleen
2008-08-22 16:41               ` H. Peter Anvin
2008-08-23  6:42                 ` Jeremy Fitzhardinge
2008-08-23  6:44                   ` H. Peter Anvin
2008-08-22 11:13           ` adobriyan
2008-08-24  9:20         ` Vegard Nossum
2008-08-24 16:43           ` H. Peter Anvin
2008-08-24 17:17           ` H. Peter Anvin
2008-08-24 17:22             ` Vegard Nossum
2008-08-24 17:45               ` Vegard Nossum
2008-08-24 17:59                 ` H. Peter Anvin
2008-08-24 18:13                 ` Dave Jones
2008-08-25 18:31                   ` Vegard Nossum
2008-08-25 18:38                     ` Dave Jones
2008-08-25 18:36                   ` Andi Kleen
2008-08-25 18:54                     ` Dave Jones
2008-08-25 19:39                       ` Andi Kleen
2008-08-25 19:50                         ` Dave Jones
2008-08-25 20:36                           ` Andi Kleen
2008-08-25 20:47                             ` Dave Jones
2008-08-25 21:24                               ` Arjan van de Ven
2008-08-25 19:08                     ` H. Peter Anvin
2008-08-25 19:13                       ` Dave Jones

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=48AE5BB8.5080701@zytor.com \
    --to=hpa@zytor.com \
    --cc=andi@firstfloor.org \
    --cc=davej@redhat.com \
    --cc=hpa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vegard.nossum@gmail.com \
    --cc=x86@kernel.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