Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755567AbZIBC36 (ORCPT ); Tue, 1 Sep 2009 22:29:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751536AbZIBC36 (ORCPT ); Tue, 1 Sep 2009 22:29:58 -0400 Received: from eddie.linux-mips.org ([78.24.191.182]:51905 "EHLO eddie.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751856AbZIBC35 (ORCPT ); Tue, 1 Sep 2009 22:29:57 -0400 X-Greylist: delayed 768 seconds by postgrey-1.27 at vger.kernel.org; Tue, 01 Sep 2009 22:29:57 EDT Date: Wed, 2 Sep 2009 03:17:08 +0100 (BST) From: "Maciej W. Rozycki" To: Rakib Mullick cc: LKML , x86@kernel.org, Ingo Molnar Subject: Re: [Question] x86,APIC: In apicdef.h dfr,svr,...... shouldn't be const? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 692 Lines: 17 On Tue, 1 Sep 2009, Rakib Mullick wrote: > Hello guys, Intel System programmers guide says - dfr, svr, esr - this > registers should be readonly. So shouldn't they use const? Or is it > anything else? All the three have meaningful semantics on writes at least on some versions of the APIC (they either have writable fields or trigger side effects on writes). It looks like your documentation is wrong (not unheard of with Intel). Maciej -- 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/