Re: [PATCH 4/6] Record how many zones can be safely skipped in the zonelist

Is there any performance improvement because of this patch? It looks like processing got more expensive since an additional cacheline needs to be fetches to get the skip factor. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: kfree(0) - ok?

On Fri, 17 Aug 2007, Andrew Morton wrote: > On Wed, 15 Aug 2007 05:12:41 +0530 (IST) > Satyam Sharma <[EMAIL PROTECTED]> wrote: > > > [PATCH] {slub, slob}: use unlikely() for kfree(ZERO_OR_NULL_PTR) check > > > > Considering kfree(NULL) would normally occur only in error paths and > >

Re: [PATCH]: proc: export a processes resource limits via proc/

On Fri, Aug 17, 2007 at 12:45:47PM -0700, Andrew Morton wrote: > On Fri, 17 Aug 2007 06:59:18 -0400 > Neil Horman <[EMAIL PROTECTED]> wrote: > > > Currently, there exists no method for a process to query the resource > > limits of another process. They can be inferred via some mechanisms but >

Re: Early printk behaviour

On Fri 17 Aug 2007 03:49, Gerd Hoffmann pondered: > Mike Frysinger wrote: > >> Hmm, sort of, although I didn't think about the case of no real console > >> replacing the early console. The intention of the patch is to have a > >> smooth handover from the boot console to the real console. And,

Re: [PATCH RFC] CPU hotplug support for preemptible RCU

On Thu, Aug 16, 2007 at 06:26:18PM -0700, Paul E. McKenney wrote: > On Tue, Aug 14, 2007 at 04:41:16PM -0700, Paul E. McKenney wrote: > > Hello! > > > > Work in progress, not for inclusion. > > > > The attached patch passes multiple hours of rcutorture while hotplugging > > CPUs every ten

Re: [PATCH 2/6] Use one zonelist that is filtered instead of multiple zonelists

