On Thu, 30 Aug 2007, Luck, Tony wrote:
>
> This will update the files shown below. The change to drivers/char/hpet.c
> makes the hpet timer code there ia64 only until we can do something better
> to merge in arch/{i386,x86_64)/kernel/hpet.c
That's crazy. The patch in question looks like this:
On Fri, 2007-08-31 at 09:45, Luck, Tony wrote:
> > Please consider the scenario when many cpus are calling
> > ia64_global_tlb_purge at the same time without any lock.
> > Using global variables to indicate tlb flush start and end is not safe
> > here.
>
> Isn't everything protected by the
> Please consider the scenario when many cpus are calling
> ia64_global_tlb_purge at the same time without any lock.
> Using global variables to indicate tlb flush start and end is not safe
> here.
Isn't everything protected by the
spin_lock(&ptcg_lock);
...
spin_unlock(
On Fri, 2007-08-31 at 04:38, Natalie Protasevich wrote:
> From: Natalie Protasevich <[EMAIL PROTECTED]>
>
> This patch allows to disable ptc.g. The code used to be in the kernel, then
> was removed in 2.4 since the bug that it was fixing has gone away. However,
> some large system vendors now wa
Hi Linus,
please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git release
This will update the files shown below. The change to drivers/char/hpet.c
makes the hpet timer code there ia64 only until we can do something better
to merge in arch/{i386,x86_64)/kernel
From: Natalie Protasevich <[EMAIL PROTECTED]>
This patch allows to disable ptc.g. The code used to be in the kernel, then
was removed in 2.4 since the bug that it was fixing has gone away. However,
some large system vendors now want this capability available through a means
that can be control
On Thu, 30 Aug 2007, Nick Piggin wrote:
> OK, thanks for that. I think I have a rough idea of how they both
> work... I was just thinking (hoping) that, although the writel may
> not reach the device before the store reaches memory, it would
> _appear_ that way from the POV of the device (ie. if t
