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: <20080903184552.GE14481@linux-os.sc.intel.com>
Date:	Wed, 3 Sep 2008 11:45:52 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
Cc:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	"mingo@...e.hu" <mingo@...e.hu>, "hpa@...or.com" <hpa@...or.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [patch 1/2] x2apic: fix reserved APIC register accesses in print_local_APIC()

On Tue, Sep 02, 2008 at 10:28:54PM -0700, Maciej W. Rozycki wrote:
> On Tue, 2 Sep 2008, Suresh Siddha wrote:
> 
> > APIC_RRR is a reserved register for integrated APIC's.
> 
>  NAK this change -- the Remote Read register is officially supported up to
> the Pentium integrated APIC and to the best of my knowledge it works with
> the P6 APIC as well.  Any APIC using the serial inter-APIC bus should
> support it.

from SDV Vol 3a Section 17.27.1

  The remote read delivery mode provided in the 82489DX and local APIC for
  Pentium processors is not supported in the local APIC in the Pentium 4, Intel
  Xeon, and P6 family processors.

It looks like it is not supported (officially atleast) even in APIC bus
architectures. Only the Pentium integrated APIC seems to be the exception.

I have to probably use maxlvt check, to selectively enable this debug output
for Pentium and !APIC_INTEGRATED check for 82489DX.

thanks,
suresh
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