All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] unified spinlock
Date: Thu, 20 Jan 2005 16:50:47 +0000	[thread overview]
Message-ID: <20050120165045.GA9097@kroah.com> (raw)
In-Reply-To: <41EFCFDC.4060509@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]

On Thu, Jan 20, 2005 at 07:44:24AM -0800, Randy.Dunlap wrote:
> Matthew Wilcox wrote:
> >I think this is referring to initialisation of spinlocks that are
> >allocated dynamically, not statically.  If a lock validator can't cope
> >with that, it needs to be fixed, IMO.
> >
> Having just looked at the LWN.net article, is this (still) true?
> 
> <quote>
> The stated reasons for this change include consistency and making life 
> easier for automatic lock validators. There is also an unstated, but 
> evident reason: the assignment form of lock initialization gets in the 
> way of the realtime preemption patches. Those patches change most 
> spinlocks in the kernel to a different, mutex type, and that breaks 
> the initializers. As a result, the preemption patches must change all 
> of those initializations throughout the kernel. By putting those 
> specific changes into the mainline, it is possible to make the 
> realtime patches smaller, less intrusive, and a little bit less scary.
> </quote>

Yes, it is.  See the number of patches that have been flowing into the
kernel lately to fix this issue up.

thanks,

greg k-h

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2005-01-20 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 15:35 [KJ] [PATCH] unified spinlock Randy.Dunlap
2005-01-20 15:44 ` Randy.Dunlap
2005-01-20 15:47 ` Matthew Wilcox
2005-01-20 16:50 ` Greg KH [this message]
2005-01-20 20:04 ` Matthew Wilcox
2005-01-20 20:09 ` Greg KH
2005-01-22 18:12 ` Domen Puncer

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=20050120165045.GA9097@kroah.com \
    --to=greg@kroah.com \
    --cc=kernel-janitors@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.