RE: [PATCH v1 0/2] fix the defect that pcc-cpufreq's pcc_get_freq() sometimes can't get correct CPU frequency

nal Message- > From: Zhang, Lin-Bao (Linux Kernel R) > Sent: 2015年11月16日 18:36 > To: 'r...@rjwysocki.net'; 'viresh.ku...@linaro.org'; > 'linux...@vger.kernel.org'; > 'linux-kernel@vger.kernel.org' > Subject: [PATCH v1 0/2] fix the defect that pcc-cpufreq's pcc_get_freq()

RE: [PATCH v1 0/2] fix the defect that pcc-cpufreq's pcc_get_freq() sometimes can't get correct CPU frequency

nal Message- > From: Zhang, Lin-Bao (Linux Kernel R) > Sent: 2015年11月16日 18:36 > To: 'r...@rjwysocki.net'; 'viresh.ku...@linaro.org'; > 'linux...@vger.kernel.org'; > 'linux-kernel@vger.kernel.org' > Subject: [PATCH v1 0/2] fix the defect that pcc-cpufreq's pcc_get_freq()

[PATCH v1 2/2] retry 2 times when getting cpu frequency is zero

when getting cpu frequency failures, it will retry 2 times at most. Signed-off-by: Pearson, Greg Signed-off-by: Zhang, Lin-Bao --- drivers/cpufreq/pcc-cpufreq.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/drivers/cpufreq/pcc-cpufreq.c b/drivers/cpufreq/pcc-cpufreq.c index

[PATCH v1 1/2] enforce max/min time between commands

In Processor Clocking Control specification v1.0 ,there are 2 definitions: 2.1.8 Minimum Time Between Commands 2.1.9 Maximum Time Between Commands that means 2 commands' interval should be located between Minimum Time Between Commands and Maximum Time Between Commands. 3.1 Get Average Frequency

[PATCH v1 0/2] fix the defect that pcc-cpufreq's pcc_get_freq() sometimes can't get correct CPU frequency

Summary : These 2 patches are developed for drivers/cpufreq/pcc-cpufreq.c's pcc_get_freq() function. The pcc-cpufreq driver's function pcc_get_freq() sometimes returns invalid frequency information. Without the these 2 patches , it can be reproduced on booting Linux Kernel with loading

[PATCH v1 1/2] enforce max/min time between commands

In Processor Clocking Control specification v1.0 ,there are 2 definitions: 2.1.8 Minimum Time Between Commands 2.1.9 Maximum Time Between Commands that means 2 commands' interval should be located between Minimum Time Between Commands and Maximum Time Between Commands. 3.1 Get Average Frequency

[PATCH v1 0/2] fix the defect that pcc-cpufreq's pcc_get_freq() sometimes can't get correct CPU frequency

Summary : These 2 patches are developed for drivers/cpufreq/pcc-cpufreq.c's pcc_get_freq() function. The pcc-cpufreq driver's function pcc_get_freq() sometimes returns invalid frequency information. Without the these 2 patches , it can be reproduced on booting Linux Kernel with loading

[PATCH v1 2/2] retry 2 times when getting cpu frequency is zero

when getting cpu frequency failures, it will retry 2 times at most. Signed-off-by: Pearson, Greg Signed-off-by: Zhang, Lin-Bao --- drivers/cpufreq/pcc-cpufreq.c | 10 ++ 1 file changed, 10 insertions(+) diff --git

[stable 3.0 v2] x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems

Hi Greg, This patch is specially for 3.0 by integrating upstream commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc and ea0dcf903e7d76aa5d483d876215fedcfdfe140f . I fixed patch format warning and re-send it as v2. Thanks . --- ./scripts/checkpatch.pl

[stable 3.0] x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems

Hi Greg, This patch is specially for 3.0 by integrating upstream commit cb214ede7657db458fd0b2a25ea0b28dbf900ebc and ea0dcf903e7d76aa5d483d876215fedcfdfe140f I tested it in v3.0.66. any questions, let me know. Thanks. -- From: Zhang Lin-Bao x86/apic: Work around boot

[ stable-3.0] x86/apic: Work around boot failure on HP ProLiant DL980 G7 Server systems

Hi Greg, I am very pleased to see this patch has been put into 3.8,3.7.9,and 3.4.4. thanks for your works. Do you have any plan to put it into stable-3.0.y version ? and other mainline ,such as 3.1.x,3.2.x,3.3.x ,etc. afterwards ? I see 3.0.66 is just released 8 hours ago, but without

