On Mon, 29 Jan 2007, Oleg Nesterov wrote:
> > But we could delay CPU_DOWN in the handler for the slab until we know that
> > the cache_reaper is no longer running?
>
> Hmm... I don't undestand this. We can delay CPU_DOWN if we cancel cache_reaper
> like you did in the previous patch. Did you
> This is the most straight forward and handles machines with really
> weird msi setups, so I lean in this direction.
>
> The question is there anything at all we can do generically?
>
> I can't see a case where ppc_md would not wind up with the hooks
> that decide if it is a hypervisor or not.
On Mon, 29 Jan 2007 14:53:28 -0500, Kristian Høgsberg <[EMAIL PROTECTED]> wrote:
> >>git://people.freedesktop.org/~krh/linux-2.6
> >
> > This seems to have disappeared. Was it moved or dropped?
>
> No, it's still there, and I just did a git clone on it. How does it fail for
> you?
Oh
When the world was a simple and static place setting up irqs was easy.
It sufficed to allocate a linux irq number and a find a free cpu
vector we could receive that linux irq on. In those days it was
a safe assumption that any allocated vector was actually in use
so after one global pass through
On Mon, 29 Jan 2007, Jeff Dike wrote:
> +#if CONFIG_ZONE_DMA_FLAG
> + sizes->cs_dmacachep = kmem_cache_create(
This would need to be
#idef CONFIG_ZONE_DMA
There have been some recent changes though so I am not sure what your
codebase is.
-
To unsubscribe from this list: send the
Hi.
On Mon, 2007-01-29 at 12:34 +0100, Oliver Neukum wrote:
> Am Montag, 29. Januar 2007 12:24 schrieb Nigel Cunningham:
> > Hi.
> >
> > On Mon, 2007-01-29 at 12:06 +0100, Oliver Neukum wrote:
> > > Hi,
> > >
> > > may a driver call wake_up() while doing resume() ?
> >
> > I assume you mean
optional-zone_dma-in-the-vm-no-gfp_dma-check-in-the-slab-if-
no-config_zone_dma-is-set-reduce-config_zone_dma-ifdefs converts some
ifdefs into ifs.
One of them causes cs_dmacachep to be referenced, when that field
doesn't exist, because it's ifdefed on CONFIG_ZONE_DMA.
I'd suggest reverting that
Sometimes developers need to see more object code in an oops report,
e.g. when kernel may be corrupted at runtime.
Add the "code_bytes" option for this.
Signed-off-by: Chuck Ebbert <[EMAIL PROTECTED]>
Documentation/kernel-parameters.txt |5 +
arch/i386/kernel/traps.c| 20
On Mon, 2007-01-29 at 11:08 -0800, Casey Schaufler wrote:
> --- Stephen Smalley <[EMAIL PROTECTED]> wrote:
>
> > True, but a system that disables proc is likely a
> > system with a custom
> > policy anyway, and dependency on proc is fairly
> > basic to selinux these
> > days (due to reliance on
On Mon, 2007-01-29 at 11:31 -0800, Stephen Hemminger wrote:
> Does this fix it?
Don't know.
> --- sky2-2.6.orig/drivers/net/sky2.c 2007-01-29 10:05:12.0 -0800
> +++ sky2-2.6/drivers/net/sky2.c 2007-01-29 10:29:56.0 -0800
> @@ -3675,6 +3675,12 @@
> sky2_write32(hw,
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> Here are the numbers that i think changes the picture:
i forgot to explain them:
current (estimated) total installed base of 32-bit (i686) Fedora:
> http://www.fedoraproject.org/awstats/stats/updates-released-fc6-i386.total
current (estimated)
On Mon, Jan 29, 2007 at 09:20:58PM +1100, Nick Piggin wrote:
> But it is sad that this thing got merged without any callers to even know
> how it is intended to work. Must it be able to sleep?
Ocfs2 absolutely needs to be able to sleep in there in order to take cluster
locks, do allocation, etc.
Hi Linus,
I made a silly error in my last upstream push. This patch makes
ocfs2 build again.
--Mark
Please pull from 'upstream-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/mfasheh/ocfs2.git upstream-linus
to receive the following updates:
fs/ocfs2/ocfs2_fs.h |
Pete Zaitcev wrote:
On Thu, 25 Jan 2007 16:18:35 -0500, Kristian Høgsberg <[EMAIL PROTECTED]> wrote:
Indeed, I've just moved to an in-tree development model now. I still think
the out-off-tree model is a good way to prototype, get started and reach
"critical mass" with your driver. But as
include/linux/cdev.h defines cd_forget to take a struct inode *, but does not
pull in any definition or declaration for struct inode. This generates a
compiler warning if a source file pulls in cdev.h without first pulling in
fs.h. Add a forward declaration of struct inode to cdev.h, to
the current filename->define translation does not scrub dashes so when
creating stub defines for like asm-x86_64/ptrace-abi.h, we get:
#define __ASM_STUB_PTRACE-ABI_H
gcc just hates that sort of thing :)
trivial attached patch adds - to the tr list to scrub it to _
-mike
pgpYLCcJoqp75.pgp
* Hugh Dickins <[EMAIL PROTECTED]> wrote:
> > For every 64-bit Fedora box there's more than seven 32-bit boxes. I
> > think 32-bit is going to live with us far longer than many thought,
> > so we might as well make it work better. Both HIGHMEM and HIGHPTE is
> > the default on many distro
On 01/29, Christoph Lameter wrote:
>
> On Mon, 29 Jan 2007, Oleg Nesterov wrote:
>
> > > > Even if smp_processor_id() was stable during the execution of
> > > > cache_reap(),
> > > > this work_struct can be moved to another CPU if CPU_DEAD happens. We
> > > > can't
> > > > avoid this, and this
Subject: Add support to OProfile for profiling Cell BE SPUs
From: Maynard Johnson <[EMAIL PROTECTED]>
This patch updates the existing arch/powerpc/oprofile/op_model_cell.c
to add in the SPU profiling capabilities. In addition, a 'cell' subdirectory
was added to arch/powerpc/oprofile to hold
Subject: Enable SPU switch notification to detect currently active SPU tasks.
From: Maynard Johnson <[EMAIL PROTECTED]>
This patch adds to the capability of spu_switch_event_register so that the
caller is also notified of currently active SPU tasks. It also exports
spu_switch_event_register
The code was setting up the debug bus for group 21 when profiling on the
event PPU CYCLES. The debug bus is not actually used by the hardware
performance counters when counting PPU CYCLES. Setting up the debug bus
for PPU CYCLES causes signal routing conflicts on the debug bus when
Linus, please apply before 2.6.20. Thanks.
The BUG in fuse_ctl_add_dentry() could be triggered if the control
filesystem was unmounted and mounted again while one or more fuse
filesystems were present.
The fix is to reset the dentry counter in fuse_ctl_kill_sb().
Bug reported by Florent
This is a clean up patch that includes the following changes:
-It removes some macro definitions that are only used once
with the actual code.
-Some comments were added to clarify the code based on feedback
from the community.
-The write_pm_cntrl() and
On December 14, 2006, I posted a patch that added support to the
OProfile kernel driver for profiling Cell SPUs. There have been some
changes/fixes to this patch since the original posting (including
forward porting from 2.6.18-based kernel to 2.6.20-rc1), so I am
reposting the patch for
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Mon, 29 Jan 2007, Auke Kok wrote:
>>
>> Yes. A few hundred cycles of loading/unloading snd_hda_intel with
>> enable_msi=1
>> didn't break it on i386.
>>
>> I sure hope this can get into 2.6.20!
>
> Eric, can you write an explanation, add your
On Mon, 29 Jan 2007, Auke Kok wrote:
>
> Yes. A few hundred cycles of loading/unloading snd_hda_intel with enable_msi=1
> didn't break it on i386.
>
> I sure hope this can get into 2.6.20!
Eric, can you write an explanation, add your sign-off, Auke's ACK, and
send out the result? The patch
Does this fix it?
---
drivers/net/sky2.c | 43 ++-
1 file changed, 18 insertions(+), 25 deletions(-)
--- sky2-2.6.orig/drivers/net/sky2.c2007-01-29 10:05:12.0 -0800
+++ sky2-2.6/drivers/net/sky2.c 2007-01-29 10:29:56.0 -0800
@@
On 01/29, Christoph Lameter wrote:
>
> On Mon, 29 Jan 2007, Oleg Nesterov wrote:
>
> > > The slab would need a notification
> > > that the workqueue for a processor was shutdown in order to set work.func
> > > = NULL.
> >
> > The slab has a notification:
On Mon, 2007-01-29 at 10:55 -0700, Eric W. Biederman wrote:
> James Morris <[EMAIL PROTECTED]> writes:
>
> > On Mon, 29 Jan 2007, Stephen Smalley wrote:
> >
> >> NAK. Mapping all sysctls to a single security label prevents any kind
> >> of fine-grained security on sysctls, and current policies
On Fri, Jan 26, 2007 at 11:08:42AM -0500, Lennart Sorensen wrote:
> OK, the tty settings according to stty that I am using are:
> # stty -F /dev/ttyn0 -a
> speed 230400 baud; rows 0; columns 0; line = 0;
> intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 =
> ; start = ^Q; stop
On Mon, 29 Jan 2007, Oleg Nesterov wrote:
> > > Even if smp_processor_id() was stable during the execution of
> > > cache_reap(),
> > > this work_struct can be moved to another CPU if CPU_DEAD happens. We can't
> > > avoid this, and this is correct.
> >
> > Uhh This may not be correct in
On Saturday, January 27, 2007 8:19 am, Matthew Wilcox wrote:
> > There are also some "legacy io" binary sysfs files in these
> > directories for those platforms that support it (#ifdef
> > HAVE_PCI_LEGACY), and I'm guessing that there is some user for them
> > out there, otherwise they would not
On Mon, 29 Jan 2007, Ingo Molnar wrote:
>
> For every 64-bit Fedora box there's more than seven 32-bit boxes. I
> think 32-bit is going to live with us far longer than many thought, so
> we might as well make it work better. Both HIGHMEM and HIGHPTE is the
> default on many distro kernels,
On Mon, 29 Jan 2007 10:49:43 -0800
Randy Dunlap <[EMAIL PROTECTED]> wrote:
> > I could probably arrange to share an ARM toolchain if there was
> > demand...
>
> I'd certainly like to see/use it.
http://userweb.kernel.org/~akpm/arm-cross.tar.bz2 works. It's linked
on FC5 x86, runs OK on FC6 and
Stephen Smalley <[EMAIL PROTECTED]> writes:
>> > If the ctl_table supplied more information about the functional purpose
>> > and the security sensitivity of the sysctl, then we could leverage that
>> > information instead, as long as we can at least derive the current
>> > labelings from that
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> > The idea being to essentially suspend the system to RAM, remove the
> > CPU and then unsuspend it? Seems like quite high overhead -- or am
> > I misunderstanding the proposal?
>
> The process freezer basically wakes up all threads in the machine
Patch adds ability to work with 64bit metadata,
this made by replacing work with 32bit pointers by
inline functions.
Signed-off-by: Evgeniy Dushistov <[EMAIL PROTECTED]>
---
Index: linux-2.6.20-rc5/fs/ufs/balloc.c
===
---
These series of patches add UFS2 write-support.
UFS2 - is default file system for recent versions of FreeBSD.
The main differences from UFS1 from write support point of view
are:
1)Not all inodes are allocated during formatation of disk.
2)All meta-data(pointer to data blocks) are 64bit(in UFS1
This patch adds into write inode path function to write
UFS2 inode,
and modifys allocate inode path to allocate and init additional
inode chunks.
Also some cleanups:
- remove not used parameters in some functions
- remove i_gen field from ufs_inode_info structure,
there is i_generation in inode
On Mon, 29 Jan 2007, Oleg Nesterov wrote:
> > The slab would need a notification
> > that the workqueue for a processor was shutdown in order to set work.func
> > = NULL.
>
> The slab has a notification: CPU_XXX events. It should cancel a pending per
> cpu
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> > Eradicate global locks.
> >
> > - kmap_lock is removed by extensive use of atomic_t, a new flush
> >scheme and modifying set_page_address to only allow NULL<->virt
> >transitions.
> I really don't recall any performance problems being
--- Stephen Smalley <[EMAIL PROTECTED]> wrote:
> True, but a system that disables proc is likely a
> system with a custom
> policy anyway, and dependency on proc is fairly
> basic to selinux these
> days (due to reliance on /proc/self/attr for process
> attribute
> manipulation in place of the
On Mon, Jan 29, 2007 at 07:12:35PM +0100, Christoph Hellwig wrote:
> Okay. Now that we get into the details I've also added some renaming,
> release_mem becomes release_tty and the new factored out function is
> release_one_tty. The difference is documented in the kdoc comments.
>
>
>
Eric W. Biederman wrote:
Auke Kok <[EMAIL PROTECTED]> writes:
Hi,
I've established a regression in the MSI vector/irq allocation routine for both
i386 and x86_64. Our test labs repeatedly modprobe/rmmod the e1000 driver for
serveral minutes which allocates msi vectors and frees them. These
On Mon, 29 Jan 2007 18:36:49 + Richard Purdie wrote:
> On Sat, 2007-01-27 at 12:05 -0800, Andrew Morton wrote:
> > On Sat, 27 Jan 2007 13:11:16 -0500
> > Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> >
> > > I am currently trying crosstool by Dan Kegel, it looks promising.
> > >
On Mon, 2007-01-29 at 10:15 -0800, Christoph Lameter wrote:
> On Mon, 29 Jan 2007, Peter Zijlstra wrote:
>
> > Ladder locking would end up:
> >
> > lock A0
> > lock B1
> > unlock A0 -> a new operation can start
> > lock C2
> > unlock B1
> > lock D5
> > unlock C2
> > ** we do stuff to D5
> >
On Mon, 2007-01-29 at 10:43 -0700, Eric W. Biederman wrote:
> Stephen Smalley <[EMAIL PROTECTED]> writes:
>
> > On Sun, 2007-01-28 at 12:21 -0700, Eric W. Biederman wrote:
> >> With the sysctl cleanups sysctl is not really a part of proc
> >> it just shows up there, and any path based approach
On Sat, 2007-01-27 at 12:05 -0800, Andrew Morton wrote:
> On Sat, 27 Jan 2007 13:11:16 -0500
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > I am currently trying crosstool by Dan Kegel, it looks promising.
> > http://www.kegel.com/crosstool/
>
> Yeah, I spent a frustrating two days with
Hello,
I am using kernel 2.6.18, and have been trying without success to set
up multiple network interfaces using kernel boot arguments. It makes
sense to be able to specify multiple interface configurations on the
command line, but it has occurred to me that I may not be correctly
On Mon, 29 Jan 2007, Andi Kleen wrote:
> On Thursday 25 January 2007 22:37, David Rientjes wrote:
> > Any leftover memory is allocated
> > to a final node unless the command-line ends with a comma.
>
> That sounds like syntactical vinegar and a nasty trap. Remember
> that venus probe that got
When expanding the stack, we don't currently check if the VMA will cross into
an area of the address space that is reserved for hugetlb pages. Subsequent
faults on the expanded portion of such a VMA will confuse the low-level MMU
code, resulting in an OOPS. Check for this.
Signed-off-by: Adam
On 1/29/07, Hugh Dickins <[EMAIL PROTECTED]> wrote:
But, never mind hugetlb, you still not quite convinced me that there's
no problem at all with get_user_pages find_extend_vma growing on ia64.
I repeat that ia64_do_page_fault has REGION tests to guard against
expanding either kind of stack
Hi Pierre,
Sorry about the delay.
I changed a bit the code to align with your latest suggestions.
ext Pierre Ossman wrote:
> I've queued it up for -mm, but there a few more comments I want resolved
> before this can move to Linus...
>
> You need to clean up mmc_lockable_store(). It had a few
On 01/29, Christoph Lameter wrote:
>
> On Mon, 29 Jan 2007, Oleg Nesterov wrote:
>
> > > > This is wrong. Suppose we have a CPU_UP,CPU_DOWN,CPU_UP sequence. The
> > > > last
> > > > CPU_UP will not restart a per-cpu "cache_reap timer".
> > >
> > > Why?
> >
> > Because the last CPU_UP calls
On Mon, 2007-01-29 at 09:37 -0800, Andrew Morton wrote:
> hm, thanks for testing - I'll drop it.
>
> I don't really understand what's wrong with it though. Maybe it's settng
> USER_DS on kernel threads?
For architectures with a split address space there has to be a call
set_fs(USER_DS) that
On Mon, Jan 29, 2007 at 04:10:29AM +0100, Andi Kleen wrote:
> Don't require the vDSO for handling a.out signals
> --- linux.orig/include/linux/binfmts.h
> +++ linux/include/linux/binfmts.h
> @@ -59,6 +59,7 @@ struct linux_binfmt {
> int (*load_shlib)(struct file *);
> int
On Mon, 29 Jan 2007, Peter Zijlstra wrote:
> Ladder locking would end up:
>
> lock A0
> lock B1
> unlock A0 -> a new operation can start
> lock C2
> unlock B1
> lock D5
> unlock C2
> ** we do stuff to D5
> unlock D5
>
Instead of taking one lock we would need to take 4? Wont doing so cause
Hello,
Under kexec, I/OAT initialization breaks over busy resources
because the previous kernel did not release them.
I'm not sure this fix can be considered a complete one but
it works for me. I guess something similar to the *_remove
method should occur there..
Signed-off-by: Dan Aloni
On Mon, Jan 29, 2007 at 07:01:00AM -0500, Alan Cox wrote:
> On Sun, Jan 28, 2007 at 06:12:44PM +0100, Christoph Hellwig wrote:
> > release_mem contains two copies of exactly the same code. Refactor
> > these into a new helper, release_tty. The only change in behaviour
> > is that the driver
On Mon, 2007-01-29 at 09:20 -0800, Christoph Lameter wrote:
> On Sun, 28 Jan 2007, Peter Zijlstra wrote:
>
> > With Nick leading the way to getting rid of the read side of the tree_lock,
> > this work continues by breaking the write side of said lock.
>
> Could we get the read side in separately
> This was patch inspired by my finding out that code in the running
> kernel might have
> been modified at runtime by some strange bug, and looking at vmlinux
> might not be
> helpful.
Hmm ok, although I still suspect in such a case you'll be better
off with a full kcrash dump.
-Andi
-
To
On (26/01/07 09:16), Christoph Lameter didst pronounce:
> I do not see any updates of vmstat.c and vmstat.h. This
> means that VM statistics are not kept / considered for ZONE_MOVABLE.
Based on searching around for ZONE_DMA32, the following patch appears to be
all that is required;
diff -rup -X
On Mon, Jan 29, 2007 at 08:32:53AM -0500, Stephen Smalley wrote:
> > - fs/selinuxfs.c:sel_remove_bools()
> >
> > Utter madness. I have no idea how this ever got merged.
> > Maybe the selinux folks can explain what crack they were
> > on when writing this. The problem would go away
James Morris <[EMAIL PROTECTED]> writes:
> On Mon, 29 Jan 2007, Stephen Smalley wrote:
>
>> NAK. Mapping all sysctls to a single security label prevents any kind
>> of fine-grained security on sysctls, and current policies already make
>> use of the current distinctions to limit access to
On Mon, 29 Jan 2007, Andrew Morton wrote:
> > static int
> > svc_pool_map_init_percpu(struct svc_pool_map *m)
> > {
> > - unsigned int maxpools = nr_node_ids;
> > + unsigned int maxpools = num_online_cpus();
> > unsigned int pidx = 0;
> > unsigned int cpu;
> > int err;
>
>
Good day.
I have a really big trouble with VIA-EPIA mainboards under Linux
2.6.19. After loading kernel Linux the RESET-circuit ceases to work
correctly.
At reset (by RESET-button or by Watchdog) the system begins to be
restarted, but hangs before occurrence of any BIOS-messages. Only a
NEQ-Tasklet wasn't killed when module is removed.
Signed-off-by: Thomas Klein <[EMAIL PROTECTED]>
---
drivers/net/ehea/ehea_main.c |1 +
1 files changed, 1 insertion(+)
diff -Nurp -X dontdiff linux-2.6.20-rc6/drivers/net/ehea/ehea_main.c
patched_kernel/drivers/net/ehea/ehea_main.c
---
Stephen Smalley <[EMAIL PROTECTED]> writes:
> On Sun, 2007-01-28 at 12:21 -0700, Eric W. Biederman wrote:
>> With the sysctl cleanups sysctl is not really a part of proc
>> it just shows up there, and any path based approach will not
>> adequately describe the data as sysctl is essentially a
>>
This patch fixes the wrong query and logging of the per interface jumbo frames
enabled/disabled status.
Signed-off-by: Thomas Klein <[EMAIL PROTECTED]>
---
drivers/net/ehea/ehea.h |2 +-
drivers/net/ehea/ehea_main.c | 30 +++---
2 files changed, 24
Randy Dunlap wrote:
On Sat, 27 Jan 2007 10:05:48 -1000 akuster wrote:
My apologies, I cc'd the wrong list the first time around.
+config FAST_POWER_DOWN
+ tristate "Fast power of profile"
---> off
What does that mean? especially the "profile" part?
On Fri, 26 Jan 2007 19:02:37 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> On Friday 26 January 2007 5:19 pm, Matthew Garrett wrote:
> > On Fri, Jan 26, 2007 at 04:42:56PM -0800, David Brownell wrote:
> > > On Friday 26 January 2007 3:15 pm, Matthew Garrett wrote:
> > > > It's certainly the
The softlockup watchdog needs to be touched after resume to avoid a
false positive.
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Acked-by: Jiri Kosina <[EMAIL PROTECTED]>
Index: linux-2.6.20-rc6-mm/kernel/time/tick-common.c
Randy Dunlap wrote:
On Sat, 27 Jan 2007 10:05:43 -1000 akuster wrote:
My apologies, I cc'd the wrong list the first time around.
{argh, attachments}
my bad
--- linux-2.6_dev.orig/kernel/power/Kconfig
+++ linux-2.6_dev/kernel/power/Kconfig
@@ -131,3 +131,5 @@ config SUSPEND_SMP
On Mon, 29 Jan 2007 14:59:58 +0100
Heiko Carstens <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 29, 2007 at 12:33:28PM +0100, Heiko Carstens wrote:
> > On Wed, Jan 24, 2007 at 01:09:18AM -0800, [EMAIL PROTECTED] wrote:
> > > mm-search_binary_handler-mem-limit-fix.patch
> > > From: Dmitriy
I have a consistent problem running 'make modules_install' after compiling. The
directory structure forms in /lib/modules, but no modules install. This problem
showed up under -rc6-mm1 and -rc6-mm2, but not -rc6. I'm hoping somebody has
hit this before, otherwise it's git-bisect time.
Process
On Mon, 29 Jan 2007 11:21:41 +
Frederik Deweerdt <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 29, 2007 at 12:12:07AM -0800, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm2/
> >
>
> Hi,
>
> The svc_pool_map_init_percpu()
On Fri, 26 Jan 2007, Christoph Lameter wrote:
On Thu, 25 Jan 2007, Mel Gorman wrote:
@@ -166,6 +168,8 @@ enum zone_type {
#define ZONES_SHIFT 1
#elif __ZONE_COUNT <= 4
#define ZONES_SHIFT 2
+#elif __ZONE_COUNT <= 8
+#define ZONES_SHIFT 3
#else
You do not need a shift of 3. Even with
On Mon, 29 Jan 2007, Oleg Nesterov wrote:
> > > This is wrong. Suppose we have a CPU_UP,CPU_DOWN,CPU_UP sequence. The last
> > > CPU_UP will not restart a per-cpu "cache_reap timer".
> >
> > Why?
>
> Because the last CPU_UP calls start_cpu_timer(), but since ->work.func != NULL
> we don't do
On Sun, 28 Jan 2007, Ken Chen wrote:
>
> For ia64, the hugetlb address region is reserved at the top of user
> space address. Stacks are below that region. Throw in the mix, we
> have two stacks, one memory stack that grows down and one register
> stack backing store that grows up. These two
Fixes compilation with 2.6.20-rc6-mm1.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
drivers/net/spider_net.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Index: b/drivers/net/spider_net.c
===
---
On 01/29, Christoph Lameter wrote:
>
> On Mon, 29 Jan 2007, Oleg Nesterov wrote:
>
> > Now,
> > static void __devinit start_cpu_timer(int cpu)
> > {
> > struct delayed_work *reap_work = _cpu(reap_work, cpu);
> >
> > if (keventd_up() && reap_work->work.func ==
On Sun, 28 Jan 2007, Peter Zijlstra wrote:
> With Nick leading the way to getting rid of the read side of the tree_lock,
> this work continues by breaking the write side of said lock.
Could we get the read side in separately from the write side? I think I
get the read side but the write side
On Sun, 28 Jan 2007, Peter Zijlstra wrote:
> provide an unsigned long atomic type.
Is this really necessary? We have no atomic_uint_t type either.
Could you use atomic_long_t instead?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Mon, 29 Jan 2007 10:54:49 -0500 Phillip Susi wrote:
> I have noticed that vger seems to be truncating Cc lists lately, often
> resulting in broken partial email addresses in the Cc list causing
> people that reply to have copies of the message bounced back instead of
> being delivered to
On Sun, Jan 28, 2007 at 06:03:08PM +0100, Denis Vlasenko wrote:
> I still don't see much difference between O_SYNC and O_DIRECT write
> semantic.
O_DIRECT is about avoiding the copy_user between cache and userland,
when working with devices that runs faster than ram (think >=100M/sec,
quite
On 01/29/2007 02:46 PM, Rene Herman wrote:
This syncs up the x86_64 probe_roms() with the i386 version as just
submitted.
===
Sync up with i386. Specifically, be careful about touching the
legacy ROMs; in virtualized environments they may not be mapped.
Crosscompiled, but not booted due to
On Mon, 29 Jan 2007, Oleg Nesterov wrote:
> Now,
> static void __devinit start_cpu_timer(int cpu)
> {
> struct delayed_work *reap_work = _cpu(reap_work, cpu);
>
> if (keventd_up() && reap_work->work.func == NULL) {
>
Am 2007-01-29 15:37 + schrieb Russell King:
> Is it really worth adding additional code to shut up this (imho) silly
> warning? It's just adding needless complexity to drivers.
As I pointed out in
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2006-November/037192.html
the
Evgeniy Polyakov wrote:
Hello.
I'm pleased to announce initial userspace M-on-N threading model
implementation (for hackers) called NTL.
If you haven't already, I suggest you look into the story of NGPT and
also read the NPTL white paper
(http://people.redhat.com/drepper/nptl-design.pdf)
On Mon, 2007-01-29 at 17:22 +0100, Karsten Wiese wrote:
> Hi,
>
> with dynticks and highres_timers enabled, cpufreq_ondemand makes mess here on
> an AMD64 UP.
> cpufreq_ondemand assumes that jiffies advance at exactly the same pace as the
> sum of all kstat_cpu(cpu).cpustat.* members.
> This
On Mon, 29 Jan 2007, Thomas Gleixner wrote:
> > I guess that it's caused by some timer changes (added Thomas and Ingo to
> > CC), which confuse the softlockup detector sense of time?
> Does the patch below fix this ?
It does.
Acked-by: Jiri Kosina <[EMAIL PROTECTED]>
--
Jiri Kosina
-
To
Hi,
with dynticks and highres_timers enabled, cpufreq_ondemand makes mess here on
an AMD64 UP.
cpufreq_ondemand assumes that jiffies advance at exactly the same pace as the
sum of all kstat_cpu(cpu).cpustat.* members.
This isn't the case here as dmesg output from patch below shows.
Is
On Mon, 29 Jan 2007, Nick Piggin wrote:
>
> After do_wp_page calls page_mkwrite on its target (old_page), it then drops
> the reference to the page before locking the ptl and verifying that the pte
> points to old_page.
>
> Unfortunately, old_page may have been truncated and freed, or reclaimed,
On Mon, Jan 29, 2007 at 07:07:04AM -0800, Ulrich Drepper wrote:
> Alexey Dobriyan wrote:
> > What do you mean by "filesystems cannot support lutimes"? Filesystems
> > that don't have on-disk timestamps for symlinks?
>
> Yes.
Checked to be sure, on ext2, ext3, reiserfs, XFS symlink timestamps
I have noticed that vger seems to be truncating Cc lists lately, often
resulting in broken partial email addresses in the Cc list causing
people that reply to have copies of the message bounced back instead of
being delivered to the intended recipients. It seems that it munges
long, multi
Matthew Garrett wrote:
> On Mon, Jan 29, 2007 at 01:55:41PM +0100, roucaries bastien wrote:
>> - return 0;
>> + return bcm43xx_init_one(pdev, NULL);
>> }
>
> While this may well work (it's basically equivalent to unloading and
> reloading the module), it's not a long-term fix -
Denis Vlasenko wrote:
I still don't see much difference between O_SYNC and O_DIRECT write
semantic.
Yes, if you change the normal io paths to properly support playing
vmsplice games ( which have a number of corner cases ) to get the zero
copy, and support madvise() and O_SYNC to control
> Fix VIA quirks that were recently broken by Alan Cox in the upstream
> kernel (commit 1597cacbe39802d86656d1f2e6329895bd2ef531).
>
> My understanding is that pci_find_present() doesn't work yet at the
> time the quirks are run. So I used a two-step quirk as is done for
> some other quirks
Andi Kleen wrote:
> On Friday 26 January 2007 00:56, Chuck Ebbert wrote:
>
>
>> Can't think of a way to word the justification, but I've wanted to see more
>> code a few times.
>>
>
> Hmm, not sure I see the point. The Code line is just that you can
> make sense of random mailing list
On Mon, 2007-01-29 at 12:02 +0100, Jiri Kosina wrote:
>
> I guess that it's caused by some timer changes (added Thomas and Ingo to
> CC), which confuse the softlockup detector sense of time?
Does the patch below fix this ?
tglx
Index: linux-2.6.20-rc6-mm/kernel/time/tick-common.c
201 - 300 of 800 matches
Mail list logo
