On 03 Sep 2007 05:21:41 -0400, Jes Sorensen <jes@xxxxxxx> wrote: > >>>>> "Natalie" == Natalie Protasevich <protasnb@xxxxxxxxx> writes: > > Natalie> From: Natalie Protasevich <protasnb@xxxxxxxxx> > > Natalie> This patch allows to disable ptc.g. The code used to be in > Natalie> the kernel, then was removed in 2.4 since the bug that it was > Natalie> fixing has gone away. However, some large system vendors now > Natalie> want this capability available through a means that can be > Natalie> controlled by the platform in the event that there is an > Natalie> issue with either processor or their chipset where global > Natalie> ptc.g is not operational. They want the mechanism for future > Natalie> platforms to work around such issues. It is also needed for > Natalie> platform makers when they deliberately do not use the global > Natalie> cache purge in their chipset implementation. (For such cases, > Natalie> Intel provided a SAL table entry to specify if ptc.g is > Natalie> allowed and how many). > > If you need a special TLB purge implementation, please use the machine > vector as we do on the sn2 architecture - there is no reason to > implement a boot time option for this. The boot option is only temporary, until the SAL/PAL mechanism will be shaken up. I will digest and use the machvec then, how about that? For now I'd like to provide this revived patch as is for it is proven to be working in the past, if you don't mind this first stage. > Who are these large system vendors who want this patch in? I presume > it's not the people running gmail? :-) No :) those interested are big hardware makers of large scaled out boxes, such as HP, UIS. They are using own asics and are not necessarily being able to keep chipset native capabilities intact. As I said in the preamble, the mechanism has to be there so they can turn the ptc.g off and run the OS. Regards, --Natalie > > Cheers, > Jes > - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|