the existing kobject_put to fix this.
Signed-off-by: Balaji Rao <[EMAIL PROTECTED]>
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 64926aa..2158786 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -1004,17 +1004,6 @@ static int __cpufreq_
to the existing kobject_put to fix this.
Signed-off-by: Balaji Rao [EMAIL PROTECTED]
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 64926aa..2158786 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -1004,17 +1004,6 @@ static int __cpufreq_remove_dev (struct
irst
> or
> + trim_start = (u64)highest_pfn << PAGE_SHIFT;
> + trim_size = (u64)end_pfn << PAGE_SHIFT;
>
Yea right.. Thanks for pointing that out.
--
regards,
balaji rao
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
On Thursday 07 February 2008 01:32:45 pm Ingo Molnar wrote:
> * Balaji Rao <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > The following commit caused my X server to stop working.
> >
> > commit 99fc8d424bc5d803fe92cad56c068fe64e73747a
> > Author: Jesse B
On Thursday 07 February 2008 01:32:45 pm Ingo Molnar wrote:
* Balaji Rao [EMAIL PROTECTED] wrote:
Hello,
The following commit caused my X server to stop working.
commit 99fc8d424bc5d803fe92cad56c068fe64e73747a
Author: Jesse Barnes [EMAIL PROTECTED]
Date: Wed Jan 30 13:33:18 2008
ndling of addresses > 4G by
mtrr_trim_uncached_memory.
This, now brings up X on my system.
Signed-off-by: Balaji Rao <[EMAIL PROTECTED]>
diff --git a/arch/x86/kernel/cpu/mtrr/main.c b/arch/x86/kernel/cpu/mtrr/main.c
index 1e27b69..b0f1d48 100644
--- a/arch/x86/kernel/cpu/mtrr/main.c
+++ b/arch/x86/
4G by
mtrr_trim_uncached_memory.
This, now brings up X on my system.
Signed-off-by: Balaji Rao [EMAIL PROTECTED]
diff --git a/arch/x86/kernel/cpu/mtrr/main.c b/arch/x86/kernel/cpu/mtrr/main.c
index 1e27b69..b0f1d48 100644
--- a/arch/x86/kernel/cpu/mtrr/main.c
+++ b/arch/x86/kernel/cpu/mtrr
On Friday 18 January 2008 04:04:33 am Jan Engelhardt wrote:
>
> On Jan 16 2008 13:20, Daniel Walker wrote:
> >On Thu, 2008-01-17 at 02:09 +0530, Balaji Rao wrote:
> >> Hi,
> >>
> >> When i set jiffies as the current_clocksource, date(1) tells me
> &g
> > --- linux-2.6.orig/arch/x86/kernel/hpet.c
> ...
> >
>
> it works
>
Cool!
Ingo, here's the patch with the SOB. Please apply.
regards,
balaji rao
Check if there's an IRQ assigned to the timer before
...
it works
Cool!
Ingo, here's the patch with the SOB. Please apply.
regards,
balaji rao
Check if there's an IRQ assigned to the timer before assigning one.
Signed-off-by: Balaji Rao [EMAIL PROTECTED]
Index: linux-2.6/arch/x86/kernel/hpet.c
On Friday 18 January 2008 04:04:33 am Jan Engelhardt wrote:
On Jan 16 2008 13:20, Daniel Walker wrote:
On Thu, 2008-01-17 at 02:09 +0530, Balaji Rao wrote:
Hi,
When i set jiffies as the current_clocksource, date(1) tells me
that wallclock time has stopped, and soon after
also encountered the same problem when i ran the kernel in qemu, and set pit
as the current_clocksource. Why does this
happen ?
So, i think should we unregister jiffies as a clocksource when we go into NO_HZ
?
Thomas, Ingo what are your thoughts on this ?
regards,
balaji rao
--
To unsubscribe
On Wednesday 16 January 2008 12:21:33 pm Ingo Molnar wrote:
Hi Ingo,
> * Yinghai Lu <[EMAIL PROTECTED]> wrote:
> > "
> > commit e5ed385fa0d6f35406e3e3ed75e5eb9adeb811df
> > Author: Balaji Rao <[EMAIL PROTECTED]>
> > Date: Tue Jan 15 16:53:29 2008
On Wednesday 16 January 2008 12:21:33 pm Ingo Molnar wrote:
Hi Ingo,
* Yinghai Lu [EMAIL PROTECTED] wrote:
commit e5ed385fa0d6f35406e3e3ed75e5eb9adeb811df
Author: Balaji Rao [EMAIL PROTECTED]
Date: Tue Jan 15 16:53:29 2008 +0100
Assign IRQs to HPET Timers
in x86.git
also encountered the same problem when i ran the kernel in qemu, and set pit
as the current_clocksource. Why does this
happen ?
So, i think should we unregister jiffies as a clocksource when we go into NO_HZ
?
Thomas, Ingo what are your thoughts on this ?
regards,
balaji rao
--
To unsubscribe
On Monday 14 January 2008 06:29:27 pm Clemens Ladisch wrote:
> Andrew Paprocki wrote:
> > I started debugging a problem I was having with my sky2 network driver
> > under 2.6.23.13. The investigation led me to find that the HPET timer
> > wasn't working at all, causing the sky2 driver to not work
On Monday 14 January 2008 06:29:27 pm Clemens Ladisch wrote:
Andrew Paprocki wrote:
I started debugging a problem I was having with my sky2 network driver
under 2.6.23.13. The investigation led me to find that the HPET timer
wasn't working at all, causing the sky2 driver to not work
| 45 ++---
include/linux/hpet.h |2 +-
3 files changed, 44 insertions(+), 16 deletions(-)
Signed-off-by: Balaji Rao <[EMAIL PROTECTED]>
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index 4a86ffd..08ee998 100644
--- a/arch/x86/
| 45 ++---
include/linux/hpet.h |2 +-
3 files changed, 44 insertions(+), 16 deletions(-)
Signed-off-by: Balaji Rao [EMAIL PROTECTED]
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index 4a86ffd..08ee998 100644
--- a/arch/x86/kernel/hpet.c
Assign an IRQ to HPET Timer devices when interrupt enable is requested.
This now makes the HPET userspace API work.
drivers/char/hpet.c | 31 +--
include/linux/hpet.h |2 +-
2 files changed, 30 insertions(+), 3 deletions(-)
Signed-off-by: Balaji Rao R <[EM
Assign an IRQ to HPET Timer devices when interrupt enable is requested.
This now makes the HPET userspace API work.
drivers/char/hpet.c | 31 +--
include/linux/hpet.h |2 +-
2 files changed, 30 insertions(+), 3 deletions(-)
Signed-off-by: Balaji Rao R [EMAIL
21 matches
Mail list logo