RE: Why Linux kernel forced to enter X2APIC mode( just because of booting cpu has supported x2apic) without depending on BIOS' setting in MSR->x2apic enablement bit ?

Hi Yinghai, Maybe two days ago, mis-understand the usage of MSR. Today, I carefully researched Intel? 64 Architecture x2APIC Specification which is open for all people. I think current core argument is our BIOS did following judgement , but Linux kernel did not(Linux seems just judge

RE: Why Linux kernel forced to enter X2APIC mode( just because of booting cpu has supported x2apic) without depending on BIOS' setting in MSR->x2apic enablement bit ?

Hi Yinghai , Actually ,my question like this: OS can really enable x2apic correctly without BIOS' help in this case : BIOS has claimed definitely it doesn't enable x2apic ,but OS feel it can enable x2apic(based on BSP supports x2apic) ). If Linux don't need BIOS' help , how did linux

RE: Why Linux kernel forced to enter X2APIC mode( just because of booting cpu has supported x2apic) without depending on BIOS' setting in MSR->x2apic enablement bit ?

Hi Yinghai , Thanks very much for your reply. I also checked some other previous emails about x2apic patches. > From: yhlu.ker...@gmail.com [mailto:yhlu.ker...@gmail.com] On Behalf Of > Yinghai Lu I just worry about this case, > > b) If BIOS feel the system doesn't meet x2apic

Why Linux kernel forced to enter X2APIC mode( just because of booting cpu has supported x2apic) without depending on BIOS' setting in MSR->x2apic enablement bit ?

Hi Suresh and other guys , In 3.4.4/3.6.6 ,I found a x2apic issue . if I am wrong , sorry first , and welcome your correction . thanks for your forwarding other maintainers. I am testing a server , its BIOS is like this: a) If BIOS think the system is of x2apic , it will set

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

> -Original Message- > From: Suresh Siddha [mailto:suresh.b.sid...@intel.com] > Sent: 2012年10月10日 18:02 > > > So I looked at why you are seeing the problem with v2.6.32 but not > > > with the recent kernels. And I think I found out the reason. > > > > I want to know what masking IO-APIC

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

> -Original Message- > From: H. Peter Anvin [mailto:h...@zytor.com] > Sent: 2012年10月10日 23:27 > To: Zhang, Lin-Bao (Linux Kernel R); Suresh Siddha > Cc: linux-kernel@vger.kernel.org; a...@lxorguk.ukuu.org.uk; > mi...@redhat.com; Croxon, Nigel; t...@linutronix.d

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

> -Original Message- > From: Suresh Siddha [mailto:suresh.b.sid...@intel.com] > > > Can you please apply the appended patch to 2.6.32 kernel and see if > > > the issue you mentioned gets fixed? If so, we can ask the -stable > > > and OSV's teams to pick up this fix. > > Yes , it can

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

Hi Suresh, Now , I want to clarify 2 type of errors : a) some interrupt doesn't work through Interrupt -remapped IO-APIC. b) an interrupt is coming , there is an IO-APIC entry to know how to route it to which CPU, but VT-d entry is empty, ITP will report Present bit is clear. BIOS should

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

Hi Suresh, Thanks very much for your reply! I tested this patch in 2.6.32 with our machine , it can indeed can resolve current issue. that 's good. I also check 3.x version of kernel source , for example , 3.3.8 and 3.0.0 , they indeed include similar patch , I think the key action

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

? Thanks very much! -- Bob(LinBao Zhang) HP linux kernel enginner > -Original Message- > From: Zhang, Lin-Bao (Linux Kernel R) > Sent: 2012年9月21日 1:16 > To: 'Suresh Siddha' > Cc: linux-kernel@vger.kernel.org; a...@lxorguk.ukuu.org.uk; > mi...@redhat.com; Croxon, Nigel; '

RE: [PATCH] fix x2apic defect that Linux kernel doesn't mask 8259A interrupt during the time window between changing VT-d table base address and initializing these VT-d entries(smpboot.c and apic.c )

; From: Suresh Siddha [mailto:suresh.b.sid...@intel.com] > Sent: 2012年9月21日 6:23 > To: Zhang, Lin-Bao (Linux Kernel R) > Cc: linux-kernel@vger.kernel.org; a...@lxorguk.ukuu.org.uk; > mi...@redhat.com; Croxon, Nigel > Subject: Re: [PATCH] fix x2apic defect that Linux kernel doesn't m