On Sun, 2007-03-25 at 22:08 +0200, Jörn Engel wrote:
> And there is no fundamental reason why UBI should export blocks with
> non-power-of-two sizes.
False. There is.
> UBI currently consists of two parts that are
> intimately intertwined in the current implementation, but have
> relatively lit
On Mon, 26 Mar 2007, Con Kolivas wrote:
On Monday 26 March 2007 09:01, Con Kolivas wrote:
On Monday 26 March 2007 03:14, malc wrote:
On Mon, 26 Mar 2007, Con Kolivas wrote:
On Monday 26 March 2007 01:19, malc wrote:
Erm... i just looked at the code and suddenly it stopped making any sense
at
On Mon, 26 Mar 2007 12:34:33 +0200 Eric Rannaud <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote:
> > On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <[EMAIL PROTECTED]> wrote:
> > > > If so, do you think I should labour on with
> > > > uevent-improve-err
On Mon, 26 Mar 2007 18:23:57 +0800 "Wu, Bryan" <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> As struct mm_struct vm_mm is hidden in struct vm_area_struct in NOMMU
> arch, this is a fixing method when compiling failure on blackfin arch.
>
> Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
> ---
>
> fs
On Mon, 26 Mar 2007, Wu, Bryan wrote:
> As struct mm_struct vm_mm is hidden in struct vm_area_struct in NOMMU
> arch, this is a fixing method when compiling failure on blackfin arch.
What compile error is that? I don't see any #ifdef around ->vm_mm for
struct vm_area_struct in .
On Mon, 26 Mar 2
2007/3/26, Thomas Gleixner <[EMAIL PROTECTED]>:
On Mon, 2007-03-26 at 08:45 +0200, Frédéric RISS wrote:
> Additional data point: I just tried with -rc5 and the issue is still
> present. The config I used for this test defines neither NO_HZ nor
> HIGH_RES_TIMERS.
Do you have CONFIG_HPET_TIMER ena
On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote:
> On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <[EMAIL PROTECTED]> wrote:
> > > If so, do you think I should labour on with
> > > uevent-improve-error-checking-and-handling.patch plus your fix, or should
> > > I
> > > drop the lot?
Hi,
Thanks for your reply.
>>3) Use "dirty_ratio" as the blocking ratio. And add
>> "start_writeback_ratio", and start writeback at
>> start_writeback_ratio(default:90) * dirty_ratio / 100 [%].
>> In this way, specifying blocking ratio can be done in the same way
>> as current kernel, but
On Fri, 23 Mar 2007 12:08:59 -0400 Mimi Zohar <[EMAIL PROTECTED]> wrote:
> This is a set of updates to the integrity service framework, previously
> accepted into -mm, EVM a new integrity service provider, and a new LSM
> module called Integrity Based Access Control(IBAC), a sample consumer of
>
Hi folks,
As struct mm_struct vm_mm is hidden in struct vm_area_struct in NOMMU
arch, this is a fixing method when compiling failure on blackfin arch.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
kernel/signal.c |4
1 file changed, 4 insertions(+)
Index: linux-2.6/kernel/signal.c
Hi folks,
As struct mm_struct vm_mm is hidden in struct vm_area_struct in NOMMU
arch, this is a fixing method when compiling failure on blackfin arch.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
fs/revoke.c | 22 +++---
1 file changed, 15 insertions(+), 7 deletions(-)
In
Hi folks,
This patch cleanup blackfin SPI driver code and fix some coding style
problems.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
drivers/spi/spi_bfin5xx.c | 322 +-
1 file changed, 179 insertions(+), 143 deletions(-)
Index: linux-2.6/driver
Hi folks,
This patch fix a printing error bug when reboot kernel mounting on SPI
flash.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
drivers/spi/spi_bfin5xx.c |9 -
1 file changed, 9 deletions(-)
Index: linux-2.6/drivers/spi/spi_bfin5xx.c
===
hm, on a T60, after suspend/resume, i get an e1000 timeout:
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX/TX
e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Tx Queue <0>
TDH
TDT
next_to_use
Hi folks,
Replacing class_dev to directly using rtc_dev.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
drivers/rtc/rtc-bfin.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/drivers/rtc/rtc-bfin.c
===
Hi folks,
According to Paul's review, this patch cleanup the
include/asm-blackfin/cache.h comments.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
include/asm-blackfin/cache.h | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
Index: linux-2.6/include/asm-blackfin/
Hi folks,
This patch fix a printing error bug when reboot kernel mounting on SPI
flash.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
arch/blackfin/mach-bf533/boards/cm_bf533.c |2 +-
arch/blackfin/mach-bf533/boards/ezkit.c |2 +-
arch/blackfin/mach-bf533/boards/stamp.c
Hi folks,
THis patch fixed including wrong header file when compiling in
2.6.21-rc4-mm.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
arch/blackfin/kernel/flat.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/arch/blackfin/kernel/flat.c
Hi folks,
This patches replace firmware disk mode according to include/linux/pm.h
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
arch/blackfin/mach-common/pm.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.x/arch/blackfin/mach-common/pm.c
=
Hi folks,
This patch adds kdebug.h header file to blackfin architecture.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
include/asm-blackfin/kdebug.h |1 +
1 file changed, 1 insertion(+)
Index: linux-2.6/include/asm-blackfin/kdebug.h
==
Hi folks,
This patch fix a bug about struct dmasg packed missing bug.
Using __attribute__ instead of pragma.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
include/asm-blackfin/dma.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/include/asm-blackfin/dma.h
=
On Mon, 2007-03-26 at 11:51 +0200, Jörn Engel wrote:
> Are you sure? Do you have any specs or similar that state this?
>
> So far I have only encountered this limitation by word of mouth. And
> such a myth coming from ECC effects is nothing that would surprise
> me.
See pp 6 and 31 of http://d
Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> Hrm... I'm not sure I like the io_* name, I think it's even more
> confusing, people will never know when to use what ...
I'd've thought it more obvious, but given there are several types of I/O, some
of which might require different barriering
On Mon, 26 Mar 2007 11:32:47 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> Stopping writers which have idle queues is completely unproductive,
> and that is basically what the current algorithm does.
This is because the kernel permits all of its allotment of dirty+writeback
pages to be dirty+
Lennert Buytenhek <[EMAIL PROTECTED]> wrote:
> Does everybody agree on these semantics, though? At least David seems
> to think that mb/rmb/wmb aren't required to order normal memory accesses
> against each other..
Ummm... I've just realised that your statement here is ambiguous. When you
say
The sysctl handler for min_free_kbytes calls setup_per_zone_pages_min()
on read or write. This function iterates through every zone and calls
spin_lock_irqsave() on the zone LRU lock. When reading min_free_kbytes, this
is a total waste of time that disables interrupts on the local processor. It
mig
On Mon, 2007-03-26 at 10:45 +0100, David Woodhouse wrote:
> On Mon, 2007-03-26 at 03:04 +0200, Jörn Engel wrote:
> > That limitation stems from ECC and ECC is done in software. Currently
> > everyone and his dog is doing ECC in chunks of 256 bytes on NAND. So
> > your minimum write size is 256 by
Adrian Bunk wrote:
> Subject: NCQ problem with ahci and Hitachi drive (ACPI related)
> References : http://lkml.org/lkml/2007/3/4/178
> http://lkml.org/lkml/2007/3/9/475
> Submitter : Mathieu Bérard <[EMAIL PROTECTED]>
> Handled-By : Tejun Heo <[EMAIL PROTECTED]>
> Status : p
Andrew Morton <[EMAIL PROTECTED]> writes:
> On Sat, 24 Mar 2007 10:17:24 +0100 Andreas Schwab <[EMAIL PROTECTED]> wrote:
>
>> I'm getting this panic when loading sata-vsc on a SGI Prism:
>
> With what kernel?
It's still the same with 2.6.21-rc5.
>> Bisection has identified this patch (together w
Adrian Bunk wrote:
> Subject: ThinkPad R60: suspend to disk broken
> References : http://lkml.org/lkml/2007/3/23/74
> Submitter : Marcus Better <[EMAIL PROTECTED]>
> Status : submitter tries to bisect
I just tried -rc5. Now suspend to disk seems to work. I think the XFS
workqueue patch f
On Wed, 21 Mar 2007 10:54:34 +0100 [EMAIL PROTECTED] wrote:
> This patch modifies futex_wait() to use an hrtimer + schedule() in place of
> schedule_timeout().
>
> schedule_timeout() is tick based, therefore the timeout granularity is
> the tick (1 ms, 4 ms or 10 ms depending on HZ). By using a
Ingo Molnar wrote:
> * Nicolas Boichat <[EMAIL PROTECTED]> wrote:
>
>
>>> I found out which commit seems to cause these bugs:
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d04f41e35343f1d788551fd3f753f51794f4afcf
>>>
>>> The latest GIT without this commit works
On Mon, 26 March 2007 10:45:57 +0100, David Woodhouse wrote:
>
> No, on NAND flash it's a limitation of the hardware. The number of write
> cycles you can perform to a given page is limited. Exceed it and the
> contents of that page become undefined due to leakage, until you next
> erase it.
Are
> patch did, though, it was that way already before. But otoh with the
> legacy flag set in progif, these BARs *should* be I/O ones...
They *are* I/O resources. The register value loaded by the BIOS or
hardware at start up is undefined and the "is memory" check is actually
wrong.
Doesn't explain
At Fri, 23 Mar 2007 15:22:46 -0400,
Chuck Ebbert wrote:
>
> Takashi Iwai wrote:
> > At Tue, 20 Mar 2007 17:08:48 +0100,
> > I wrote:
> >> At Tue, 20 Mar 2007 12:05:07 -0400,
> >>>
> >>> http://lkml.org/lkml/2006/12/3/9
> >> This is a different problem.
> >> A known workaround is to provide probe_m
> > Well, not a picture, but a sort of indented call trace:
> >
> > [some process, which has a fuse file writably mmaped]
> > write fault on upper filesystem
> > balance_dirty_pages
> > loop...
> > submit write requests
>
> This, I assume, is the upper fs
>
> > --
On Mon, 2007-03-26 at 03:04 +0200, Jörn Engel wrote:
> That limitation stems from ECC and ECC is done in software. Currently
> everyone and his dog is doing ECC in chunks of 256 bytes on NAND. So
> your minimum write size is 256 bytes _if you care about ECC_. If you
> don't care, you can write s
> > This patch adds support for finding out the current file position,
> > open flags and possibly other info in the future.
> > These new entries are added:
> >
> > /proc/PID/fdinfo/FD
> > /proc/PID/task/TID/fdinfo/FD
> > For each fd the information is provided in the following format:
> > po
Linus,
Please pull 'master' from:
git://git.kernel.org:/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
master
Basically we have some fixes at IR code, a Kconfig fix when Radio is
selected, some lock fixes at DVB core, Secam on saa7115 will now work
properly, a fix on msp34xx detection an
> > > > This is a slightly different take on the fix for the deadlock in fuse
> > > > with dirty balancing. David Chinner convinced me, that per-bdi
> > > > counters are too expensive, and that it's not worth trying to account
> > > > the number of pages under writeback, as they will be limited by
On Mon, 26 Mar 2007 11:20:11 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > > > > It also makes a deadlock possible when one filesystem is writing data
> > > > > through another, and the balance_dirty_pages() for the lower
> > > > > filesystem is stalling the writeback for the upper filesyste
* Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> The current sysfs support of clockevents does not obey the "only one
> value per file" rule.
>
> The real fix is not 2.6.21 material. Therefor remove the sysfs support
> for now.
>
> Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Acked-by: I
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> There's various fixes here, ranging from some architecture updates
> (ia64, ARM, MIPS, SH, Sparc64) to KVM, networking and network drivers.
here's a new v2.6.20 -> v2.6.21 forcedeth.c regression:
in the last week or so i've been seeing sporadic und
On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <[EMAIL PROTECTED]> wrote:
> On Fri, 23 Mar 2007 21:06:18 -0800,
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Would I be right in guessing that this was all triggered by
> > uevent-improve-error-checking-and-handling.patch?
>
> Looks like it,
> > > > It also makes a deadlock possible when one filesystem is writing data
> > > > through another, and the balance_dirty_pages() for the lower
> > > > filesystem is stalling the writeback for the upper filesystem's
> > > > data (*).
> > >
> > > I still don't understand this one. I got lost wh
The current sysfs support of clockevents does not obey the "only one
value per file" rule.
The real fix is not 2.6.21 material. Therefor remove the sysfs support
for now.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
index 6
On Mon, 2007-03-26 at 08:45 +0200, Frédéric RISS wrote:
> Additional data point: I just tried with -rc5 and the issue is still
> present. The config I used for this test defines neither NO_HZ nor
> HIGH_RES_TIMERS.
Do you have CONFIG_HPET_TIMER enabled and does the box have one ?
If yes, can you p
Andrew Morton wrote:
[...skip]
> The problem is memory reclaim. A number of schemes which have been
> proposed require a per-container page reclaim mechanism - basically a
> separate scanner.
>
> This is a huge, huge, huge problem. The present scanner has been under
> development for over a
On Sun, 25 Mar 2007 23:37:08 -0700 (PDT) David Rientjes <[EMAIL PROTECTED]>
wrote:
> Date: Sun, 25 Mar 2007 23:07:43 -0800
> From: Zachary Amsden <[EMAIL PROTECTED]>
>
> If you actually clear the bit, you need to:
>
> + pte_update_defer(vma->vm_mm, addr, ptep);
>
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> my first quick guess was to extend np->priv locking to the whole of
> nv_start_xmit/nv_start_xmit_optimized - while that appeared to make
> the crash a bit less likely, it did not prevent it. So there must be
> some other, more fundamental problem be
On Fri, 23 Mar 2007 21:06:18 -0800,
Andrew Morton <[EMAIL PROTECTED]> wrote:
> Would I be right in guessing that this was all triggered by
> uevent-improve-error-checking-and-handling.patch?
Looks like it, since it passed the uevent failures to the upper layer.
> If so, do you think I should lab
On Mon, 26 Mar 2007 10:26:18 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > > This is a slightly different take on the fix for the deadlock in fuse
> > > with dirty balancing. David Chinner convinced me, that per-bdi
> > > counters are too expensive, and that it's not worth trying to account
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > my first quick guess was to extend np->priv locking to the whole of
> > nv_start_xmit/nv_start_xmit_optimized - while that appeared to make
> > the crash a bit less likely, it did not prevent it. So there must be
> > some other, more fundamental pro
On Sun, 2007-03-25 at 16:08 -0700, Linus Torvalds wrote:
> Those timer changes ended up much more painful than anybody wished for,
> but big thanks to Thomas Gleixner for being on it like a weasel on a dead
> rat, and the regression list has kept shrinking.
Why certainly ! I caused them, so I ha
Marcel Holtmann wrote:
that is the whole point. The slash was never meant to be used. It was
designed to take a filename or a pattern that will be later matched by
userspace. However some developers are now trying to abuse this since
the simple firmware helper script matches this directly to a fi
On Monday 26 March 2007 15:11, Al Boldi wrote:
> Con Kolivas wrote:
> > Ok this one is heavily tested. Please try it when you find the time.
>
> It's better, but still skewed. Try two chew.c's; they account 80% each.
>
> > ---
> > Currently we only do cpu accounting to userspace based on what is
>
On Sun, Mar 25, 2007 at 08:24:18PM -0700, Paul E. McKenney wrote:
> > > > > [ background: On ARM, SMP synchronisation does need barriers but
> > > > > device
> > > > > synchronisation does not. The question is that given this, whether
> > > > > mb() and friends can be NOPs on ARM or not (i.e
P.S. (I've not studied the hotplug code) When a cpu is hot-unplugged,
are it's runqueues and whatnot deallocated? (i should just go look, but
by the time i get around to it, some nice person may have already put an
answer in my mailbox;)
-Mike
P.S.#2: not only bitmap are zeroed, task
> >
> > Remove this function. It's purpose was to limit the global number of
> > writeback pages from submitted by direct reclaim. But this is equally
> > well accomplished by limited queue lengths. When this function was
> > added, the device queues had much larger default lengths (8192
> > re
Hi Arjan,
> > > > Is the tool you mentioned last June [1] available for splitting up the
> > > > old firmware files to the new format (eg
> > > > /lib/firmware/intel-ucode/06-0d-06), or are updates available from
> > > > Intel (or otherwise) in this new format?
> > > Yes, we are preparing the new
Hi Li,
> --
> HID bus design overview.
> --
>
> A. Terms.
>
> The device of an driver: this mean the device that this driver matched.
>
> B. Design.
>
> As we discussed before, The entire HID subsystem is divid
> > This is a slightly different take on the fix for the deadlock in fuse
> > with dirty balancing. David Chinner convinced me, that per-bdi
> > counters are too expensive, and that it's not worth trying to account
> > the number of pages under writeback, as they will be limited by the
> > queue a
On Mon, 2007-03-26 at 17:19 +1000, Con Kolivas wrote:
> On Monday 26 March 2007 15:00, Mike Galbraith wrote:
> > On Mon, 2007-03-26 at 11:00 +1000, Con Kolivas wrote:
> > > This is just for testing at the moment! The reason is the size of this
> > > patch.
> >
> > (no testing done yet, but I have a
On Sun, 25 Mar 2007, Andrew Morton wrote:
> On Sun, 25 Mar 2007 16:28:39 -0400 (EDT) "Robert P. J. Day" <[EMAIL
> PROTECTED]> wrote:
>
> > Delete the never-compiled source file drivers/input/power.c, and
> > remove its entry from the corresponding Makefile, as there is no
> > Kconfig file that re
Hi,
On Sun, Mar 25, 2007 at 06:30:34PM +0200, Folkert van Heusden wrote:
> > > I'd say "feature", glibc's malloc also returns an address on
> > > malloc(0).
> > >
> > This is implementation defined-the standard allows for return of either
> > null or an address.
>
> Entirely for entertainment: A
I2O subsystem has been broken in mainstream several months ago (after 2.6.18).
The following patch from Jens Axboe splits struct request ->flags into two
parts: cmd_type and cmd_flags
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4aff5e2333c9a1609662f2091f55c3f6fffdad3
301 - 366 of 366 matches
Mail list logo
