Date: Thu, 6 Mar 2008 14:13:23 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Jan Beulich <jbeulich@novell.com>, tglx@linutronix.de, hpa@zytor.com,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fix typo(?) in step.c
Message-ID: <20080306131323.GD21359@elte.hu>
References: <47CE69B0.76E4.0078.0@novell.com> <20080305134150.GA16477@elte.hu> <20080306075223.BA28B2700FD@magilla.localdomain> <20080306113413.GD17906@elte.hu> <20080306121648.A53FA2700FD@magilla.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080306121648.A53FA2700FD@magilla.localdomain>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 777
Lines: 22


* Roland McGrath <roland@redhat.com> wrote:

> > So in theory the bug should manifest itself as block-step mode never 
> > clearing itself, once activated.
> 
> That doesn't happen in the trivial sense of "never", because in the 
> normal case an actual block-step exception happens and that makes the 
> hardware clear BTF from the MSR (as well as TF from eflags).  So it 
> would only come up in a more obscure case. [...]

ah, i missed that detail - this indeed makes this code a lot less 
dangerous.

/me stops worrying

	Ingo
--
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/