Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update ucode on Intel's CPU

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/15/2012 03:15 PM, Yinghai Lu wrote:

That is for the kernel region itself (that code is actually unchanged from
the current code), and yes, we could cap that one to _end if there are
systems which have bugs in that area.  The dynamic page tables map 1G
aligned at a time.

dynamic should be 2M too.

AMD system:

http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commitdiff;h=66520ebc2df3fe52eb4792f8101fac573b766baf

  BIOS-e820: [mem 0x0000000100000000-0x000000e037ffffff] usable
  BIOS-e820: [mem 0x000000e038000000-0x000000fcffffffff] reserved
  BIOS-e820: [mem 0x0000010000000000-0x0000011ffeffffff] usable

the hole is not 1G aligned.

or HT region is from e040000000 ?


The HT region starts at 0xfd00000000 -- after that reserved region, so I have no idea what that particular system is trying to do or what is requirements are (nor what its MTRR setup is, since you didn't post it.)

	-hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Stable Commits]     [Linux Stable Kernel]     [Linux Kernel]     [Linux USB Devel]     [Linux Video &Media]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux