Randy Dunlap <[EMAIL PROTECTED]>:
> Another convention is that we put kernel-doc with the implementation
> (i.e., in .c files) when possible, not with the function prototype.
> Of course, for inline functions or macros in header files, that's
> where the kernel-doc has to live.
>
> so we don't
On Mon, 24 Sep 2007 08:06:45 +0200, Jiri Slaby said:
> Heh :). The few last before the list corruption BUG (you have to have
> LIST_DEBUG
> enabled) -- but it seems you never reached that phase?
Seems to be somewhat racy - had one attempt that obviously got into some grand
Mongolian
On Mon, 24 Sep 2007 11:01:10 +0800 Fengguang Wu <[EMAIL PROTECTED]>
wrote:
> > That is an interesting idea how about this:
>
> It looks like a workaround, but it does solve the most important problem.
> And it is a good logic by itself. So I'd vote for it.
>
> The fundamental problem is that
On Mon, 24 Sep 2007 08:22:31 +0200, Jan Engelhardt said:
>
> On Sep 24 2007 01:35, [EMAIL PROTECTED] wrote:
> >On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
> >
> >> -static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
> >> -{
> >> - if (n != 0 && size > ULONG_MAX / n)
>
Modular puppyvisor started giving linking errors
MODPOST 1 modules
ERROR: "kasprintf" [drivers/lguest/lg.ko] undefined!
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
lib/Makefile |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/lib/Makefile
+++
Hi,
> > This patch does the following things:
> >
> > - Make hidp_setup_input() return int to indicate errors.
> > - Check its return value to handle errors.
> >
> > Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
> >
> > ---
> > net/bluetooth/hidp/core.c |7 ---
> > 1 file changed, 4
On Sun, Sep 23, 2007 at 04:51:15PM -0400, Hector Martin wrote:
> I see several options for implementing this:
> - Add support to the standard FAT driver. This should probably be made a
> configurable suboption.
> - Add support that piggybacks onto the standard FAT driver, but
> otherwise doesn't
Davide,
Is it perhaps not better to group the three syscalls contiguously with
respect to syscall numbers? The old timerfd slot can be re-used for some
other syscall later.
Cheers,
Michael
Davide Libenzi wrote:
> Wires up the new timerfd API to the x86 family.
>
>
>
> Signed-off-by: Davide
On Fri, Sep 21, 2007 at 01:03:47PM +0200, Jarek Poplawski wrote:
...
> I hope not! But, then it would be probably another logical trick:
> ipc_rcu_getref/putref() seems to prevent kfreeing of a structure, so
> if it's used in do_msgsnd() there should be a risk something can do
> this kfree at this
Hello,
I already reported kernel 2.6.23-rcX warning about irq X : nobody cared, and
it seemed to have been fixed in 2.6.23-rc6... Unfortunately, just rebooting
with my 2.6.23-rc7, I got it appearing again, though the previous boot was
just fine, and I didn't change/recompile my kernel in between.
On Sep 24 2007 01:35, [EMAIL PROTECTED] wrote:
>On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
>
>> -static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
>> -{
>> -if (n != 0 && size > ULONG_MAX / n)
>> -return NULL;
>> -return __kmalloc(n * size, flags |
On Sun, 23 Sep 2007, Mike Galbraith wrote:
On Sat, 2007-09-22 at 12:01 +0200, Mike Galbraith wrote:
On Fri, 2007-09-21 at 20:27 -0700, Tong Li wrote:
Mike,
Could you try this patch to see if it solves the latency problem?
No, but it helps some when running two un-pinned busy loops, one at
On Thu, 20 Sep 2007 12:53:20 -0700 Dave Hansen <[EMAIL PROTECTED]> wrote:
> This is the real meat of the entire series. It actually
> implements the tracking of the number of writers to a mount.
> However, it causes scalability problems because there can
> be hundreds of cpus doing
On 09/24/2007 05:25 AM, [EMAIL PROTECTED] wrote:
> On Fri, 21 Sep 2007 21:43:20 +0200, Jiri Slaby said:
>> On 09/21/2007 09:38 PM, Jiri Slaby wrote:
>>> It is rather the other user who adds the page to some other list while bein
> g at
>>> deferred_pages list. Could you try my debug patch
>>>
On Sat, 22 Sep 2007 21:56:04 -0400
ben soo <[EMAIL PROTECTED]> wrote:
> i spoke too soon. The Gbit interface still dies. Lasted around
> 19hrs. or so. i can't tell if there are hardware issues: yesterday
> a Gbit NIC on the firewall died. Different chip (Realtek),
> different driver,
On Sat, 22 Sep 2007 21:56:04 -0400
ben soo [EMAIL PROTECTED] wrote:
i spoke too soon. The Gbit interface still dies. Lasted around
19hrs. or so. i can't tell if there are hardware issues: yesterday
a Gbit NIC on the firewall died. Different chip (Realtek),
different driver, different
On 09/24/2007 05:25 AM, [EMAIL PROTECTED] wrote:
On Fri, 21 Sep 2007 21:43:20 +0200, Jiri Slaby said:
On 09/21/2007 09:38 PM, Jiri Slaby wrote:
It is rather the other user who adds the page to some other list while bein
g at
deferred_pages list. Could you try my debug patch
On Thu, 20 Sep 2007 12:53:20 -0700 Dave Hansen [EMAIL PROTECTED] wrote:
This is the real meat of the entire series. It actually
implements the tracking of the number of writers to a mount.
However, it causes scalability problems because there can
be hundreds of cpus doing open()/close() on
On Sun, 23 Sep 2007, Mike Galbraith wrote:
On Sat, 2007-09-22 at 12:01 +0200, Mike Galbraith wrote:
On Fri, 2007-09-21 at 20:27 -0700, Tong Li wrote:
Mike,
Could you try this patch to see if it solves the latency problem?
No, but it helps some when running two un-pinned busy loops, one at
On Sep 24 2007 01:35, [EMAIL PROTECTED] wrote:
On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
-static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
-{
-if (n != 0 size ULONG_MAX / n)
-return NULL;
-return __kmalloc(n * size, flags | __GFP_ZERO);
Hello,
I already reported kernel 2.6.23-rcX warning about irq X : nobody cared, and
it seemed to have been fixed in 2.6.23-rc6... Unfortunately, just rebooting
with my 2.6.23-rc7, I got it appearing again, though the previous boot was
just fine, and I didn't change/recompile my kernel in between.
On Fri, Sep 21, 2007 at 01:03:47PM +0200, Jarek Poplawski wrote:
...
I hope not! But, then it would be probably another logical trick:
ipc_rcu_getref/putref() seems to prevent kfreeing of a structure, so
if it's used in do_msgsnd() there should be a risk something can do
this kfree at this
Davide,
Is it perhaps not better to group the three syscalls contiguously with
respect to syscall numbers? The old timerfd slot can be re-used for some
other syscall later.
Cheers,
Michael
Davide Libenzi wrote:
Wires up the new timerfd API to the x86 family.
Signed-off-by: Davide
On Sun, Sep 23, 2007 at 04:51:15PM -0400, Hector Martin wrote:
I see several options for implementing this:
- Add support to the standard FAT driver. This should probably be made a
configurable suboption.
- Add support that piggybacks onto the standard FAT driver, but
otherwise doesn't touch
Hi,
This patch does the following things:
- Make hidp_setup_input() return int to indicate errors.
- Check its return value to handle errors.
Signed-off-by: WANG Cong [EMAIL PROTECTED]
---
net/bluetooth/hidp/core.c |7 ---
1 file changed, 4 insertions(+), 3
Modular puppyvisor started giving linking errors
MODPOST 1 modules
ERROR: kasprintf [drivers/lguest/lg.ko] undefined!
Signed-off-by: Alexey Dobriyan [EMAIL PROTECTED]
---
lib/Makefile |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/lib/Makefile
+++
On Mon, 24 Sep 2007 08:22:31 +0200, Jan Engelhardt said:
On Sep 24 2007 01:35, [EMAIL PROTECTED] wrote:
On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
-static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
-{
- if (n != 0 size ULONG_MAX / n)
- return
On Mon, 24 Sep 2007 11:01:10 +0800 Fengguang Wu [EMAIL PROTECTED]
wrote:
That is an interesting idea how about this:
It looks like a workaround, but it does solve the most important problem.
And it is a good logic by itself. So I'd vote for it.
The fundamental problem is that the
On Mon, 24 Sep 2007 08:06:45 +0200, Jiri Slaby said:
Heh :). The few last before the list corruption BUG (you have to have
LIST_DEBUG
enabled) -- but it seems you never reached that phase?
Seems to be somewhat racy - had one attempt that obviously got into some grand
Mongolian flustercluck,
Randy Dunlap [EMAIL PROTECTED]:
Another convention is that we put kernel-doc with the implementation
(i.e., in .c files) when possible, not with the function prototype.
Of course, for inline functions or macros in header files, that's
where the kernel-doc has to live.
so we don't need this
On Mon, Sep 24, 2007 at 08:54:07AM +0200, Jarek Poplawski wrote:
After rethinking, this scenario seems to be wrong or very unprobable
(I'm not sure of all ways if (--container...) could be compiled),
so there should be no such risk - double kfree/vfree is more probable,
so no danger. More
On Mon, Sep 24, 2007 at 11:18:26AM +0400, Alexey Dobriyan wrote:
Modular puppyvisor started giving linking errors
MODPOST 1 modules
ERROR: kasprintf [drivers/lguest/lg.ko] undefined!
Please kill lib-y while you're at it. It's useless and a constant
source of pain like this.
-
On 9/24/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
-static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
-{
- if (n != 0 size ULONG_MAX / n)
- return NULL;
- return __kmalloc(n * size, flags |
[EMAIL PROTECTED] wrote:
Using kernel 2.6.23-rc7 as xen domU client system I observe a kernel bug
which occurs reproducibly when calling a shell from midnight commander F2
context menu or with testcase given below (However most other programs seem
to
be well behaved and do not trigger this
Try this:
1. At one prompt, do cat.
Now, switch to another prompt and...
2. Do pstree -p|grep cat to find out the PID of your cat command. I
get 20502.
3. Do cat /proc/20502/wchan. I get 0 here.
4. Do strace -p 20502. I get read(0, unfinished ... here.
So wchan says cat is waiting for 0.
On Mon, 24 Sep 2007 11:44:35 +0400, Alexey Dobriyan said:
On 9/24/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
-static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
-{
- if (n != 0 size ULONG_MAX / n)
-
On Thu, 20 Sep 2007 10:57:19 -0700 Frank Mayhar [EMAIL PROTECTED] wrote:
Properly support the ru_maxrss field of the rusage structure returned by
getrusage(). This patch includes documentation both of the getrusage()
implementation in general and of the ru_maxrss implementation
specifically.
On Mon, Sep 24, 2007 at 08:41:10AM +0100, Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:18:26AM +0400, Alexey Dobriyan wrote:
Modular puppyvisor started giving linking errors
MODPOST 1 modules
ERROR: kasprintf [drivers/lguest/lg.ko] undefined!
Please kill lib-y while
On Sun, 2007-09-23 at 22:52 +0200, Rafael J. Wysocki wrote:
Second, noacpitimer added to the command line makes all of the kernels,
up to
and including 2.6.23-rc6-mm1, boot (this seems to be 100% reproducible).
That's valuable information. Can you please provide a boot log of one of
On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
Please kill lib-y while you're at it. It's useless and a constant
source of pain like this.
Kernel-bloat is another constant source of pain.
But the troubles are that increased blot does not result in compiler erros.
And your
On 09/24/2007 09:37 AM, [EMAIL PROTECTED] wrote:
(Interestingly, I can't find any of the 3 addresses listed in the 'list_add
corruption' message anywhere *else* in the netconsole output, and the last
thing
we hear from before the kersplat is apparently an RCU callback in a softirq?)
Hmm,
On Mon, Sep 24, 2007 at 09:35:23AM +0200, Peter Zijlstra wrote:
On Mon, 24 Sep 2007 11:01:10 +0800 Fengguang Wu [EMAIL PROTECTED]
wrote:
That is an interesting idea how about this:
It looks like a workaround, but it does solve the most important problem.
And it is a good logic by
Jarek Poplawski wrote:
On Fri, Sep 21, 2007 at 01:03:47PM +0200, Jarek Poplawski wrote:
...
I hope not! But, then it would be probably another logical trick:
ipc_rcu_getref/putref() seems to prevent kfreeing of a structure, so
if it's used in do_msgsnd() there should be a risk something can do
On Mon, 24 Sep 2007 11:44:35 +0400, Alexey Dobriyan said:
Interesting. Here is output from kernel with patch applied and leak
plugged into proc_dointvec() (I checked twice):
$ grep kcalloc /proc/slab_allocators
$ grep proc_dointvec /proc/slab_allocators
size-64: 19
@@ -162,7 +198,7 @@ __change_page_attr(unsigned long address
/* on x86-64 the direct mapping set at boot is not using 4k pages */
BUG_ON(PageReserved(kpte_page));
- save_page(kpte_page);
+ save_page(kpte_page, 0);
if (page_private(kpte_page) == 0)
On Mon, 24 Sep 2007 09:09:48 +0100 Christoph Hellwig [EMAIL PROTECTED] wrote:
On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
Please kill lib-y while you're at it. It's useless and a constant
source of pain like this.
Kernel-bloat is another constant source of pain.
But
Davide,
On Sun, 2007-09-23 at 15:49 -0700, Davide Libenzi wrote:
This is the new timerfd API as it is implemented by the following patch:
---
fs/compat.c | 32 ++-
fs/timerfd.c | 199
++-
include/linux/compat.h
The merge window for 2.6.24 should open up any day now, so it's
probably time for me to detail what I intend to cram in there.
This release will probably be one of the biggest ones for the MMC layer
so far. The major pieces are SDIO and SPI support, but there are
several small nuggets as well.
On Mon, Sep 24, 2007 at 09:09:48AM +0100, Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
Please kill lib-y while you're at it. It's useless and a constant
source of pain like this.
Kernel-bloat is another constant source of pain.
But the troubles
This should be accompanied by
addr2 = __START_KERNEL_map + __pa(address);
/* Make sure the kernel mappings stay executable */
prot2 = pte_pgprot(pte_mkexec(pfn_pte(0, prot)));
- err =
Just an idea I had, it seems like a good idea to wait for RCU callbacks
in reclaim so that we won't get all of memory stuck there.
If this location is too aggressive we might stick it next to
disable_swap_token().
---
Couple RCU and reclaim.
There could be a lot of memory stuck in RCU
From: Andrey Mirkin [EMAIL PROTECTED]
Right now futexfs and inotifyfs have one magic 0xBAD1DEA, that looks a little
bit confusing.
Use 0xBAD1DEA as magic for futexfs and 0x2BAD1DEA as magic for inotifyfs.
Signed-off-by: Andrey Mirkin [EMAIL PROTECTED]
fs/inotify_user.c |4 +++-
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
- New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
things, mainly (Kumar Gala [EMAIL PROTECTED])
Boilerplate:
- See the `hot-fixes' directory for any important updates to this
Sorry for the long delay, been very busy since I last posted the 386
kernel patches back in July.
Now that I have more free time I remade the patches in a cleaner manner,
broken down into
smaller patches, with fewer #ifdefs all over the place. most #ifdefs are
in the include/asm-i386 headers
Hi Vegard,
On Sat, 2007-09-22 at 21:27 +0200, Vegard Nossum wrote:
After recent discussions on LKML and a general dissatisfaction at the
current printk() kernel-message logging interface, I've decided to
write down some of the ideas for a better system.
Good luck :-)
[snip]
Example: {
Jarek Poplawski wrote:
On Thu, Sep 20, 2007 at 03:08:42PM +0200, Nadia Derbey wrote:
Nadia Derbey wrote:
Jarek Poplawski wrote:
On Thu, Sep 20, 2007 at 08:24:58AM +0200, Nadia Derbey wrote:
...
Actually, ipc_lock() is called most of the time without the
ipc_ids.mutex held and without
Hi Pierre,
There are currently three working drivers for this new stack:
- sdio_uart: A driver for the standardised GPS and UART interfaces.
Currently we only know how the GPS system works, so UART is only a
future possibility.
- libertas_sdio: Support for Marvell's 8686 Libertas wifi
static void lock_and_coalesce_cpu_mnt_writer_counts(void)
{
int cpu;
struct mnt_writer *cpu_writer;
for_each_possible_cpu(cpu) {
cpu_writer = per_cpu(mnt_writers, cpu);
spin_lock_nested(cpu_writer-lock, 42);
Hello,
I tried to compile the kernel 2.6.9 because I want to use it with
RTLinux and that the only 2.6.x kernel supported. I used gcc 2.95.3 as
recommended.
But I have an error by compilation of process.c :
CC arch/i386/kernel/process.o
{standard input}: Assembler messages:
{standard
Hello,
I have an LCD panel on a custom PXA27x based board and it must be turned
on/off by some special commands via a GPIO throught a I2C chip.
I'd like some suggestion about I can easily manage this situation.
Maybe can I add a special I2C function to get i2c_client pointer and then
using it
Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
- New git tree git-powerpc-galak.patch added to the -mm lineup: ppc32
things, mainly (Kumar Gala [EMAIL PROTECTED])
snip
Hi Andrew,
The link error for a PowerMac G5 (powerpc)
On Sun, 2007-09-23 at 23:21 -0700, Tong Li wrote:
On Sun, 23 Sep 2007, Mike Galbraith wrote:
On Sat, 2007-09-22 at 12:01 +0200, Mike Galbraith wrote:
On Fri, 2007-09-21 at 20:27 -0700, Tong Li wrote:
Mike,
Could you try this patch to see if it solves the latency problem?
No, but
Denys Vlasenko wrote:
On Friday 31 August 2007 16:13, Denys Vlasenko wrote:
Attached are three patches which fix that:
textdata bss dec hex filename
261433 500181172 312623 4c52f
linux-2.6.23-rc1.org.t/drivers/scsi/aic7xxx/built-in.o
199654 500181172
Hi all,
2.6.22.7's include/linux/autoconf.h is completely screwed up as
compare to 2.6.10's autoconf.h .
2.6.22.7 totally changed the meaning of autoconf.h
By just reading autoconf.h of 2.6.10 , we can understand what is the
system and its configuration, it is properly arranged and divided into
Denys Vlasenko wrote:
On Friday 31 August 2007 16:15, Denys Vlasenko wrote:
On Friday 31 August 2007 16:13, Denys Vlasenko wrote:
Attached are three patches which fix that:
textdata bss dec hex filename
261433 500181172 312623 4c52f
Denys Vlasenko wrote:
On Friday 31 August 2007 16:16, Denys Vlasenko wrote:
On Friday 31 August 2007 16:15, Denys Vlasenko wrote:
On Friday 31 August 2007 16:13, Denys Vlasenko wrote:
Attached are three patches which fix that:
textdata bss dec hex filename
261433 50018
On Mon, 24 Sep 2007 12:10:09 +0200 Mike Galbraith [EMAIL PROTECTED] wrote:
@@ -117,7 +117,7 @@ static inline struct task_struct *task_o
static inline u64
max_vruntime(u64 min_vruntime, u64 vruntime)
{
- if ((vruntime min_vruntime) ||
+ if (((s64)vruntime (s64)min_vruntime) ||
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
Hi all,
2.6.22.7's include/linux/autoconf.h is completely screwed up as
compare to 2.6.10's autoconf.h .
2.6.22.7 totally changed the meaning of autoconf.h
... snip ...
why do you care what autoconf.h looks like? it's automatically
generated,
hello rday,
In my view autoconf.h is the index of kernel you are using. By reading
autoconf.h you will know what Architecture, drivers is selected.
For example, If we are using some ARM based board, If you give me your
autoconf.h , I can replicate same environment as yours. If it is not
properly
Am Freitag 21 September 2007 schrieb Jiri Kosina:
On Fri, 21 Sep 2007, Hans de Goede wrote:
Thats not what I had in mind, autosuspend doesn't work (presumably
because hal keeps polling for media change) maybe I should fix hal to
not keep polling for devices which don't have removable
On Mon, 24 Sep 2007 10:58:08 +0200 (CEST)
Rodolfo Giometti [EMAIL PROTECTED] wrote:
Hello,
I have an LCD panel on a custom PXA27x based board and it must be
turned on/off by some special commands via a GPIO throught a I2C chip.
I'd like some suggestion about I can easily manage this
On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
It lived fast, it died young, it didn't leave a pretty corpse...
Something in the startup scripts did a 'touch', and ker-blam.
[ 15.668000] Unable
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
hello rday,
In my view autoconf.h is the index of kernel you are using. By
reading autoconf.h you will know what Architecture, drivers is
selected.
For example, If we are using some ARM based board, If you give me
your autoconf.h , I can
On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
how about something like:
s64 delta = (s64)(vruntime - min_vruntime);
if (delta 0)
min_vruntime += delta;
That would rid us of most of the funny conditionals there.
That still left me with negative min_vruntimes. The pinned
Peter Zijlstra wrote:
Just an idea I had, it seems like a good idea to wait for RCU callbacks
in reclaim so that we won't get all of memory stuck there.
If this location is too aggressive we might stick it next to
disable_swap_token().
---
Couple RCU and reclaim.
There could be a
hello rday,
On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
hello rday,
In my view autoconf.h is the index of kernel you are using. By
reading autoconf.h you will know what Architecture, drivers is
selected.
For example, If we are
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
hello rday,
On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
hello rday,
In my view autoconf.h is the index of kernel you are using. By
reading autoconf.h you will know what
hello rday,
On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
hello rday,
On 9/24/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007, Jaswinder Singh wrote:
hello rday,
In my view autoconf.h is the index of
On (22/09/07 08:20), Satyam Sharma didst pronounce:
Hi,
On Thu, 20 Sep 2007, Alan Cox wrote:
On Thu, 20 Sep 2007 14:13:15 +0100
[EMAIL PROTECTED] (Mel Gorman) wrote:
PPC64 building allmodconfig fails to compile drivers/ata/pata_scc.c . It
doesn't show up on other arches
I can't see the reason . = VDSO_PRELINK + 0x900; was ever there in the
linker script for the x86_64 vDSO. I can't find anything that depends on
this magic offset, or that should care at all about the particular location
of of the .data section (all from vvar.c) in the vDSO image. If it is
This adds a const to the definitions vvar.c makes, so that the vdso_*
variables go into .rodata instead of .data. This is essentially a cosmetic
change, just giving the section headers in the vDSO file more pleasing flags.
These variables are read-only from the perspective of the vDSO itself and
On Mon, 24 Sep 2007 16:12:19 +0530 Balbir Singh
[EMAIL PROTECTED] wrote:
Peter Zijlstra wrote:
Just an idea I had, it seems like a good idea to wait for RCU callbacks
in reclaim so that we won't get all of memory stuck there.
If this location is too aggressive we might stick it next
On Mon, 24 Sep 2007 12:42:15 +0200 Mike Galbraith [EMAIL PROTECTED] wrote:
On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
how about something like:
s64 delta = (s64)(vruntime - min_vruntime);
if (delta 0)
min_vruntime += delta;
That would rid us of most of the
[EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
It lived fast, it died young, it didn't leave a pretty corpse...
Something in the startup scripts did a 'touch', and
Hi all,
Can please someone let me know what is criteria for default kernel
configuration .
Is it based upon some survey or requested by Fedora or others.
By default configuration size of vmlinux is 41 MB and it includes
approx 75% of useless stuff for me.
what is the idea behind 'default
On (22/09/07 12:24), Satyam Sharma didst pronounce:
On Thu, 20 Sep 2007, Satyam Sharma wrote:
BTW ppc64_defconfig didn't quite like 2.6.23-rc6-mm1 either ...
IIRC I got build failures in:
drivers/net/spider_net.c
[PATCH -mm] spider_net: Misc build fixes after recent netdev
On (22/09/07 14:11), Satyam Sharma didst pronounce:
-static volatile int kgdb_hwbreak_sstep[NR_CPUS];
+volatile int kgdb_hwbreak_sstep[NR_CPUS];
That looks fishy to me. Why is it volatile-qualified?
It turned out that it was unnecessary. A follow-up patch removed the volatile
and kept
On Mon, 2007-09-24 at 12:42 +0200, Mike Galbraith wrote:
On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
how about something like:
s64 delta = (s64)(vruntime - min_vruntime);
if (delta 0)
min_vruntime += delta;
That would rid us of most of the funny conditionals
Peter Zijlstra wrote:
On Mon, 24 Sep 2007 16:12:19 +0530 Balbir Singh
[EMAIL PROTECTED] wrote:
Peter Zijlstra wrote:
Just an idea I had, it seems like a good idea to wait for RCU callbacks
in reclaim so that we won't get all of memory stuck there.
If this location is too aggressive we
This patch:
- makes hidp_setup_input() return int to indicate errors;
- checks its return value to handle errors.
And this time it is against -rc7-mm1 tree.
Thanks to roel and Marcel Holtmann for comments.
Signed-off-by: WANG Cong [EMAIL PROTECTED]
---
net/bluetooth/hidp/core.c | 11
On Fri, 21 Sep 2007, Andi Kleen wrote:
For the curious the details of all the hassle are reasonably well
described in the Intel's AP-578 application note.
Thanks. Ok it has to stay for for i386 then; although it would be in theory
possible to only reserve when the CPU is a real 386. For
On Mon, 2007-09-24 at 13:08 +0200, Peter Zijlstra wrote:
Its perfectly valid for min_vruntime to exist in 1ULL 63.
But wrap backward timewarp is what's killing my box.
-Mike
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Hi Andrew,
The kernel build fails with
CC arch/ia64/kernel/efi.o
arch/ia64/kernel/efi.c: In function 'efi_memmap_init':
arch/ia64/kernel/efi.c:1088: error: 'total_memory' undeclared (first use in
this function)
arch/ia64/kernel/efi.c:1088: error: (Each undeclared identifier is reported
Hi all,
I want to check performance difference by using realtime preemption patch :
http://www.kernel.org/pub/linux/kernel/projects/rt/
Please let me know from where I can download samples to test realtime
preemption performance difference.
Can someone please share performance numbers for your
On Mon, 24 Sep 2007 16:52:15 +0530 Balbir Singh
[EMAIL PROTECTED] wrote:
Peter Zijlstra wrote:
On Mon, 24 Sep 2007 16:12:19 +0530 Balbir Singh
[EMAIL PROTECTED] wrote:
Peter Zijlstra wrote:
Just an idea I had, it seems like a good idea to wait for RCU callbacks
in reclaim so that we
On Mon, 24 Sep 2007 13:22:14 +0200 Mike Galbraith [EMAIL PROTECTED] wrote:
On Mon, 2007-09-24 at 12:42 +0200, Mike Galbraith wrote:
On Mon, 2007-09-24 at 12:24 +0200, Peter Zijlstra wrote:
how about something like:
s64 delta = (s64)(vruntime - min_vruntime);
if (delta 0)
On Mon, Sep 24, 2007 at 04:41:54PM +0530, Jaswinder Singh wrote:
Hi all,
Can please someone let me know what is criteria for default kernel
configuration .
Is it based upon some survey or requested by Fedora or others.
By default configuration size of vmlinux is 41 MB and it includes
Oliver Neukum wrote:
Am Freitag 21 September 2007 schrieb Jiri Kosina:
On Fri, 21 Sep 2007, Hans de Goede wrote:
Thats not what I had in mind, autosuspend doesn't work (presumably
because hal keeps polling for media change) maybe I should fix hal to
not keep polling for devices which don't
On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
Hi all,
2.6.22.7's include/linux/autoconf.h is completely screwed up as
compare to 2.6.10's autoconf.h .
2.6.22.7 totally changed the meaning of autoconf.h
autoconf.h has always been autogenerated. And autoconf.h has always
On Mon, Sep 24, 2007 at 06:35:50AM -0400, [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2007 02:17:16 PDT, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc7/2.6.23-rc7-mm1/
It lived fast, it died young, it didn't leave a pretty corpse...
Something in
501 - 600 of 1028 matches
Mail list logo
