On Thu, 20 Dec 2007 18:51:04 +0100 Jan Kara [EMAIL PROTECTED] wrote:
Although we don't allow writes over s_maxbytes, it can happen that a file's
size is larger than s_maxbytes. For example we can write the file from a
computer with a different architecture (which has larger s_maxbytes), boot
Cant you, modify bootmem allocator to test with memtest patterns and then
use kexec (as Pavel suggested) to test the one where kernel was sitting
earlier?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Pavel Machek
Sent: Friday, December 21, 2007 6:28 PM
On Sat, 22 Dec 2007, Zhang Rui wrote:
On Sat, 2007-12-22 at 06:36 +0800, Andrei Gaponenko wrote:
With 2.6.23 or newer (including 2.6.24-rc6) kernels, writing to the
/sys/devices/platform/asus-laptop/display file does not do anything:
...
hmm, please echo 1 /proc/acpi/video/xxx/DOS in
On Thu, 20 Dec 2007 11:09:44 +0100 Jesper Nilsson [EMAIL PROTECTED] wrote:
Subject: [PATCH] Remove unused __dummy, CONST_ADDR and ADDR from CRIS bitops.h
It's nice (and conventional) to prefix the patch title with the subsystem
name. So this one would become
Subject: [PATCH] cris: remove
On Fri, Dec 21, 2007 at 11:02:09PM -0800, Joe Perches wrote:
Signed-off-by: Joe Perches [EMAIL PROTECTED]
---
arch/alpha/boot/Makefile |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/alpha/boot/Makefile b/arch/alpha/boot/Makefile
index cd14388..c53169c
Hi Jesper.
__initramfs_end = .;
- /* We fill to the next page, so we can discard all init
-pages without needing to consider what payload might be
-appended to the kernel image. */
- FILL (0);
- . = ALIGN
On Mon, 17 Dec 2007 20:48:03 -0800 Joe Perches [EMAIL PROTECTED] wrote:
Back to Adam Fritzler...
...
diff --git a/CREDITS b/CREDITS
index ee909f2..449ec7f 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1124,6 +1124,9 @@ S: 1150 Ringwood Court
S: San Jose, California 95131
S: USA
+N:
On Sat, 2007-12-22 at 09:33 +0100, Sam Ravnborg wrote:
arch/alpha/boot/mixc.c have:
#include ../../../lib/inflate.c
Right. thanks. Sorry for the noise.
Should the makefiles for the sources that include lib/inflate.c
have a dependency similar to arm and alpha?
With:
arch/alpha/boot/misc.c
Andrew Morton wrote:
On Mon, 17 Dec 2007 20:48:03 -0800 Joe Perches [EMAIL PROTECTED] wrote:
Back to Adam Fritzler...
...
diff --git a/CREDITS b/CREDITS
index ee909f2..449ec7f 100644
--- a/CREDITS
+++ b/CREDITS
@@ -1124,6 +1124,9 @@ S: 1150 Ringwood Court
S: San Jose, California 95131
S:
On Fri, Dec 21, 2007 at 04:21:17PM -0800, Andrew Morton wrote:
On Fri, 21 Dec 2007 16:55:03 +0100
Marcin Slusarz [EMAIL PROTECTED] wrote:
sparse generated:
fs/udf/dir.c:78:5: warning: symbol 'udf_readdir' was not declared. Should
it be static?
there are 2 different prototypes of
On Sat, 2007-12-22 at 03:53 -0500, Jeff Garzik wrote:
What was the rationale for removing Adam from MAINTAINERS?
I sent him a patch to that address and it bounced.
I sent him a note asking if he was still a maintainer to
his new address and he replied:
On Thu, 20 Dec 2007 11:46:16 +0300 Ivan Kokshaysky [EMAIL PROTECTED] wrote:
PCI: do respect full 64-bit address for bridge prefetch window
Prevent the prefetch window from being programmed with a bogus address
when its respective resource gets allocated above the 4G mark.
Note that we
On Sat, 22 Dec 2007 01:12:18 -0800 Andrew Morton [EMAIL PROTECTED] wrote:
On Thu, 20 Dec 2007 11:46:16 +0300 Ivan Kokshaysky [EMAIL PROTECTED] wrote:
PCI: do respect full 64-bit address for bridge prefetch window
Prevent the prefetch window from being programmed with a bogus address
On Mon, 17 Dec 2007 19:25:27 -0500 Chuck Ebbert [EMAIL PROTECTED] wrote:
Looks like a commit that I can't find in git due to the arch merge
has broken PCI address assignment. This patch by Richard Henderson
against 2.6.23 fixes it for x86_64:
---
On Mon, 17 Dec 2007 23:43:14 +0100 Michal Schmidt [EMAIL PROTECTED] wrote:
kthreadd, the creator of other kernel threads, runs as a normal
priority task. This is a potential for priority inversion when a task
wants to spawn a high-priority kernel thread. A middle priority
SCHED_FIFO task can
Hi Thomas,
On Dec 5, 2007 11:25 AM, Thomas Bogendoerfer [EMAIL PROTECTED] wrote:
These:
+#define READ_SC(p, r)readb((p)-membase + RD_##r)
+#define WRITE_SC(p, r, v)writeb((v), (p)-membase + WR_##r)
and these:
+#define READ_SC_PORT(p, r) read_sc_port(p,
* David Miller [EMAIL PROTECTED] wrote:
From: Ingo Molnar [EMAIL PROTECTED]
Date: Fri, 21 Dec 2007 23:54:13 +0100
Really, if your behavior is representative of how our SLAB allocator
will be maintained in the future then i'm very, very worried :-(
Actually, to the contrary, I
On Sat, 2007-12-22 at 01:30 -0800, Andrew Morton wrote:
On Mon, 17 Dec 2007 23:43:14 +0100 Michal Schmidt [EMAIL PROTECTED] wrote:
kthreadd, the creator of other kernel threads, runs as a normal
priority task. This is a potential for priority inversion when a task
wants to spawn a
Hi Vitaly,
I had an attempt a while ago to do this but haven't had enough time to get it
completed, so
I am glad to see it finally picked up. There was some sort of discussion that
time, you seem to have some of those points
addressed but something not, please
check:
* Andi Kleen [EMAIL PROTECTED] wrote:
Ingo Molnar [EMAIL PROTECTED] writes:
Christoph, /proc/slabinfo is an _ABI_. You HAVE to provide it.
slabtop relies on it, people use it every day to monitor memory
consumption.
It's definitely not a stable ABI. slabtop tends to exit without
On Mon, 17 Dec 2007 12:13:22 + richard [EMAIL PROTECTED] wrote:
fix lockup in when calling drop_caches
calling /proc/sys/vm/drop_caches can hang due to a AB/BA lock dependency
between j_list_lock and the inode_lock. This patch moves the redirtying
of the buffer head out
On Sat, 22 Dec 2007 04:52:50 -0500 Jon Masters [EMAIL PROTECTED] wrote:
The general approach we've taken to this is don't do that. Yes, we could
boost lots of kernel threads in the way which this patch does but this
actually takes control *away* from userspace. Userspace no longer has the
On Sat, 2007-12-22 at 02:11 -0800, Andrew Morton wrote:
Should there be a watchdog which checks for a process which has run
realtime for a certain period and which then takes some action? Such as
descheduling it for a while, generating warnings, demoting its policy,
killing it etc?
Using
On Mon, 17 Dec 2007 03:35:55 +0100 (MET) Richard Knutsson [EMAIL PROTECTED]
wrote:
Convert handmade 'max' to max().
...
--- a/ipc/msg.c
+++ b/ipc/msg.c
@@ -473,7 +473,7 @@ asmlinkage long sys_msgctl(int msqid, int cmd, struct
msqid_ds __user *buf)
On Mon, 17 Dec 2007 03:36:00 +0100 (MET) Richard Knutsson [EMAIL PROTECTED]
wrote:
Convert m_ts (message text size) from int to size_t.
Signed-off-by: Richard Knutsson [EMAIL PROTECTED]
---
Remove some trailing spaces, since we are in the neighborhood.
diff --git a/include/linux/msg.h
On Sat, 2007-12-22 at 04:52 -0500, Jon Masters wrote:
So, user tasks running with SCHED_FIFO should be able to lock a system?
I guess I see both sides of this argument - yes, it's userspace at
fault, but in other cases when userspace is at fault, we take action
(OOM, segfault, others). Isn't
On Thursday 20 December 2007, Adrian McMenamin wrote:
On 20/12/2007, Adrian McMenamin [EMAIL PROTECTED] wrote:
This patch adds support for the CD Rom device (called a GD Rom) on
the SEGA Dreamcast.This device has a command block similar to a
standard ATA-3 device, though implements Sega's
Hi,
Sorry for repeating but as far as i can see 2.6.23.11/12 got no changes
into NFS.
I've run into this problem 2.6.23.9. The open syscall will return
Invalid argument when O_TRUNC is set on existing files.
The same file can be opened for append or removed.
The evidence is for example:
On Sat, 22 Dec 2007 11:39:30 +0100 Mike Galbraith [EMAIL PROTECTED] wrote:
On Sat, 2007-12-22 at 04:52 -0500, Jon Masters wrote:
So, user tasks running with SCHED_FIFO should be able to lock a system?
I guess I see both sides of this argument - yes, it's userspace at
fault, but in
On 2007.12.22 01:25:16 +0100, Harald Welte wrote:
I'm running an Intel DQ35JO mainboard (Q35 chipset, Q6600 CPU) and I am
observing a regression with linux-2.6.24-rc1 through -rc6 (linux-2.6.git as
of today, ea67db4cdbbf7f4e74150e71da0984e25121f500).
The last working version is 2.6.24-rc1.
On Sat, 2007-12-22 at 02:52 -0800, Andrew Morton wrote:
On Sat, 22 Dec 2007 11:39:30 +0100 Mike Galbraith [EMAIL PROTECTED] wrote:
On Sat, 2007-12-22 at 04:52 -0500, Jon Masters wrote:
So, user tasks running with SCHED_FIFO should be able to lock a system?
I guess I see both
Hi Darrick,
Le 20/12/2007, Darrick J. Wong écrit:
On Thu, Dec 20, 2007 at 10:58:08AM +0100, Jean Delvare wrote:
BTW, did you try your driver with lm-sensors 3.0.0?
Yes I did, and it looked ok to me. Did you find something wrong?
No, I just wanted to make sure that you had tested it. Now
--
Thanks,
Oliver
I backported this patch to 2.6.22.y tree.
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6206
---
original patch:
c46f739dd39db3b07ab5deb4e3ec81e1c04a91af in linux-2.6.git
Ingo Molnar [Wed, 28 Nov 2007 12:59:18 + (13:59 +0100)]
fix:
Hi Bjorn,
Le 21/12/2007, Bjorn Helgaas [EMAIL PROTECTED] a écrit:
On Tuesday 18 December 2007 10:59:18 am Jean Delvare wrote:
My initial idea was to identify the faulty motherboard using DMI and to
force pnpacpi=off on the faulty motherboards. If this is considered too
aggressive, maybe we
On Sat, 22 Dec 2007, Balbir Singh wrote:
Andrew Morton wrote:
On Fri, 21 Dec 2007 00:23:58 +0530 Balbir Singh [EMAIL PROTECTED] wrote:
Based on the discussion at http://lkml.org/lkml/2007/12/20/383, it was
felt that control_type might not be a good thing to implement right away.
We can
On Thu, Dec 20, 2007 at 02:04:56PM -0800, Greg KH wrote:
On Sat, Dec 15, 2007 at 04:19:16PM +0100, Kay Sievers wrote:
On Sat, 2007-12-15 at 16:34 +0300, Alexey Dobriyan wrote:
On Fri, Dec 14, 2007 at 01:48:23PM -0800, Greg KH wrote:
On Mon, Dec 03, 2007 at 01:25:51PM -0800, Greg KH
Hi,
Linus really wants the extended (4Kb) PCI configuration space (using MCFG acpi
table etc) to be opt-in, since there's many issues with it and most drivers
don't even use/need it. The idea behind opt-in is that if you don't use it, you
don't get to suffer the bugs...
Booted on my 64 bit
could be offered on SLUB too.
Sure (I argued that in a earlier mail in fact), but it doesn't make
sense to fake into the old slabinfo format.
'top' isnt critical functionality either like udev, and the ABI does not
only cover 'critical' functionality. A utility suddenly not working
gives
From: Arjan van de Ven [EMAIL PROTECTED]
Subject: opt the sky2 driver into using extended config space
So far, the sky2 driver is the only one I've identified (with a quick grep)
that actually would be using extended configuration space; the patch below
adds the enablement of this to the driver.
On Fri, Dec 21, 2007 at 08:36:40PM -0800, David Miller wrote:
From: Andi Kleen [EMAIL PROTECTED]
Date: Sat, 22 Dec 2007 02:53:11 +0100
And to handle potentially ambiguous cases we, for a long time, have
the force_successful_syscall_return() arch hook.
Ah I see what you mean now.
From: Pekka Enberg [EMAIL PROTECTED]
This adds a read-only /proc/slabinfo file that is ABI compatible with SLAB for
SLUB.
Cc: Ingo Molnar [EMAIL PROTECTED]
Cc: Andi Kleen [EMAIL PROTECTED]
Cc: Christoph Lameter [EMAIL PROTECTED]
Cc: Peter Zijlstra [EMAIL PROTECTED]
Signed-off-by: Pekka Enberg
Hi,
On Dec 22, 2007 2:37 PM, Andi Kleen [EMAIL PROTECTED] wrote:
Removing an interface that exposes lots of internal details when you
rewrite the subsystem and those internal details all change seems
like a good reason to me.
Yeah but then again removing an interface that has been around for
Yeah but then again removing an interface that has been around for
ever
Version 2.1 hasn't been around forever and at least slabtop does not
work over version number changes in my experience.
-Andi
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
the rule is very simple: unless you have really, really, really, REALLY
good reasons, just dont break stuff.
Could we please drop kset: move /sys/slab to /sys/kernel/slab from -mm?
Old slabinfo complains that SLUB_DEBUG is not on and refuses to do anything.
--
To unsubscribe from this list:
Emanuele Rocca wrote:
* David Miller [EMAIL PROTECTED], [2007-12-20 0:40 -0800]:
The problem is that I created indirection that was totally unused, the
operation vectors members for these cases thus didn't get filled in,
and we OOPS trying to call NULL pointers as functions :-)
This
* Pekka J Enberg [EMAIL PROTECTED] wrote:
From: Pekka Enberg [EMAIL PROTECTED]
This adds a read-only /proc/slabinfo file that is ABI compatible with
SLAB for SLUB.
cool :-) I tried your patch and slabtop works just fine:
--
Active / Total Objects (% used): 31939 /
* Pekka J Enberg [EMAIL PROTECTED] wrote:
From: Pekka Enberg [EMAIL PROTECTED]
This adds a read-only /proc/slabinfo file that is ABI compatible with
SLAB for SLUB.
Cc: Ingo Molnar [EMAIL PROTECTED]
Tested-by: Ingo Molnar [EMAIL PROTECTED]
Ingo
--
To unsubscribe from this list:
Hi Andi,
On Dec 22, 2007 2:54 PM, Andi Kleen [EMAIL PROTECTED] wrote:
Yeah but then again removing an interface that has been around for
ever
Version 2.1 hasn't been around forever and at least slabtop does not
work over version number changes in my experience.
True but the default
Hi Ingo,
On Dec 22, 2007 3:14 PM, Ingo Molnar [EMAIL PROTECTED] wrote:
Also please apply the cleanup patch below, it fixes 34 checkpatch errors
and warnings in mm/slub.c.
Those are already fixed in -mm:
* Ingo Molnar [EMAIL PROTECTED] wrote:
From: Pekka Enberg [EMAIL PROTECTED]
This adds a read-only /proc/slabinfo file that is ABI compatible with
SLAB for SLUB.
Cc: Ingo Molnar [EMAIL PROTECTED]
Tested-by: Ingo Molnar [EMAIL PROTECTED]
Pekka, i stuck your patch into the
Hi Ingo,
On Dec 22, 2007 3:37 PM, Ingo Molnar [EMAIL PROTECTED] wrote:
Pekka, i stuck your patch into the x86.git random-test-grid, and it
found the following build error after a few iterations:
mm/slub.c: In function 's_show':
mm/slub.c:4188: error: implicit declaration of function
* Pekka Enberg [EMAIL PROTECTED] wrote:
Hi Ingo,
On Dec 22, 2007 3:14 PM, Ingo Molnar [EMAIL PROTECTED] wrote:
Also please apply the cleanup patch below, it fixes 34 checkpatch errors
and warnings in mm/slub.c.
Those are already fixed in -mm:
On Sat 2007-12-22 13:42:47, Richard D wrote:
Cant you, modify bootmem allocator to test with memtest patterns and then
use kexec (as Pavel suggested) to test the one where kernel was sitting
earlier?
I do not think you need to modify anything in kernel. Just use
/dev/mem to test areas that
Hi Ingo,
On Dec 22, 2007 3:40 PM, Ingo Molnar [EMAIL PROTECTED] wrote:
ah, didnt see that. Could you pick up bits of my patch because it seems
to do a better job, such as proper c99 initializer:
[snip]
also, my patch fixes all the warnings as well, not just the errors. So
please give it a
David Brownell wrote:
Which is why my suggestion was to have them both move up a level, with
host and peripheral side menus nested normally:
Device Drivers:
...
[ ] HID devices
Host side USB
Peripheral side USB
unfortunately 32 bit apps don't see the joysticks on a 64 bit system.
this prevents one playing X-Plane (http://www.x-plane.com/) or other
32-bit games with joysticks.
this is a known issue, and already raised several times:
http://readlist.com/lists/vger.kernel.org/linux-kernel/28/144411.html
Hi Alan
thanks for the input! This BIOS seems to be current, there are just two
beta BIOS available and as in the changelog there is nothing IRQ related
written (there is almost nothing in it) I don't think I want to flash
one of them, but here are the various options I tried:
noapic the one
[EMAIL PROTECTED] (Lennart Sorensen) writes:
On Fri, Dec 21, 2007 at 12:55:16PM +0100, Jan Engelhardt wrote:
o_O I better continue believing it is the subject. Because with
one extra word at the front, you can make this a complete sentence:
Please initialize [the] current offset in
Here is a patch that fixes a couple of issues with ttys in the stopped
state. See patch below for more details.
Note that this patch assumes that my previous patch from last month
(called tty-enable-the-echoing-of-c-in-the-n_tty-discipline.patch in
the -mm tree) has been applied, since part of
Arjan van de Ven wrote:
Hi,
Linus really wants the extended (4Kb) PCI configuration space (using MCFG acpi
table etc) to be opt-in, since there's many issues with it and most drivers
don't even use/need it. The idea behind opt-in is that if you don't use it, you
don't get to suffer the
On Sat, Dec 22, 2007 at 12:50:12AM -0800, Joe Perches wrote:
On Sat, 2007-12-22 at 09:33 +0100, Sam Ravnborg wrote:
arch/alpha/boot/mixc.c have:
#include ../../../lib/inflate.c
Right. thanks. Sorry for the noise.
It was the removal of the file I objected against - not thremoval of the
On Sat, 22 Dec 2007 09:20:06 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
Arjan van de Ven wrote:
Hi,
Linus really wants the extended (4Kb) PCI configuration space
(using MCFG acpi table etc) to be opt-in, since there's many issues
with it and most drivers don't even use/need it. The
[EMAIL PROTECTED] wrote on Fri, 21 Dec 2007 17:18 -0500:
On Fri, 2007-12-21 at 16:52 -0500, David Dillow wrote:
I'm getting the following oops when doing the following commands:
modprobe ib_srp
add targets(s) to ib_srp using sysfs
rmmod ib_srp
modprobe ib_srp
OOPS
I'm going to
I was thinking that by the time userspace is ready, the memory that can be
tested will be less.
-Original Message-
From: Pavel Machek [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 22, 2007 7:16 PM
To: Richard D
Cc: 'Matthew Bloch'; linux-kernel@vger.kernel.org
Subject: Re: Testing
On Sat, Dec 22, 2007 at 06:47:19AM -0800, Arjan van de Ven wrote:
Do you hate the name or the concept? I'm certainly open for a better name
I hate the concept. We should just fall back to type1 accesses on
mmconfig machines for all accesses below 64 bytes, as Ivan suggested.
--
Intel are
On Wed, 19 Dec 2007 21:32:44 +0100
Remy Bohmer [EMAIL PROTECTED] wrote:
We need to fix the break- and error handling though. But my vacation
starts tomorrow, so I probably won't be able to fix it until next
year.
In that case, I wish you very good holiday, and a happy new-year.
It was
On Sat, 22 Dec 2007 08:54:37 -0700
Matthew Wilcox [EMAIL PROTECTED] wrote:
On Sat, Dec 22, 2007 at 06:47:19AM -0800, Arjan van de Ven wrote:
Do you hate the name or the concept? I'm certainly open for a
better name
I hate the concept. We should just fall back to type1 accesses on
Pavel Machek wrote:
On Sat 2007-12-22 13:42:47, Richard D wrote:
Cant you, modify bootmem allocator to test with memtest patterns and then
use kexec (as Pavel suggested) to test the one where kernel was sitting
earlier?
I do not think you need to modify anything in kernel. Just use
Arjan van de Ven wrote:
Hi,
Linus really wants the extended (4Kb) PCI configuration space (using MCFG acpi
table etc) to be opt-in, since there's many issues with it and most drivers
don't even use/need it. The idea behind opt-in is that if you don't use it, you
don't get to suffer the
I have a rt2500pci card on an 64 bit system (Ubuntu) AMD X2 processor and i'm
trying latest vanilla kernels i've used a 2.6.24-rc5 kernel without mayor issues
(except that i have to issue a sudo iwconfig wlan0 rate 54M because it allways
connect at 1Mbit and it is dog slow) but now with
On Fri, 21 Dec 2007 17:18:52 -0500
David Dillow [EMAIL PROTECTED] wrote:
On Fri, 2007-12-21 at 16:52 -0500, David Dillow wrote:
I'm getting the following oops when doing the following commands:
modprobe ib_srp
add targets(s) to ib_srp using sysfs
rmmod ib_srp
modprobe ib_srp
Loic Prylli wrote:
On 12/20/2007 6:21 PM, Tony Camuso wrote:
And the MMCONFIG problem with enterprise systems and workstations, where
we do control the BIOS (for the most part), is due to known bugs in
certain versions of certain chipsets, HT1000, AMD8132, among them, not
the BIOS.
The lack
I need to resubmit this patch.
Resubmission will be in my next email.
It was a minor problem whereby the patch would advise the user
If a device isn't working, try pci=nommconf.
even when pci=mmconf was used at the command line.
One additional line of logic fixed it, but I would like
On Fri, 2007-12-21 at 22:24 -0800, Pete Zaitcev wrote:
When I tried it, usb-storage would not load with unresolved symbols.
It happens if child (usu_probe_thread) runs ahead of its parent
(usb_usual_init - usb_register - usu_probe). It's entirely possible,
depending on your scheduler.
I
This patch (v0.4.3) adds /sysfs/firmware/ibft/[initiator|targetX|ethernetX|
extensionX] directories along with text properties which export the the iSCSI
Boot Firmware Table (iBFT) structure.
What is iSCSI Boot Firmware Table? It is a mechanism for the iSCSI
tools to extract from the machine
I've no idea why this is occurring:
WARNING: at kernel/lockdep.c:700 look_up_lock_class()
Pid: 2068, comm: scsi_wq_3 Not tainted 2.6.24-rc6 #38
[c010535a] show_trace_log_lvl+0x1a/0x30
[c0105ce2] show_trace+0x12/0x20
[c010601c] dump_stack+0x6c/0x80
[c014696d] __lock_acquire+0x46d/0x10b0
On Sun, 2007-12-23 at 01:41 +0900, FUJITA Tomonori wrote:
I think that as Pete pointed out, srp_remove_one needs to call
srp_remove_host.
Can you try this?
If I need to escape family during the holidays, I'll test it from home.
Otherwise I'll be able to test on Wednesday.
Thanks for the
Andrew Morton wrote:
It would all look a lot more solid if this locking was retained and both
ecryptfs_tfm_exists() and ecryptfs_add_new_key_tfm() were designed to be
called under key_tfm_list_mutex.
Hmm good point, sorry for missing that. How's this look?
===
Jeff Moyer pointed
On Sat, 22 Dec 2007, Ingo Molnar wrote:
It's definitely not a stable ABI. slabtop tends to exit without any
error message on any slabinfo version number increase and I've seen
that happen several times in not so old kernels.
so because we sucked in the past we can continue to suck?
On Sat, 22 Dec 2007, Arjan van de Ven wrote:
On Sat, 22 Dec 2007 09:20:06 -0500
Jeff Garzik [EMAIL PROTECTED] wrote:
Yuck. And, Linus is just being silly. Wait a year then turn on
MMCONFIG :) It took PCI MSI a while to mature, but is finally
getting there.
That _really_ doesn't
On Sat 2007-12-22 21:00:11, Richard D wrote:
I was thinking that by the time userspace is ready, the memory that can be
tested will be less.
Which does not matter when you can test the rest using second
(kexec-ed) kernel, right?
On Sun 2007-12-23 02:36:14, David Newall wrote:
Pavel Machek wrote:
On Sat 2007-12-22 13:42:47, Richard D wrote:
Cant you, modify bootmem allocator to test with memtest patterns and then
use kexec (as Pavel suggested) to test the one where kernel was sitting
earlier?
I do not think you
* Linus Torvalds [EMAIL PROTECTED] wrote:
It's definitely not a stable ABI. slabtop tends to exit without
any error message on any slabinfo version number increase and I've
seen that happen several times in not so old kernels.
so because we sucked in the past we can continue to
On Sat, Dec 22, 2007 at 10:22:29AM -0600, Robert Hancock wrote:
Arjan van de Ven wrote:
Hi,
Linus really wants the extended (4Kb) PCI configuration space (using MCFG
acpi table etc) to be opt-in, since there's many issues with it and most
drivers don't even use/need it. The idea behind
On Sat, Dec 22, 2007 at 10:01:37AM -0800, Linus Torvalds wrote:
Well, I do have to admit that I'm not a huge fan of /proc/slabinfo, and
the fact that there hasn't been a lot of complaints about it going away
does seem to imply that it wasn't a very important ABI.
I'm the first to stand up
On Sat, 2007-12-22 at 15:31 +0100, Sam Ravnborg wrote:
I looked at how inflate was used:
$ grep inflate */boot/Makefile
alpha/boot/Makefile:$(obj)/misc.o: lib/inflate.c
= redundandt dependency, can be deleted
A cleanup of all this is needed.
Perhaps it's better to move lib/inflate.c to
* Ingo Molnar [EMAIL PROTECTED] wrote:
I'd also not rely on the fact that only a few people are complaining.
Most people, even 2.6.24-rc early adopters, still use SLAB because
early adopters typically use their .23 .config and do a 'make
oldconfig' - which picks up SLAB. So SLUB use will
As a followup to the thread regarding slabinfo and Andrew's
earlier query about updating slabtop.
watch -n1 slabinfo -S
seems to be a reasonable replacement for slabtop. The only
missing functionality are some hotkeys missing: you have to restart
now to get a different sort order (and to
On Sat, Dec 22, 2007 at 12:12:06AM -0800, Andrew Morton wrote:
This patch takes the total text size of the affected nine files from 74167
bytes up to 75066 on i386. This is core, core kernel. Ouch.
Yeah, as you note below - this should be un-inlined.
It's also pretty fragile. We now have
Hello!
Just make it so. The name is fine, the concept is unavoidable. The people
who complain are whiners that haven't ever had to deal with the fact that
there are broken machines around.
I complain as well as the maintainer of the pciutils. Breaking all userspace
accesses to extended
On Tue, 18 Dec 2007 17:06:24 +
Matthew Bloch [EMAIL PROTECTED] wrote:
Hi - I'm trying to come up with a way of thoroughly testing every byte
of RAM from within Linux on amd64 (so that it can be automated better
than using memtest86+), and came up with an idea which I'm not sure is
On Sat, 22 Dec 2007 20:30:58 +0100
Martin Mares [EMAIL PROTECTED] wrote:
Hello!
Just make it so. The name is fine, the concept is unavoidable. The
people who complain are whiners that haven't ever had to deal with
the fact that there are broken machines around.
I complain as well as
There seems to have two regressions between the kernels from yesterday and
before-yesterday
On the kernel -git7 what didnt happened on -git6
1) My hard disk is /dev/hda, but when I have an usb key sticked in /dev/sba,
and run lilo then, then it dont boot but give L99 99 99 99 ... error. When I
On Sat, 22 Dec 2007 15:04:16 +0100
Benny Amorsen [EMAIL PROTECTED] wrote:
It is a bit of a mystery why the kernel is ordering me to initialize
the current offset of xfs_file_readdir though. I don't know how to do
that, so I guess it's lucky that I don't use XFS. Who knows what would
happen if
Rik van Riel wrote:
On large memory systems, the VM can spend way too much time scanning
through pages that it cannot (or should not) evict from memory. Not
only does it use up CPU time, but it also provokes lock contention
and can leave large systems under memory presure in a catatonic state.
On Sat, 22 Dec 2007 04:35:59 -0800
Arjan van de Ven [EMAIL PROTECTED] wrote:
From: Arjan van de Ven [EMAIL PROTECTED]
Subject: opt the sky2 driver into using extended config space
So far, the sky2 driver is the only one I've identified (with a quick grep)
that actually would be using
Hello!
it's not just a couple of chipsets, it's actually
* a whole lot of bioses
* at least one whole CPU generation
* ..
* ..
Do you really want to code all of that into your userspace access code as
well?
No, I certainly don't. But I expect this to be handled reasonably in the
Pavel Machek wrote:
memtest has following problems:
0) it is kind of hard to run memtest over ssh
It's kind of hard to run anything over SSH if it has to be run before
userspace is up. But the kernel can collect results from a modified
memtest, after it chains back.
(CC'ing linux-input, as that is the relevant subsystem list for wistron-btns).
Rémi Hérilier wrote:
To use my previous patch (wistron_btns support for fujitsu-siemens amilo
pro edition v3505) with my laptop, I need to make the wistron module
compile for x86_64. It is based on Linux 2.4.24-rc4
On Sat, 2007-12-22 at 04:31 -0800, Arjan van de Ven wrote:
Hi,
Linus really wants the extended (4Kb) PCI configuration space (using MCFG
acpi table etc) to be opt-in, since there's many issues with it and most
drivers don't even use/need it. The idea behind opt-in is that if you don't
1 - 100 of 390 matches
Mail list logo
