All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: convert to asm-generic/hardirq.h
Date: Thu, 17 Dec 2009 17:26:09 +0900	[thread overview]
Message-ID: <20091217082609.GC20425@linux-sh.org> (raw)
In-Reply-To: <20091217081916.GA11850@lst.de>

On Thu, Dec 17, 2009 at 09:19:16AM +0100, Christoph Hellwig wrote:
> On Thu, Dec 17, 2009 at 05:15:54PM +0900, Paul Mundt wrote:
> > On Thu, Dec 17, 2009 at 09:10:48AM +0100, Christoph Hellwig wrote:
> > > On Wed, Aug 05, 2009 at 04:18:28PM +0900, Paul Mundt wrote:
> > > > On Tue, Aug 04, 2009 at 04:55:29PM +0200, Christoph Hellwig wrote:
> > > > > 
> > > > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > > > 
> > > > Applied, thanks.
> > > 
> > > Did this cause problems in the end?  Still doesn't seem to be in Linus'
> > > tree.
> > 
> > Nope, it was in Linus' tree for awhile, but then I needed to add an
> > nmi_count and had to switch back to an arch-specific one.
> 
> Is there a good reason to overload the irq_cpustat with that?  It seems
> like a quite horrible way to duplicate per-cpu data in a less efficient
> way.

I suppose not, but there didn't seem like a lot of good alternatives
either. Shoving it in irq_cpustat is what is presently done by at least
mn10300, x86, and xtensa. sparc chose stashing it in its cpuinfo struct,
but then also has a meaningful per-cpu storage area. If you have any
better ideas I'll certainly consider moving it.

      reply	other threads:[~2009-12-17  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 14:55 [PATCH] sh: convert to asm-generic/hardirq.h Christoph Hellwig
2009-08-05  7:18 ` Paul Mundt
2009-12-17  8:10   ` Christoph Hellwig
2009-12-17  8:15     ` Paul Mundt
2009-12-17  8:19       ` Christoph Hellwig
2009-12-17  8:26         ` Paul Mundt [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=20091217082609.GC20425@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.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 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.