Home » Mailing list archives » linux-kernel » 2007 » October » 2

Re: [PATCH] mark read_crX() asm code as volatile

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Arjan van de Ven <arjan@...>
To: Kirill Korotaev <dev@...>
Cc: Andrew Morton <akpm@...>, Andi Kleen <ak@...>, Linux Kernel Mailing List <linux-kernel@...>, <devel@...>
Subject: Re: [PATCH] mark read_crX() asm code as volatile
Date: Tuesday, October 2, 2007 - 11:28 am

On Tue, 02 Oct 2007 18:08:32 +0400
Kirill Korotaev <dev@openvz.org> wrote:


I'm not so sure volatile is the right answer, as compared to giving the
asm more strict contraints....

asm volatile tends to mean something else than "the result has
changed"....

-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[PATCH] mark read_crX() asm code as volatile, Kirill Korotaev, (Tue Oct 2, 10:08 am)
Re: [PATCH] mark read_crX() asm code as volatile, Arjan van de Ven, (Tue Oct 2, 11:28 am)
Re: [PATCH] mark read_crX() asm code as volatile, Kirill Korotaev, (Wed Oct 3, 4:25 am)
Re: [PATCH] mark read_crX() asm code as volatile, H. Peter Anvin, (Tue Oct 2, 3:21 pm)
Re: [PATCH] mark read_crX() asm code as volatile, Chuck Ebbert, (Tue Oct 2, 2:27 pm)
Re: [PATCH] mark read_crX() asm code as volatile, Nick Piggin, (Tue Oct 2, 8:14 am)
Re: [PATCH] mark read_crX() asm code as volatile, H. Peter Anvin, (Wed Oct 3, 2:18 am)
Re: [PATCH] mark read_crX() asm code as volatile, Nick Piggin, (Tue Oct 2, 11:49 am)
Re: [PATCH] mark read_crX() asm code as volatile, Andi Kleen, (Wed Oct 3, 4:45 am)
Re: [PATCH] mark read_crX() asm code as volatile, Andi Kleen, (Tue Oct 2, 10:17 am)