Re: [PATCH] lock assertion macros for 2.5.30

From: Rik van Riel (riel@conectiva.com.br)
Date: Thu Aug 08 2002 - 14:00:33 EST

Next message: Petr Vandrovec: "Re: Part 2: Re: [PATCH] pdc20265 problem."
Previous message: Scott Murray: "Re: RFC: PCI hotplug resource reservation"
In reply to: Paul Menage: "Re: [PATCH] lock assertion macros for 2.5.30"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, 8 Aug 2002, Paul Menage wrote:

> There are some cases where this might not be true - e.g. in the
> migration code in at least one version of the O(1) scheduler (included
> in RedHat's 2.4.18-4) the migration_lock is taken on one CPU and
> released on another (following an IPI being sent from the CPU that took
> the lock).

Colour me impressed ...

Ingo never ceases to amaze ;)

Rik

-- http://www.linuxsymposium.org/2002/ "You're one of those condescending OLS attendants" "Here's a nickle kid. Go buy yourself a real t-shirt"

http://www.surriel.com/ http://distro.conectiva.com/

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Petr Vandrovec: "Re: Part 2: Re: [PATCH] pdc20265 problem."
Previous message: Scott Murray: "Re: RFC: PCI hotplug resource reservation"
In reply to: Paul Menage: "Re: [PATCH] lock assertion macros for 2.5.30"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:17 EST