linux-kernel - Re: [Question] x86,APIC: In apicdef.h dfr,svr,...... shouldn't be const?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0909020308510.27310@eddie.linux-mips.org>
Date:	Wed, 2 Sep 2009 03:17:08 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Rakib Mullick <rakib.mullick@...il.com>
cc:	LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [Question] x86,APIC: In apicdef.h dfr,svr,...... shouldn't be
 const?

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/