On Fri, 17 Aug 2007, Mel Gorman wrote: > +/* Returns the first zone at or below highest_zoneidx in a zonelist */ > +static inline struct zone **first_zones_zonelist(struct zonelist *zonelist, > + enum zone_type highest_zoneidx) > +{ > + struct zone **z; > +

Re: [PATCH] select: fix sys_select to not leak ERESTARTNOHAND to userspace

On Fri, Aug 17, 2007 at 11:41:20AM -0400, John Blackwood wrote: > Hi Neil, > > We've been having problems with this select patch change. > > Specifically -- previously, when a ptrace attach was done to a task > blocked in a select() call and that task had a timeout value, > the task would

[PATCH] Fix section mismatch in the Adaptec DPT SCSI Raid driver

Fix section mismatch in the Adaptec DPT SCSI Raid driver. Signed-off-by: Joe Korty <[EMAIL PROTECTED]> Index: 2.6.23-rc3-git1/drivers/scsi/dpt_i2o.c === --- 2.6.23-rc3-git1.orig/drivers/scsi/dpt_i2o.c 2007-08-17 16:36:05.0

how to add debug information into the vmlinux

Hello everyone, I am trying to port kernel 2.6.19 onto my system.so I need the c code , which can show me where the program is running. I add -g when I compile it. after I got the vmlinux( uncompressed) I used arm-none-eabi-objcopy --change-addresses 0x4000 to change the start address. it

Re: kfree(0) - ok?

On Fri, 17 Aug 2007, Andrew Morton wrote: > are we seeing a pattern here? We could stick the unlikely inside > ZERO_OR_NULL_PTR() itself. That's a little bit sleazy though - there might > be future callsites at which it is likely, who knows? Thought about that myself but then there would be a

Re: [PATCH 1/7] Simple Performance Counters: Core Piece

On Fri, 17 Aug 2007, Mathieu Desnoyers wrote: > Actually, get_cycles() at least on some AMD cpus, do not synchronize the > core, which can skew the results. You might want to use > get_cycles_sync() there. get_cycle() results as used here are bound to a single processor. If we end up on a

Re: [PATCH 7/7] Simple Performance Counters: SLUB instrumentation

On Fri, 17 Aug 2007, Mathieu Desnoyers wrote: > Why do you printk inside the timing period ? Filling the printk buffers > or outputting on things such as serial console could really hurt your > results. It was easier to code? > I hope you run your system with idle=poll and without frequency

Re: [PATCH 00/23] per device dirty throttling -v9

On Fri, 17 Aug 2007, Peter Zijlstra wrote: > Currently we do: > dirty = total_dirty * bdi_completions_p * task_dirty_p > > As dgc pointed out before, there is the issue of bdi/task correlation, > that is, we do not track task dirty rates per bdi, so now a task that > heavily dirties on one

RE: [PATCH 02/12] Blackfin arch: Add label to call new GPIO API

>-Original Message- >From: David Brownell [mailto:[EMAIL PROTECTED] > >On Friday 17 August 2007, Mike Frysinger wrote: >> On 8/17/07, David Brownell <[EMAIL PROTECTED]> wrote: >> > ... >> > Just for the record, this is an unusual way to use these calls. >> > >> > Other platforms

Re: [PATCH]: proc: export a processes resource limits via proc/

On Fri, 17 Aug 2007 12:45:47 PDT, Andrew Morton said: > On Fri, 17 Aug 2007 06:59:18 -0400 > Neil Horman <[EMAIL PROTECTED]> wrote: > > > Currently, there exists no method for a process to query the resource > > limits of another process. They can be inferred via some mechanisms but > > they >

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Friday 17 August 2007, Jan Engelhardt wrote: > >> We exchanges several mails a few weeks ago after the Debian bug caused > >> by a modprobe loop. > > > >Which has been fixed for some time now; it was caused by legacy > >drivers, which are incapable of hotplugging. > > Speaking of which ...

Re: [PATCH 02/12] Blackfin arch: Add label to call new GPIO API

On 8/17/07, Mike Frysinger <[EMAIL PROTECTED]> wrote: > as Michael pointed out, in the Blackfin world we tend to keep things > very dynamic as we have dev systems which allow for dropping in of > optional cards at will, so doing this in the bootloader is way too > inflexible. oh, and another

Re: [PATCH 02/12] Blackfin arch: Add label to call new GPIO API

On 8/17/07, David Brownell <[EMAIL PROTECTED]> wrote: > On Friday 17 August 2007, Mike Frysinger wrote: > > On 8/17/07, David Brownell <[EMAIL PROTECTED]> wrote: > > > ... > > > Just for the record, this is an unusual way to use these calls. > > > > > > Other platforms completely decouple these

[PATCH 6/6] Do not use FASTCALL for __alloc_pages_nodemask()

One PPC64 machine using gcc 3.4.6 the machine fails to boot when __alloc_pages_nodemask() uses the FASTCALL calling convention. It is not clear why this machine in particular is affected as other PPC64 machines boot. The only usual aspect of the machine is that it has memoryless nodes but I

[PATCH 4/6] Record how many zones can be safely skipped in the zonelist

This patch is mainly the work of Kamezawa-san. As there is only one zonelist, it must be filtered for zones that are unusable by the GFP flags. As the zonelists very rarely change during the lifetime of the system, it is known in advance how many zones can be skipped from the beginning of the

[PATCH 5/6] Filter based on a nodemask as well as a gfp_mask

The MPOL_BIND policy creates a zonelist that is used for allocations belonging to that thread that can use the policy_zone. As the zonelist is already being filtered based on a zone id, this patch adds a version of __alloc_pages() that takes a nodemask for further filtering. This eliminates the

[PATCH 3/6] Embed zone_id information within the zonelist->zones pointer

Using one zonelist per node requires very frequent use of zone_idx(). This is costly as it involves a lookup of another structure and a substraction operation. struct zone is aligned on a node-interleave boundary so the pointer values of plenty of 0's at the least significant bits of the address.

[PATCH 2/6] Use one zonelist that is filtered instead of multiple zonelists

Currently a node has a number of zonelists, one for each zone type in the system. Based on the zones allowed by a gfp mask, one of these zonelists is selected. All of these zonelists occupy memory and consume cache lines. This patch replaces the multiple zonelists in the node with a single

[PATCH 1/6] Use zonelists instead of zones when direct reclaiming pages

The allocator deals with zonelists which indicate the order in which zones should be targeted for an allocation. Similarly, direct reclaim of pages iterates over an array of zones. For consistency, this patch converts direct reclaim to use a zonelist. No functionality is changed by this patch.

[PATCH 0/6] Use one zonelist per node instead of multiple zonelists v4

Biggest changes are altering the embedding of zone IDs so that the type is unsigned long instead of struct zone * and the removal of MPOL_BIND-specific zonelists and filering based on node data instead. The biggest concern is the last patch where FASTCALL doesn't appear to do the right thing in

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, Aug 17, 2007 at 12:49:00PM -0700, Arjan van de Ven wrote: > > On Fri, 2007-08-17 at 12:49 -0700, Paul E. McKenney wrote: > > > > What about reading values modified in interrupt handlers, as in your > > > > "random" case? Or is this a bug where the user of atomic_read() is > > > >

Re: [PATCH 02/12] Blackfin arch: Add label to call new GPIO API

On Friday 17 August 2007, Mike Frysinger wrote: > On 8/17/07, David Brownell <[EMAIL PROTECTED]> wrote: > > ... > > Just for the record, this is an unusual way to use these calls. > > > > Other platforms completely decouple these issues from the > > IRQ infrastructure ... doing the pinmux and gpio

Re: [draft] Blackfin Early Printk implmentation

On Fri 17 Aug 2007 13:59, Sam Ravnborg pondered: > That seems to explain why I could not follow your code changes. > A more fine grained splitup would have helped here. Sorry - see below. These aren't proper patches anymore, since it was faster for me to split them by hand (but should be OK for

RE: [PATCH 01/12] Blackfin arch: add peripheral resource allocation support

Hi Dave, >-Original Message- >From: David Brownell [mailto:[EMAIL PROTECTED] >Sent: Freitag, 17. August 2007 20:12 >To: Bryan Wu >Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org; >[EMAIL PROTECTED]; Michael Hennerich >Subject: Re: [PATCH 01/12] Blackfin arch: add peripheral resource

Re: [PATCH] wait_task_zombie: don't fight with non-existing race with a dying ptracee

> (textually depends on > wait_task_zombie-remove-unneeded-child-signal-check.patch) > > The "p->exit_signal == -1 && p->ptrace == 0" check and the comment are bogus. > We already did exactly the same check in eligible_child(), we did not drop > tasklist_lock since then, and both variables need

Re: [PATCH] Make rcutorture RNG use temporal entropy

On Fri, Aug 17, 2007 at 11:53:56AM -0700, Andrew Morton wrote: > On Wed, 15 Aug 2007 19:49:04 -0700 > "Paul E. McKenney" <[EMAIL PROTECTED]> wrote: > > > Repost of http://lkml.org/lkml/2007/8/10/472 made available by request. > > > > The locking used by get_random_bytes() can conflict with the >

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, 2007-08-17 at 12:49 -0700, Paul E. McKenney wrote: > > > What about reading values modified in interrupt handlers, as in your > > > "random" case? Or is this a bug where the user of atomic_read() is > > > invalidly expecting a read each time it is called? > > > > the interrupt handler

Re: [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP ports from the host TCP port space.

> > Isn't RDMA _part_ of the "software net stack" within Linux? > It very much is not so. This is just nit-picking. You can draw the boundary of the "software net stack" wherever you want, but I think Sean's point was just that RDMA drivers already are part of Linux, and we all want them to

Re: SVr4/SVID/SUS IPC conformance

On 17/08/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote: > > On Fri, 2007-08-17 at 19:18 +0200, Anton Arapov wrote: > > > > IPC code is good, EIDRM is justification of EINVAL. But neither SVr4 nor > > SVID \ > > documents EIDRM. Single Unix Specification mentions EINVAL but not EIDRM > > as

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Aug 17 2007 12:50, David Brownell wrote: >On Friday 17 August 2007, Kay Sievers wrote: >> On Fri, 2007-08-17 at 09:55 -0700, David Brownell wrote: >> > On Friday 17 August 2007, Kay Sievers wrote: >> > > Again, >> > >> > "Again"? >> >> We exchanges several mails a few weeks ago after the

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Friday 17 August 2007, Kay Sievers wrote: > On Fri, 2007-08-17 at 09:55 -0700, David Brownell wrote: > > On Friday 17 August 2007, Kay Sievers wrote: > > > Again, > > > > "Again"? > > We exchanges several mails a few weeks ago after the Debian bug caused > by a modprobe loop. Which has been

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, Aug 17, 2007 at 11:54:33AM -0700, Arjan van de Ven wrote: > > On Fri, 2007-08-17 at 12:50 -0600, Chris Friesen wrote: > > Linus Torvalds wrote: > > > > > - in other words, the *only* possible meaning for "volatile" is a purely > > >single-CPU meaning. And if you only have a single

Re: [PATCH]: proc: export a processes resource limits via proc/

On Fri, 17 Aug 2007 06:59:18 -0400 Neil Horman <[EMAIL PROTECTED]> wrote: > Currently, there exists no method for a process to query the resource > limits of another process. They can be inferred via some mechanisms but they > cannot be explicitly determined. Given that this information can be

[PATCH][kprobes] support kretprobe-blacklist

This patch introduces architecture dependent kretprobe blacklists to prohibit users from inserting return probes on the function in which kprobes can be inserted but kretprobes can not. Signed-off-by: Masami Hiramatsu <[EMAIL PROTECTED]> --- When a kretprobe is inserted in the entry of the

[PATCH] Reset current->pdeath_signal on SUID binary execution

Hi Linus, the attached patch fixes a flaw in the "parent process death signal" when executing SUID binaries. An unprivileged user may send arbitrary signal to a child process even if it is running with higher privileges. The idea to fix this issue is to reset pdeath_signal not only on fork, but

Re: [PATCH 02/12] Blackfin arch: Add label to call new GPIO API

On 8/17/07, David Brownell <[EMAIL PROTECTED]> wrote: > Again, the patch descriptions need work. This changes the > IRQ code (to add those labels). $SUBJECT doesn't mention IRQs, > neither does the description ... > > > On Tuesday 07 August 2007, Bryan Wu wrote: > > ---

[PATCH,RESEND] documentation: atomic_add_unless() doesn't imply mb() on failure

(the explicit ack/nack from maintainers is wanted). A "typical" implementation of atomic_add_unless() can return 0 immediately after the first atomic_read() (before doing cmpxchg). In that case it doesn't provide any barrier semantics. See include/asm-ia64/atomic.h as an example. We should

[PATCH] CIFS: check for granted memory

This patch adds just a check for granted memory to prevent possible NULL pointer usage. Signed-off-by: Cyrill Gorcunov <[EMAIL PROTECTED]> --- fs/cifs/sess.c |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/fs/cifs/sess.c b/fs/cifs/sess.c index 2ea027d..892be9b 100644

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, 17 Aug 2007, Chris Friesen wrote: > > I assume you mean "except for IO-related code and 'random' values like > jiffies" as you mention later on? Yes. There *are* valid uses for "volatile", but they have remained the same for the last few years: - "jiffies" - internal

Re: [PATCH 1/2] Add scaled time to taskstats based process accounting

Andrew Morton wrote: > On Fri, 17 Aug 2007 11:09:41 +1000 > Michael Neuling <[EMAIL PROTECTED]> wrote: > >> This adds items to the taststats struct to account for user and system >> time based on scaling the CPU frequency and instruction issue rates. >> >> Adds account_(user|system)_time_scaled

Re: Thinking outside the box on file systems

[EMAIL PROTECTED] wrote: I suspect Kyle is not quite correct - it's probably the case that you don't have to consider just the in-memory dentries, but *all* the descendent objects in the entire file system. If you have a clever proof that on-disk can't *possibly* be affected, feel free to

Re: [PATCH 1/2] Add scaled time to taskstats based process accounting

On Fri, 17 Aug 2007 11:09:41 +1000 Michael Neuling <[EMAIL PROTECTED]> wrote: > This adds items to the taststats struct to account for user and system > time based on scaling the CPU frequency and instruction issue rates. > > Adds account_(user|system)_time_scaled callbacks which architectures >

Re: SVr4/SVID/SUS IPC conformance

On Fri, 2007-08-17 at 19:18 +0200, Anton Arapov wrote: > > IPC code is good, EIDRM is justification of EINVAL. But neither SVr4 nor > SVID \ > documents EIDRM. Single Unix Specification mentions EINVAL but not EIDRM as > a \ > possible failure for shmctl(), so the current kernel behavior

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, 2007-08-17 at 12:50 -0600, Chris Friesen wrote: > Linus Torvalds wrote: > > > - in other words, the *only* possible meaning for "volatile" is a purely > >single-CPU meaning. And if you only have a single CPU involved in the > >process, the "volatile" is by definition pointless

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Sat, Aug 18, 2007 at 12:01:38AM +0530, Satyam Sharma wrote: > > > On Fri, 17 Aug 2007, Paul E. McKenney wrote: > > > On Fri, Aug 17, 2007 at 01:09:08PM +0530, Satyam Sharma wrote: > > > > > > On Thu, 16 Aug 2007, Paul E. McKenney wrote: > > > > > > > On Fri, Aug 17, 2007 at 07:59:02AM

Re: [PATCH] Make rcutorture RNG use temporal entropy

On Wed, 15 Aug 2007 19:49:04 -0700 "Paul E. McKenney" <[EMAIL PROTECTED]> wrote: > Repost of http://lkml.org/lkml/2007/8/10/472 made available by request. > > The locking used by get_random_bytes() can conflict with the > preempt_disable() and synchronize_sched() form of RCU. This patch changes

Re: [PATCH] lockdep: annotate rcu_read_{,un}lock()

On Fri, Aug 17, 2007 at 08:53:57AM -0700, Paul E. McKenney wrote: > On Fri, Aug 17, 2007 at 09:56:45AM +0200, Peter Zijlstra wrote: > > On Thu, 2007-08-16 at 09:01 -0700, Paul E. McKenney wrote: > > > On Thu, Aug 16, 2007 at 04:25:07PM +0200, Peter Zijlstra wrote: > > > > > > > > There seem to be

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

Linus Torvalds wrote: - in other words, the *only* possible meaning for "volatile" is a purely single-CPU meaning. And if you only have a single CPU involved in the process, the "volatile" is by definition pointless (because even without a volatile, the compiler is required to make

Re: [PATCH] lockdep: annotate rcu_read_{,un}lock()

Paul E. McKenney wrote: On Fri, Aug 17, 2007 at 09:56:45AM +0200, Peter Zijlstra wrote: On Thu, 2007-08-16 at 09:01 -0700, Paul E. McKenney wrote: On Thu, Aug 16, 2007 at 04:25:07PM +0200, Peter Zijlstra wrote: There seem to be some unbalanced rcu_read_{,un}lock() issues of

Re: [draft] Blackfin Early Printk implmentation

On 8/17/07, Robin Getz <[EMAIL PROTECTED]> wrote: > On Fri 17 Aug 2007 13:57, Mike Frysinger pondered: > > On 8/17/07, Robin Getz <[EMAIL PROTECTED]> wrote: > > > +int __init disable_early_printk(void) > > > +{ > > > + if (!early_console_initialized) > > > + return 0; > > > + >

Re: kfree(0) - ok?

On Fri, 17 Aug 2007, Arjan van de Ven wrote: > > On Fri, 2007-08-17 at 11:22 -0700, Andrew Morton wrote: > > On Wed, 15 Aug 2007 05:12:41 +0530 (IST) > > Satyam Sharma <[EMAIL PROTECTED]> wrote: > > > > > [PATCH] {slub, slob}: use unlikely() for kfree(ZERO_OR_NULL_PTR) check > > > > > >

Re: kfree(0) - ok?

On Aug 17 2007 11:22, Andrew Morton wrote: >Which is getting pretty idiotic: > >akpm:/usr/src/25> grep ZERO_OR_NULL_PTR */*.c >mm/slab.c: BUG_ON(ZERO_OR_NULL_PTR(cachep->slabp_cache)); >mm/slab.c: if (unlikely(ZERO_OR_NULL_PTR(cachep))) >mm/slab.c: if

Re: kfree(0) - ok?

On Fri, 2007-08-17 at 11:22 -0700, Andrew Morton wrote: > On Wed, 15 Aug 2007 05:12:41 +0530 (IST) > Satyam Sharma <[EMAIL PROTECTED]> wrote: > > > [PATCH] {slub, slob}: use unlikely() for kfree(ZERO_OR_NULL_PTR) check > > > > Considering kfree(NULL) would normally occur only in error paths and

[Patch 2.6.22.2 ] : drivers/net/via-rhine.c: Offload checksum handling to VT6105M

From: Kim Naru ([EMAIL PROTECTED]) Added support to offload TCP/UDP/IP checksum to the VIA Technologies VT6105M chip. Firstly, let the stack know this chip is capable of doing its own checksum(IPV4 only). Secondly offload checksum to VT6105M, if necessary. Verbose Mode: #1. Define 3

Re: [PATCH 02/12] Blackfin arch: Add label to call new GPIO API

Again, the patch descriptions need work. This changes the IRQ code (to add those labels). $SUBJECT doesn't mention IRQs, neither does the description ... On Tuesday 07 August 2007, Bryan Wu wrote: > --- a/arch/blackfin/mach-common/ints-priority-dc.c > +++

Re: [PATCH 01/12] Blackfin arch: add peripheral resource allocation support

On Tuesday 07 August 2007, Bryan Wu wrote: > From: Michael Hennerich <[EMAIL PROTECTED]> The patch description here is IMO misleading, and is clearly weak-to-nonexistent ... what this patch does is * Start tracking the label strings provided by gpio_request() * Provide a new portmux

Re: [PATCH 12/12] Blackfin serial driver: use new GPIO API

On Tuesday 07 August 2007, Bryan Wu wrote: > -   /* Enable UART0 RX and TX on pin 7 & 8 of PORT E */ > -   bfin_write_PORTE_FER(0x180 | bfin_read_PORTE_FER()); > -   bfin_write_PORTE_MUX(0x3C000 | bfin_read_PORTE_MUX()); > +   peripheral_request(P_UART0_TX, DRIVER_NAME); > +   

Re: [draft] Blackfin Early Printk implmentation

On Fri 17 Aug 2007 13:57, Mike Frysinger pondered: > On 8/17/07, Robin Getz <[EMAIL PROTECTED]> wrote: > > +int __init disable_early_printk(void) > > +{ > > + if (!early_console_initialized) > > + return 0; > > + > > + printk(KERN_INFO "Unregister %s%d\n",

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, 17 Aug 2007, Segher Boessenkool wrote: > > > atomic_dec() already has volatile behavior everywhere, so this is > > > semantically > > > okay, but this code (and any like it) should be calling cpu_relax() each > > > iteration through the loop, unless there's a compelling reason not to. >

Re: kfree(0) - ok?

On Wed, 15 Aug 2007 05:12:41 +0530 (IST) Satyam Sharma <[EMAIL PROTECTED]> wrote: > [PATCH] {slub, slob}: use unlikely() for kfree(ZERO_OR_NULL_PTR) check > > Considering kfree(NULL) would normally occur only in error paths and > kfree(ZERO_SIZE_PTR) is uncommon as well, so let's use unlikely()

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, 17 Aug 2007, Paul E. McKenney wrote: > On Fri, Aug 17, 2007 at 01:09:08PM +0530, Satyam Sharma wrote: > > > > On Thu, 16 Aug 2007, Paul E. McKenney wrote: > > > > > On Fri, Aug 17, 2007 at 07:59:02AM +0800, Herbert Xu wrote: > > > > > > > > First of all, I think this illustrates that

Re: Adding a security parameter to VFS functions

On Friday 17 August 2007 01:34, Al Viro wrote: > On Thu, Aug 16, 2007 at 03:57:24PM -0700, Linus Torvalds wrote: > > I personally consider this an affront to everythign that is decent. > > > > Why the *hell* would mkdir() be so magical as to need something like that? > > > > Make it something

Re: [draft] Blackfin Early Printk implmentation

On Fri, Aug 17, 2007 at 01:36:39PM -0400, Robin Getz wrote: > The patch (for review - not inclusion - I will send to Bryan if no one has > any > major objections, and he can push it via git) implements early printk for the > Blackfin architecture. > > It also adds an early exception handler,

Re: [draft] Blackfin Early Printk implmentation

On 8/17/07, Robin Getz <[EMAIL PROTECTED]> wrote: > + asm("\tRETI = %0;\n" > + "\tRETX = %0;\n" > + "\tRETN = %0;\n" > + : : "p"(early_trap)); general note, i dont think inserting whitespace by hand in asm() is a good thing ... i see it as whitenoise personally

[PATCH] - git-send-email.perl

Here's a path to enable a command line option that takes a string argument cc-cmd This modifies the @cc array to include whatever output is produced by cc_cmd $patchfile cccmd can be stored in a config settings file previous versions of this patch were submitted against an older

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

atomic_dec() already has volatile behavior everywhere, so this is semantically okay, but this code (and any like it) should be calling cpu_relax() each iteration through the loop, unless there's a compelling reason not to. I'll allow that for some hardware drivers (possibly this one) such a

Re: rtl8187: Invalid hwaddr! Using randomly generated MAC address

Probably want to copy [EMAIL PROTECTED] on wireless-related posts. Adding Michael Wu to the CC: as well... John On Fri, Aug 17, 2007 at 04:59:33PM +0100, Alan Jenkins wrote: > I've just acquired this buggy piece of hardware otherwise known as a > NetGear WG111v2. I googled and eventually found

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

Part of the motivation here is to fix heisenbugs. If I knew where they By the same token we should probably disable optimisations altogether since that too can create heisenbugs. Almost everything is a tradeoff; and so is this. I don't believe most people would find disabling all compiler

[draft] Blackfin Early Printk implmentation

The patch (for review - not inclusion - I will send to Bryan if no one has any major objections, and he can push it via git) implements early printk for the Blackfin architecture. It also adds an early exception handler, so if an interrupt/exception/violation happens before the kernel enables

SVr4/SVID/SUS IPC conformance

Hi! * Please, gurus, who cares about standards conformance, do not ignore this message! SysV code returns EIDRM for collision of IDs. I sure it should return EINVAL. Steps to reproduce: (this for shared memory code, for msg/sem it is the same) 1. Create then drop 2 shmem segments, then

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Fri, 2007-08-17 at 09:55 -0700, David Brownell wrote: > On Friday 17 August 2007, Kay Sievers wrote: > > Again, > > "Again"? We exchanges several mails a few weeks ago after the Debian bug caused by a modprobe loop. > > the only sane solution is to provide MODALIAS="platform:" > > from the

Re: [linux-usb-devel] why was MODALIAS removed from usb kernel events? [u]

On Fri, 17 Aug 2007, Andreas Jellinghaus [c] wrote: > I need some kernel event that has both DEVICE and MODALIAS set. > up to including kernel 2.6.21 this seems to come from > drivers/usb/core/driver.c if I read the code correctly, and then > it was removed. > > udevmonitor --kernel

Re: [PATCH 1/2] Add scaled time to taskstats based process accounting

On Fri, Aug 17, 2007 at 08:22:40AM +1000, Paul Mackerras wrote: > Linas Vepstas writes: > > > My gut impression (maybe wrong?) is that the scaled time is, > > in a certain sense, "more accurate" than the unscaled time. > > The "unscaled" time is just time, as in "how many seconds did this > task

Re: [PATCH 4/4] maps: /proc//pmaps interface - memory maps in granularity of pages

On Fri, Aug 17, 2007 at 02:47:27PM +0800, Fengguang Wu wrote: > Matt, > > It's not easy to do direct performance comparisons between pmaps and > pagemap/kpagemap. However some close analyzes are still possible :) > > 1) code size > pmaps ~200 LOC > pagemap/kpagemap~300

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Friday 17 August 2007, Kay Sievers wrote: > Again, "Again"? > the only sane solution is to provide MODALIAS="platform:" > from the platform bus, and adding the aliases to drivers who support > autoloading. Modalias strings are not free-text strings, they are > required to be prefixed by the

Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures

On Fri, 17 Aug 2007, Nick Piggin wrote: > > That's not obviously just taste to me. Not when the primitive has many > (perhaps, the majority) of uses that do not require said barriers. And > this is not solely about the code generation (which, as Paul says, is > relatively minor even on x86). I

Re: [PATCH 1/7] Simple Performance Counters: Core Piece

Hi Christoph, Actually, get_cycles() at least on some AMD cpus, do not synchronize the core, which can skew the results. You might want to use get_cycles_sync() there. Mathieu * Christoph Lameter ([EMAIL PROTECTED]) wrote: > Simple performance counters are a way to measure the performance on

[PATCH] __group_complete_signal: eliminate unneeded wakeup of ->group_exit_task

Cleanup. __group_complete_signal() wakes up ->group_exit_task twice. The second wakeup's state includes TASK_UNINTERRUPTIBLE, which is not very appropriate. Change the code to pass the "correct" argument to signal_wake_up() and kill now unneeded wake_up_process(). Signed-off-by: Oleg Nesterov

Re: [-mm PATCH] DMA engine kconfig improvements (rev2)

On Fri, Aug 17, 2007 at 08:59:29AM -0700, Nelson, Shannon wrote: > >From: Adrian Bunk [mailto:[EMAIL PROTECTED] > >Sent: Thursday, August 16, 2007 5:48 PM > >To: Nelson, Shannon > >Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org; > >Williams, Dan J; [EMAIL PROTECTED] > >Subject: Re: [-mm

rtl8187: Invalid hwaddr! Using randomly generated MAC address

I've just acquired this buggy piece of hardware otherwise known as a NetGear WG111v2. I googled and eventually found an explanation in the form of source code here: . It seems linux rejects the hardware MAC address

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On 8/17/07, Atsushi Nemoto <[EMAIL PROTECTED]> wrote: > On Fri, 17 Aug 2007 09:02:00 -0700, David Brownell <[EMAIL PROTECTED]> wrote: > > Because for some reason the driver name isn't rtc-ds1742 ... > > > > My preferred style for such patches puts the MODULE_ALIAS up > > near the strange driver

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Friday 17 August 2007, Atsushi Nemoto wrote: > > > My preferred style for such patches puts the MODULE_ALIAS up > > near the strange driver name, so it's more clear what's going > > on.  Putting all the MODULE_*() stuff at the end of the file > > gets confusing in this case. > > OK, then I

Re: [PATCH 17/23] mm: count reclaimable pages per BDI

On Thu, Aug 16, 2007 at 09:45:42AM +0200, Peter Zijlstra wrote: ... > Index: linux-2.6/include/linux/backing-dev.h > === > --- linux-2.6.orig/include/linux/backing-dev.h > +++ linux-2.6/include/linux/backing-dev.h > @@ -27,6 +27,7 @@

kernel 2.6.19 porting

Hi everyone, I have built up a software virtual prototype system with ARM11MPCORE. my system is similar with realview_eb_mpcore. but my system is simpler, which has only a mpcore , uart0, console,timer0_1, and memorys. I want to run kernel 2.6.19 on it. I have done some modification, and now I

Re: [PATCH 16/23] mm: scalable bdi statistics counters.

On Fri, 2007-08-17 at 12:20 -0400, Josef Sipek wrote: > On Thu, Aug 16, 2007 at 09:45:41AM +0200, Peter Zijlstra wrote: > > > Index: linux-2.6/include/linux/backing-dev.h > > === > > --- linux-2.6.orig/include/linux/backing-dev.h

Re: [PATCH 7/7] Simple Performance Counters: SLUB instrumentation

Hi Christoph, A few remarks on these tests: Why do you printk inside the timing period ? Filling the printk buffers or outputting on things such as serial console could really hurt your results. I hope you run your system with idle=poll and without frequency scaling at all, because otherwise

Re: [PATCH 16/23] mm: scalable bdi statistics counters.

On Thu, Aug 16, 2007 at 09:45:41AM +0200, Peter Zijlstra wrote: ... > Index: linux-2.6/include/linux/backing-dev.h > === > --- linux-2.6.orig/include/linux/backing-dev.h > +++ linux-2.6/include/linux/backing-dev.h ... > @@ -24,6

Re: [PATCH 11/23] mm: bdi init hooks

On Fri, 2007-08-17 at 12:10 -0400, Josef Sipek wrote: > On Thu, Aug 16, 2007 at 09:45:36AM +0200, Peter Zijlstra wrote: > > provide BDI constructor/destructor hooks > > > Index: linux-2.6/drivers/block/rd.c > > === > > ---

Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Fri, 17 Aug 2007 09:02:00 -0700, David Brownell <[EMAIL PROTECTED]> wrote: > Because for some reason the driver name isn't rtc-ds1742 ... > > My preferred style for such patches puts the MODULE_ALIAS up > near the strange driver name, so it's more clear what's going > on. Putting all the

Re: [PATCH 0/3] x86_64 EFI runtime service support

Huang, Ying wrote: >> >> Has the zero page documentation and version numbering project >> made any progress? I think we cannot merge this without at least >> the version number > More than that. You need to be able to boot a 32-bit kernel on a 64-bit system, so anything that breaks that is a

Re: [PATCH 11/23] mm: bdi init hooks

On Thu, Aug 16, 2007 at 09:45:36AM +0200, Peter Zijlstra wrote: > provide BDI constructor/destructor hooks ... > Index: linux-2.6/drivers/block/rd.c > === > --- linux-2.6.orig/drivers/block/rd.c > +++ linux-2.6/drivers/block/rd.c ...

Re: [PATCH 2/7] Simple Performance Counters: x86_64 support

* Andi Kleen ([EMAIL PROTECTED]) wrote: > On Wed, Aug 01, 2007 at 11:58:44AM -0700, Christoph Lameter wrote: > > On Wed, 1 Aug 2007, Andi Kleen wrote: > > > > > That might be on your systems, but for a mainline submission the > > > standards are higher. > > > > Right that is why I asked for

[linux-acpi] No ACPI Sleep button events problem

Hi. I have a problem with Sleep button events. dmesg shows this: ug 16 22:44:27 lapek ACPI: AC Adapter [ADP1] (off-line) Aug 16 22:44:27 lapek ACPI: Battery Slot [BAT0] (battery present) Aug 16 22:44:27 lapek ACPI: Power Button (FF) [PWRF] Aug 16 22:44:27 lapek ACPI: Lid Switch [LID0] Aug 16

Re: [PATCH 09/23] lib: percpu_counter_init error handling

On Fri, 2007-08-17 at 11:56 -0400, Josef Sipek wrote: > On Thu, Aug 16, 2007 at 09:45:34AM +0200, Peter Zijlstra wrote: > ) > > @@ -996,12 +997,16 @@ static int ext2_fill_super(struct super_ > > sbi->s_rsv_window_head.rsv_goal_size = 0; > > ext2_rsv_window_add(sb, >s_rsv_window_head); > >

Re: how to send a text format emai?

On 17/08/07, Xu Yang <[EMAIL PROTECTED]> wrote: > how to send a email of text format? Depends on your email program. But looking at your email you managed to do it: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -- Jesper Juhl <[EMAIL PROTECTED]> Don't

<    1   2   3   4   5   6   7   >