> On Mon, Feb 25, 2008 at 09:43:59AM +0800, Cai, Crane wrote:
> > > On Fri, Feb 22, 2008 at 01:49:20PM +0800, Cai, Crane wrote:
> > > > > On Thu, Feb 21, 2008 at 03:47:33PM -0800, Greg
> > > Kroah-Hartman wrote:
> > > > > > +static void __devinit quirk_amd_ide_mode(struct pci_dev
> > > > > > +*pde
[H. Peter Anvin - Sun, Feb 24, 2008 at 06:15:52PM -0800]
> Cyrill Gorcunov wrote:
>> Hi Peter, Sam,
>> could you take a look on x86/boot/header.S:280 please?
>> # Zero the bss
>> movw$__bss_start, %di
>> movw$_end+3, %cx
>> xorl%eax, %eax
>> subw%di, %cx
>>
On Saturday 23 February 2008, David Brownell wrote:
...
> No, it's fully defined. "Crash my engine" is not OK. The delay
> is controlled by transfer.delay_usecs ... possibly zero, which is
> best viewed as a degenerate case.
Ooops, I missed that (the delay *is* defined in transfer.delay_usecs).
S
On 02/25/2008 12:21 AM, Stephen Neuendorffer wrote:
@@ -549,8 +556,7 @@ static int hwicap_release(struct inode *inode,
struct file *file)
int i;
int status = 0;
- if (down_interruptible(&drvdata->sem))
- return -ERESTARTSYS;
+ mutex_lock(&drvdata->
We have four patches, all with the same title - please avoid doing this.
I could invent titles for them (as I often have to do), but I think it
would be best if you were to do so. That way, we avoid confusion and
people who later google for the patch's title to understand the patch's
background w
* James Morris <[EMAIL PROTECTED]> wrote:
> > > could you try the fix below ontop of x86.git#testing, does it
> > > solve your boot hang?
> >
> > find below another fix that is somewhat better as it does not affect
> > the native kernel and !PARAVIRT.
>
> This works.
thanks. We'll delay the
Le Sat, 23 Feb 2008 10:43:37 +0800,
Matt Mackall <[EMAIL PROTECTED]> a écrit :
> This is not quite what Peter and I were thinking of, I think. It's not
> at all generic. How about a section that simply contains a set of
> function pointers, a macro to add things to that section, and a
> function t
On Mon, Feb 25, 2008 at 8:31 AM, Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Paolo Ciarrocchi <[EMAIL PROTECTED]> wrote:
>
> > Before:
> > total: 34 errors, 14 warnings, 456 lines checked
> >
> > After:
> > total: 0 errors, 8 warnings, 456 lines checked
>
> sidenote: please also indicate to
> === after conversion
> struct bus_master_interface *interface;
> while (interface->ack != OK) {
> delay(a short while);
> rmb();
> [ after X loops device changes interface->ack by dma ]
> };
>
> All I need is for the read of interface->ack in the loop not to be optimise
During compilation:
LD [M] drivers/pcmcia/pcmcia_core.o
WARNING: drivers/pcmcia/pcmcia_core.o(.data+0x1d4): Section mismatch in
reference from the variable pccard_sysfs_interface to the function
.devinit.text:pccard_sysfs_add_socket()
The variable pccard_sysfs_interface references
the functio
* H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Please fix it in both places. Using XOR instead of AND-NOT is a bug,
> plain and simple.
yes, i already fixed that when i added Mikael's patch and it's all
queued up.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux
Sorry, [EMAIL PROTECTED] was missed in cc
On Mon, Feb 25, 2008 at 3:34 PM, Dave Young <[EMAIL PROTECTED]> wrote:
>
> On Mon, Feb 25, 2008 at 3:30 PM, Dave Young <[EMAIL PROTECTED]> wrote:
> > Quote mail from [EMAIL PROTECTED] :
> >
> > 2007/12/17 Louis JANG <[EMAIL PROTECTED]>:
> >
> >
> >
MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0xec461): Section mismatch in reference from the
function pci_scan_child_bus() to the function .devinit.text:pcibios_fixup_bus()
The function pci_scan_child_bus() references
the function __devinit pcibios_fixup_bus().
This is often because pci_scan_chil
Paul E. McKenney schrieb:
On Fri, Feb 22, 2008 at 01:52:53AM +0100, Tilman Schmidt wrote:
So the nf_conntrack BUG is fixed, but the crash (and of course the
swapper "spinlock bad magic" BUG) persists.
Do you have CONFIG_DEBUG_PREEMPT set? That would help find any other
bugs similar to nf_co
On 25-02-08 08:44, Ady Wicaksono wrote:
I have 8 Gbytes RAM, but why I can allocate 2.8 Gbytes RAM for a single
process? How to patch kernel so I have more than 2.8 Gbytes limitation?
[ ... ]
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dt
On Sun, Feb 24, 2008 at 10:21 PM, Bill Huey (hui) <[EMAIL PROTECTED]> wrote:
> It's probably safe to use, but it's not what its original purpose was
> and you should use another function/macro. This is an annotation issue
> and your use of it is inconsistent with how it's used in voluntary
> pre
On Thursday 21 February 2008, Alan Stern wrote:
> > = CUT HERE
> > Modify EHCI irq handling on the theory that at least some of the
> > "lost" IRQs are caused by goofage between multiple lowlevel IRQ
> > acking mechanisms: try rescanning before we exit the handler, in
> > case the EHCI-int
Ingo Molnar writes:
>
> * H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>
> > Please fix it in both places. Using XOR instead of AND-NOT is a bug,
> > plain and simple.
>
> yes, i already fixed that when i added Mikael's patch and it's all
> queued up.
Ok. For reference and for LKML view
* Mikael Pettersson <[EMAIL PROTECTED]> wrote:
> > yes, i already fixed that when i added Mikael's patch and it's all
> > queued up.
>
> Ok. For reference and for LKML viewers, this is what the final patch
> should be:
below is the full commit - will send it to Linus later today.
I
"Kiyoshi Ueda" <[EMAIL PROTECTED]> writes:
> o Have you tried bisecting the kernel changes to find suspicious
>commit? If so, that information will be much appreciated.
That is close to impossible. Intervening kernels either don't boot or
crash while burning. Especially the one with the b
On Mon, 2008-02-25 at 00:17 -0800, Andrew Morton wrote:
> We have four patches, all with the same title - please avoid doing this.
>
> I could invent titles for them (as I often have to do), but I think it
> would be best if you were to do so. That way, we avoid confusion and
> people who later
Hello,
2.6.25-rc2-git7 has regression, thinkpad keys do not work any more.
Probably this commit broke things 6c231bd5eb07ce546517019f334652b9ecfc329a
--
Lukáš Hejtmánek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
From: Lei Ming <[EMAIL PROTECTED]>
update the comment for the removed "driver" field and being
out-of-order of @cur_altsetting and @num_altsetting.
Signed-off-by: Lei Ming <[EMAIL PROTECTED]>
---
include/linux/usb.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
mode change 100
Hi,
Stephen Rothwell wrote:
> I have created today's linux-next tree at
i bet your $SUBJECT was meant for the Tree for Feb 25, wasn't it?
;-)
Thanks,
Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
> I ever asked marcel about the coding style. please see following thread:
> http://lkml.org/lkml/2008/1/22/91
>
> I think the style problem marcel said is
> 1. using kernel codeing style
> 2. marcel's style
> container_of or get_user_data calls at the top of the variable declaration
> using the e
Hi Sam,
you know I've just take a look on different architectures and I suddenly
realized that I even can't test my changes I'm bringnin in. For example -
xtensa arch, most of lds numeric constants could (and should) be changed
to PAGE_SIZE and THREAD_SIZE but this requires to include additional
h
cpuidle C-state sysfs node time and usage are very easy to overflow because
they are all of unsigned int type, time will overflow within about two hours,
usage will take longer time to overflow, but they are increasing for ever.
This patch will convert them to unsigned long long.
Signed-off-by:
On Monday 25 February 2008 07:49:35 Greg KH wrote:
> On Mon, Feb 25, 2008 at 08:16:17AM +0200, Pekka J Enberg wrote:
> > Hi Michael,
> >
> > On Sun, 24 Feb 2008, Michael Buesch wrote:
> > > > The ony way I see this was possible, you manually changed the
> > > > module loading order, so that the b4
* Yi Yang <[EMAIL PROTECTED]> wrote:
> cpuidle C-state sysfs node time and usage are very easy to overflow
> because they are all of unsigned int type, time will overflow within
> about two hours, usage will take longer time to overflow, but they are
> increasing for ever.
>
> This patch will
Greg KH wrote:
On Mon, Feb 25, 2008 at 03:57:44PM +0900, Kohei KaiGai wrote:
Greg KH wrote:
On Mon, Feb 25, 2008 at 03:10:27PM +0900, Kohei KaiGai wrote:
[PATCH 1/3] add a private data field within kobj_attribute structure.
This patch add a private data field, declared as void *, within
kobj
On Mon, Feb 25, 2008 at 5:28 PM, Louis JANG <[EMAIL PROTECTED]> wrote:
>
> > I ever asked marcel about the coding style. please see following thread:
> > http://lkml.org/lkml/2008/1/22/91
> >
> > I think the style problem marcel said is
> > 1. using kernel codeing style
> > 2. marcel's style
On Monday 25 February 2008 11:23:02 Alexey Zaytsev wrote:
> On Mon, Feb 25, 2008 at 9:49 AM, Greg KH <[EMAIL PROTECTED]> wrote:
> >
> > On Mon, Feb 25, 2008 at 08:16:17AM +0200, Pekka J Enberg wrote:
> > > Hi Michael,
> > >
> > > On Sun, 24 Feb 2008, Michael Buesch wrote:
> > > > > The ony way
Hi Ingo,
Le lundi 25 février 2008, Ingo Molnar a écrit :
> hm, i'm not sure. Right now we just have a 32-bit defconfig and a 64-bit
> defconfig - but there are about 8 subarchitectures in arch/x86. Given
> the amount of variety in PC hardware, i doubt it makes sense to start
> collecting defconfig
Hi Ingo,
Le lundi 25 février 2008, Ingo Molnar a écrit :
> thanks, applied. I guess i should push this change upstream only once
> the new watchdog driver has been committed to drivers/watchdog/ ?
Yes it would be better, thank you very much !
signature.asc
Description: This is a digitally signe
Hi Ingo,
Le lundi 25 février 2008, Ingo Molnar a écrit :
> ok, great! Btw., do you think you could achieve your board to boot fine
> with CONFIG_X86_GENERICARCH=y and CONFIG_M486=y?
I think it can boot already, will tell you when I have done the necessary
testing.
--
To unsubscribe from this lis
This patch adds the default kernel configuration
for the RDC R-321x SoC.
Signed-off-by: Florian Fainelli <[EMAIL PROTECTED]>
---
diff --git a/arch/x86/configs/rdc321x_defconfig
b/arch/x86/configs/rdc321x_defconfig
new file mode 100644
index 000..d87e731
--- /dev/null
+++ b/arch/x86/configs/rd
Hi All,
I report new results of dm-ioband bandwidth control test. The previous
test results were posted on Jan 25.
I've got really good results as well as the last report. dm-ioband
works well with Xen virtual disk.
I also announce that dm-ioband website has launched. The patches,
the manual, the
On Mon, Feb 25, 2008 at 9:49 AM, Greg KH <[EMAIL PROTECTED]> wrote:
>
> On Mon, Feb 25, 2008 at 08:16:17AM +0200, Pekka J Enberg wrote:
> > Hi Michael,
> >
> > On Sun, 24 Feb 2008, Michael Buesch wrote:
> > > > The ony way I see this was possible, you manually changed the
> > > > module loadin
On Sun, 2008-02-24 at 20:33 -0800, David Brownell wrote:
> > > > ==> LOCKDEP feature is evidently missing:
> > > > spin_lock_irq_nested(lock_ptr, lock_class)
> > >
> > > This rant is more lines than adding the API :-/ the reason for it not
> > > being there is simple, it wasn't ne
Hi,
Sorry for missing lots of emails in my long vacation. :)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dan Williams
> Sent: Sunday, February 24, 2008 10:06 AM
> To: Kumar Gala
> Cc: LKML Kernel; Zhang Wei
> Subject: Re: dma engine drivers for
On Mon, 2008-02-25 at 11:15 +0100, Ingo Molnar wrote:
> * Yi Yang <[EMAIL PROTECTED]> wrote:
>
> > cpuidle C-state sysfs node time and usage are very easy to overflow
> > because they are all of unsigned int type, time will overflow within
> > about two hours, usage will take longer time to over
Hi Greg!
> On Fri, Feb 15, 2008 at 11:23:47AM +0100, Miklos Szeredi wrote:
> > This is for 2.6.25 and 2.6.24.y, but NOT for 2.6.23.y.
> >
> > Thanks,
> > Miklos
> >
> >
> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >
> > I added a nasty local variable shadowing bug to fuse in 2.6.24, with
All of early setup runs with interrupts disabled, so there is no
need to set up early exception handlers for vectors >= 32
That saves some text size
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86/kernel/head64.c |2 +-
arch/x86/kernel/head_64.S |6 ++
include/asm-x86/
Currently they are in .text.head because the rest of head_64.S.
.text.head is not removed as init data, but the early exception handlers
should be because they are not needed after early boot of the BP.
So move them over.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86/kernel/head_
The early exception handlers are currently set up using a macro
recursion. Replace that with a standard loop.
Noop patch, just a cleanup.
---
arch/x86/kernel/head_64.S | 15 +++
1 file changed, 7 insertions(+), 8 deletions(-)
Index: linux/arch/x86/kernel/head_64.S
===
On Mon, Feb 25, 2008 at 11:14:33AM +0100, Ingo Molnar wrote:
>
> * Florian Fainelli <[EMAIL PROTECTED]> wrote:
>
> > This patch adds the default kernel configuration for the RDC R-321x
> > SoC.
>
> hm, i'm not sure. Right now we just have a 32-bit defconfig and a 64-bit
> defconfig - but there
Hi Frank,
On Mon, 25 Feb 2008 11:12:45 +0100 Frank Seidel <[EMAIL PROTECTED]> wrote:
>
> Stephen Rothwell wrote:
> > I have created today's linux-next tree at
>
> i bet your $SUBJECT was meant for the Tree for Feb 25, wasn't it?
> ;-)
Damn! I remembered to reread to body of the mail and forgot
* Adrian Bunk <[EMAIL PROTECTED]> wrote:
> What I want is that e.g. after fiddling with kernel headers I want an
> easy way of having much compile coverage. And my script that builds
> all defconfig's is trivial (although it takes a day to finish).
no, i think you misunderstood me. I do allyes
On Mon, Feb 25, 2008 at 10:21:01AM +0330, Paolo Ciarrocchi wrote:
> On 2/25/08, Andy Whitcroft
> > As we want the messages to be as short as possible, I am leaning towards
> > standardising on:
> >
> > spaces prohibited
> > spaces required
> >
> in that case i would prefer:
> space not required
* Florian Fainelli <[EMAIL PROTECTED]> wrote:
> > In fact for rdc321x that should be rather easy to do right now:
> > wdt.c could/should become a regular watchdog driver, and do we
> > really need those GPIO specials in include/asm-x86/mach-rdc321x/ ? I
> > believe it should be possible to boo
On Mon, 2008-02-25 at 11:38 +0100, Michael Buesch wrote:
> [1] bcm43xx is unmaintained. Larry used to be the maintainer until
> he dropped it a few months ago.
Doesn't that mean that Alexey gets to be the maintainer, as he's the one
patching it ?
Xav
--
To unsubscribe from this list: s
This driver should be moved to drivers/watchdog so let's
remove the arch/x86/mach-rdc321x/wdt.c file.
Signed-off-by: Florian Fainelli <[EMAIL PROTECTED]>
---
diff --git a/arch/x86/mach-rdc321x/Makefile b/arch/x86/mach-rdc321x/Makefile
index 1faac81..8325b4c 100644
--- a/arch/x86/mach-rdc321x/Makef
* Florian Fainelli <[EMAIL PROTECTED]> wrote:
> This driver should be moved to drivers/watchdog so let's remove the
> arch/x86/mach-rdc321x/wdt.c file.
thanks, applied. I guess i should push this change upstream only once
the new watchdog driver has been committed to drivers/watchdog/ ?
(If t
On Monday 25 February 2008 11:49:34 Xavier Bestel wrote:
> On Mon, 2008-02-25 at 11:38 +0100, Michael Buesch wrote:
> > [1] bcm43xx is unmaintained. Larry used to be the maintainer until
> > he dropped it a few months ago.
>
> Doesn't that mean that Alexey gets to be the maintainer, as he's the o
On Mon, Feb 25, 2008 at 11:51:10AM +0100, Ingo Molnar wrote:
>
> * Florian Fainelli <[EMAIL PROTECTED]> wrote:
>
> > > In fact for rdc321x that should be rather easy to do right now:
> > > wdt.c could/should become a regular watchdog driver, and do we
> > > really need those GPIO specials in in
Le lundi 25 février 2008, Adrian Bunk a écrit :
> Booting it might fine, but CLOCK_TICK_RATE will be wrong...
PIT_TICK_RATE is overriden specificaly for R321x in include/asm-x86/timex.h,
just like for AMD Elan.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Sun, 24 Feb 2008 15:42:51 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> > On Fri, 22 Feb 2008 17:28:37 -0800
> > David Brownell <[EMAIL PROTECTED]> wrote:
> >
> > > +static cycle_t tc_get_cycles(void)
> > > +{
> > > + unsigned long flags;
> > > + u32 lower, upper;
> > > +
> >
On Mon, Feb 25, 2008 at 12:17:07PM +0100, Ingo Molnar wrote:
>
> * Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > What I want is that e.g. after fiddling with kernel headers I want an
> > easy way of having much compile coverage. And my script that builds
> > all defconfig's is trivial (although
Hi,
> Git reset is just the easiest way to reproduce it.
Interesting :)
> I was able to track this corruption down to commit
> a69b176df246d59626e6a9c640b44c0921fa4566 ([XFS] Use the generic bitops
> rather than implementing them ourselves.) using git bisect.
>
> Reverting edd319dc527733e61eec5
Dave Young 쓴 글:
> On Mon, Feb 25, 2008 at 5:28 PM, Louis JANG <[EMAIL PROTECTED]> wrote:
>
>> > I ever asked marcel about the coding style. please see following thread:
>> > http://lkml.org/lkml/2008/1/22/91
>> >
>> > I think the style problem marcel said is
>> > 1. using kernel codeing sty
On Monday, 25 of February 2008, Alan Stern wrote:
> On Sun, 24 Feb 2008, Pavel Machek wrote:
>
> > > > At the very least, you'd need rmb() before reading it and wmb() after
> > > > writing to it, but I'm not sure if that's enough on every obscure
> > > > architecture out there.
> > >
> > > No, ne
On Monday, 25 of February 2008, Alan Stern wrote:
> On Sun, 24 Feb 2008, Rafael J. Wysocki wrote:
>
> > > Very subtly wrong ;-).
> > >
> > > imagine suspending_task == 0xabcdef01. Now task "R" with current ==
> > > 0xabcd reads suspending_task while the other cpu is writing to it,
> > > and s
On Sun, 24 Feb 2008 17:03:10 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> > Which reminds me...you were talking about a patch that adds oneshot
> > support for the count/compare clocksource and more cleanups, but I
> > don't think I've seen it...?
>
> I avoid sending non-working patches, and
On Mon, Feb 25, 2008 at 12:27:34PM +0100, Florian Fainelli wrote:
> Le lundi 25 février 2008, Adrian Bunk a écrit :
> > Booting it might fine, but CLOCK_TICK_RATE will be wrong...
>
> PIT_TICK_RATE is overriden specificaly for R321x in include/asm-x86/timex.h,
> just like for AMD Elan.
Not when
On Monday, 25 of February 2008, Lukas Hejtmanek wrote:
> Hello,
Hi,
Thanks for the report.
> 2.6.25-rc2-git7 has regression, thinkpad keys do not work any more.
>
> Probably this commit broke things 6c231bd5eb07ce546517019f334652b9ecfc329a
Please always provide the commit subject along with t
* Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > What i do against build breakage is randconfig testing. That catches
> > far more build breakage than a few limited number of defconfigs
> > would ever.
>
> How do you test whether a x86 merge might break the compilation of
> e.g. some ARM platform
* Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 25, 2008 at 12:27:34PM +0100, Florian Fainelli wrote:
> > Le lundi 25 février 2008, Adrian Bunk a écrit :
> > > Booting it might fine, but CLOCK_TICK_RATE will be wrong...
> >
> > PIT_TICK_RATE is overriden specificaly for R321x in
> > incl
Hi
Since upgrading to 2.6.25-rc1 I see filesystem corruption on my XFS
filesystem. I can reproduce this by doing "git reset --hard v2.6.25-rc1"
on a git checkout which is on some other revision. Git outputs strange
error messages (like file xxx is a directory when xxx really is a file)
and sometim
Hi!
> > velocity_suspend() seems to be at fault.
>
> (gdb) l *(velocity_suspend+0x37)
> 0xc0244665 is in velocity_suspend (drivers/net/via-velocity.c:3399).
> 3394 if(!netif_running(vptr->dev))
> 3395 return 0;
> 3396
> 3397 netif_device_detach(vptr->dev);
> 3
> > > > > ==> LOCKDEP feature is evidently missing:
> > > > > spin_lock_irq_nested(lock_ptr, lock_class)
> > > >
> > > > This rant is more lines than adding the API :-/ the reason for it not
> > > > being there is simple, it wasn't needed up until now.
> > >
> > > I suspected that
Rename Memory Controller to Memory Resource Controller. Reflect the same
changes in the CONFIG definition for the Memory Resource Controller.
Group together the config options for Resource Counters and Memory
Resource Controller.
This code has been compile tested with the Memory Resource Control
A boot option for the memory controller was discussed on lkml. It is a good
idea to add it, since it saves memory for people who want to turn off the
memory controller.
By default the option is on for the following two reasons
1. It provides compatibility with the current scheme where the memor
Hi!
Alan thinks that `subj` is correct...
> > > > At the very least, you'd need rmb() before reading it and wmb() after
> > > > writing to it, but I'm not sure if that's enough on every obscure
> > > > architecture out there.
> > >
> > > No, neither one is needed because of the way suspending_ta
On Mon, Feb 25, 2008 at 11:54 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > Isn't the resolution Michael is suggesting is, "use the different driver"?
>
> I have two resolutions. One being:
> rmmod b44
> rmmod ssb
> modprobe bcm43xx
> modprobe b44
>
> The other being: Wait for 2.6.25 and
On Sat, Feb 23, 2008 at 10:31:01AM -0800, Dave Hansen wrote:
> > > - 4 bits for the page size, with 0 meaning native page size (4k on x86,
> > > 8k on alpha, ...) and values 1-15 being specific to the architecture
> > > (I used 1 for 2M, 2 for 4M and 3 for 1G for x86)
>
> "Native page size" pr
On Monday 25 February 2008 13:11:04 Pekka Enberg wrote:
> On Mon, Feb 25, 2008 at 11:54 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > > Isn't the resolution Michael is suggesting is, "use the different
> > driver"?
> >
> > I have two resolutions. One being:
> > rmmod b44
> > rmmod ssb
> >
Subject: sched: revert load_balance_monitor()
The following commit causes a number of serious regressions:
commit 6b2d7700266b9402e12824e11e0099ae6a4a6a79
Author: Srivatsa Vaddagiri <[EMAIL PROTECTED]>
Date: Fri Jan 25 21:08:00 2008 +0100
sched: group scheduler, fix fairness of cpu band
On Mon, 25 Feb 2008, Michael Buesch wrote:
> > Neither of which seem like acceptable solutions for a 2.6.23 -> 2.6.24
> > _regression_. Or maybe I am just too naive to believe Linus' statement
> > on not letting the kernel regress...
>
> So, please sign-off the patch that we have, if you think it'
On Mon, Feb 25, 2008 at 12:50:22PM +0100, Ingo Molnar wrote:
>
> * Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > > What i do against build breakage is randconfig testing. That catches
> > > far more build breakage than a few limited number of defconfigs
> > > would ever.
> >
> > How do you test
On Monday, 25 of February 2008, Zdenek Kabelac wrote:
> Hi
Hi,
[CCs restored, added CC to Dave]
> I'm finally going to test some kernel - because I'd been trying it
> against the HEAD - but unfortunately it looks like there is something
> seriously broken with -rc3 and sata merge - anyway - I'm
On Tue, 19 Feb 2008, Greg KH wrote:
> On Mon, Feb 18, 2008 at 09:52:25PM +0100, Guennadi Liakhovetski wrote:
> > Booting an x86 SMP PC with todays git-snapshot or just with 2.6.25-rc2
> > getting the following warnings (with a bit of context):
>
> Can you try enabling CONFIG_DEBUG_KOBJECT and se
* Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > the existing 32-bit and 64-bit defconfigs should be enough for that.
> > For better/full coverage, randconfig should be used.
>
> The two big problems with randconfigs are:
> - either you build each .config both with and without your patch or you
>
On Mon, Feb 25, 2008 at 3:25 PM, Pekka J Enberg <[EMAIL PROTECTED]> wrote:
> On Mon, 25 Feb 2008, Michael Buesch wrote:
> > > Neither of which seem like acceptable solutions for a 2.6.23 -> 2.6.24
> > > _regression_. Or maybe I am just too naive to believe Linus' statement
> > > on not letting t
This is a pair of Xen para-virtual frontend device drivers:
drivers/video/xen-fbfront.c provides a framebuffer, and
drivers/input/xen-kbdfront provides keyboard and mouse.
The backends run in dom0 user space.
Differences since last post:
* Required patch fixing 32-on-64 xen-blkfront included.
*
Frontends are expected to write their protocol ABI to xenstore. Since
the protocol ABI defaults to the backend's native ABI, things work
fine without that as long as the frontend's native ABI is identical to
the backend's native ABI. This is not the case for xen-blkfront
running 32-on-64, because
Deferred I/O was utterly broken. Reading the mmap()ed framebuffer
worked, but writing it made the VM endlessly invoke
vm_ops.page_mkwrite(). That happened because we failed to set
page->mapping and page->index.
The fix is to set them, and clean up properly before the framebuffer
gets released.
This is a pair of Xen para-virtual frontend device drivers:
drivers/video/xen-fbfront.c provides a framebuffer, and
drivers/input/xen-kbdfront provides keyboard and mouse.
The backends run in dom0 user space.
The two drivers are not in two separate patches, because the
intermediate step (one driv
On Mon, Feb 25, 2008 at 01:57:07PM +0100, Ingo Molnar wrote:
>
> * Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > > the existing 32-bit and 64-bit defconfigs should be enough for that.
> > > For better/full coverage, randconfig should be used.
> >
> > The two big problems with randconfigs are:
>
On Mon, 2008-02-25 at 03:21 -0800, David Brownell wrote:
> > > > > > ==> LOCKDEP feature is evidently missing:
> > > > > > spin_lock_irq_nested(lock_ptr, lock_class)
> > > > >
> > > > > This rant is more lines than adding the API :-/ the reason for it not
> > > > > being there is
Hi,
I'm currently stuck between Kernel LVM and DRBD, as I'm using Kernel
2.6.24.2 with DRBD 8.2.5 on top of an LVM2 device (LV).
-LVM2/device mapper doesn't support write barriers
-DRBD uses blkdev_issue_flush() to flush its metadata to disk.
On a no-barrier-device, DRBD should receive EOPNOTSUP
On Monday 25 February 2008, Brad Rosser wrote:
[...]
> Bart wrote:
>
> > Does the following patch help?
> >
> > [ It makes ireason handling for REQ_TYPE_ATA_PC requests be the same as
> > for other request types so "ireason == 1" quirk is used if needed. ]
>
> I tried to apply the patch but fai
Hi!
This is a patch (very ugly, assumes you have just one disk) to bring
powersaving to AHCI. You need Alan's SCSI autosuspend (attached) patch
as a base.
It saves .5W compared to config with disk spinning, and even .15W
compared to hdparm -y... on my thinkpad x60 anyway.
It is also mandatory fi
* Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > so if an arguably sane testing method "only" works on x86 then the
> > right solution is to fix the other architectures to be sanely
> > testable too.
>
> If you want to fix them I won't stop you...
>
> Until they are fixed I'm staying at using the
Return ERR even if there are pending data, but hw is not running. Do not
decrement count in poll, do it in ioctl, where data are actually read.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
drivers/misc/phantom.c | 10 ++
1 files changed, 6 insertions(+), 4 deletions(-)
diff --git
Openhaptics uses pointers in _IOC() macros, implement compat for them. Also
add _IOC alternatives which are not 32/64 bit dependent (structures
passed through aren't yet) -- libphantom will use them.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
drivers/misc/phantom.c | 24
i read that you shouldn't write a testmail i need to see if this works..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.t
Dmitry Adamushko <[EMAIL PROTECTED]> wrote:
> (3)
>
> LOCK
>
> LOAD(a)
> MODIFY(b)
>
> UNLOCK
>
> and this last one is a problem. No?
I assume you meant:
LOCK
LOAD(b)
MODIFY(a)
UNLOCK
David
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
On Mon, Feb 25, 2008 at 02:45:49PM +0100, Ingo Molnar wrote:
>...
> > > I've seen architectures that were build-tested for the _first time_
> > > at around 2.6.24-rc8...
> >
> > That can't be true.
> >
> > Can you name what architectures you think of and why you think noone
> > tried to compile
Hi Ingo,
These patches change the fairness model as discussed in
http://lkml.org/lkml/2008/1/30/634
Patch 1 -> Changes the fairness model
Patch 2 -> Allows one to create multiple levels of cgroups
The second patch is not very good with SMP yet, that is the next TODO.
Also it changes the behaviou
This patch allows tasks and groups to exist in the same cfs_rq. With this
change the CFS group scheduling follows a 1/(M+N) model from a 1/(1+N)
fairness model where M tasks and N groups exist at the cfs_rq level.
Signed-off-by: Dhaval Giani <[EMAIL PROTECTED]>
Signed-off-by: Srivatsa Vaddagiri <[
1 - 100 of 544 matches
Mail list logo
