On Wed, Jun 06, 2007 at 11:40:58AM -0700, Jared Hulbert wrote:
> > The embedded people already use them
> >on flash which is a little dumb, but now we add even more cludge for
> >a non-block based access.
>
> Please justify your assertion that using cramfs on flash is dumb.
> What would be not
Hi!
This issue is solved with 2.6.22-rc for me. The second core is up with
the same speed as core 1 (Bogomips are the same, too).
- Stefan Prechtel
2007/6/6, Peter Oruba <[EMAIL PROTECTED]>:
I'm sorry, I am not able to reproduce this issue (using 2.6.21.3). Everything
works fine on my Turion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Miller wrote:
> Since the valid range of "domain" values is quite small,
> we could avoid the new system call by cribbing some of the
> upper bits of the 'domain' argument.
>
> Valid existing programs pass in valid 'domain' values and
> thus
From: Davide Libenzi <[EMAIL PROTECTED]>
Date: Wed, 6 Jun 2007 15:52:31 -0700 (PDT)
> I have no huge preferences. If not the slight one of using the same flags
> for open() and socket{2}() (O_NONSEQFD). If we overload socket() we may
> need to fight with existing O_* flags. OTOH the current
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
Nope, I booted with only netconsole= options. I have a lot of HW in
the box and I guess the buffer is too small. Not sure where to
change it in the kernel. Looking..
It's called "kernel log
On Wed, 6 Jun 2007, Stephane Eranian wrote:
> > Is this ia64 patch the one you mentioned that you did not post to LKML
> > because it was too large in patch 0? Is there any way you could break
> > that patch up itself and post it for comments?
> >
> Yes, this is the patch. It would be hard to
On 06/06/2007 04:47 PM, Ian McDonald wrote:
> Hi there,
>
> We've seen a report of a problem with dccp_probe as shown below. The
> user has also verified that it occurs in tcp_probe as well. This is on
> Dave Miller's tree but that currently tracks Linus' tree quite
> closely. I do note that it
On Wed, 6 Jun 2007, Randy Dunlap wrote:
On Wed, 6 Jun 2007 15:28:43 -0700 Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
Nope, I booted with only netconsole= options. I have a lot of HW in
the box and I guess the buffer is too small. Not sure where to
change
> The sys_accept() system call has been modified to return a file
> descriptor inside the non-sequential area, if the listening fd is.
> The sys_socketcall() system call has been also changed to support
> a new SYS_SOCKET2 indentifier.
This still all seems really really ugly. Is there anything
On Wed, 6 Jun 2007, David Miller wrote:
> From: Davide Libenzi <[EMAIL PROTECTED]>
> Date: Wed, 06 Jun 2007 15:30:31 -0700
>
> > This patch implement a new syscall sys_socket2(), that accepts an
> > extra "flags" parameter:
> >
> > int socket2(int domain, int type, int protocol, int flags);
> >
On Wed, 6 Jun 2007, Randy Dunlap wrote:
On Wed, 6 Jun 2007 15:28:43 -0700 Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
Nope, I booted with only netconsole= options. I have a lot of HW in
the box and I guess the buffer is too small. Not sure where to
change
From: Davide Libenzi <[EMAIL PROTECTED]>
Date: Wed, 06 Jun 2007 15:30:31 -0700
> This patch implement a new syscall sys_socket2(), that accepts an
> extra "flags" parameter:
>
> int socket2(int domain, int type, int protocol, int flags);
>
> The flags parameter is used to pass extra flags to
Ingo,
I saw lots of problems trying to apply the latest rt-preempt patch.
Maybe some bits got included by mistake in the patch?
Here's what I saw:
$ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.21.3.tar.bz2
$ wget http://people.redhat.com/mingo/realtime-preempt/patch-2.6.21.3-rt9
$
> > I wasn't paying close enough attention to understand why you couldn't
> > do it in two steps - make the container, and then populate it with
> > resources.
>
> Sorry, please clarify - are you saying that now you do understand, or
> that I should explain?
Could you explain -- I still don't
Jeff Dike writes:
> On Wed, Jun 06, 2007 at 12:50:04PM +1000, Benjamin Herrenschmidt wrote:
> > Yeah, synchronous signals should probably never be delivered to another
> > process, even via signalfd. There's no point delivering a SEGV to
> > somebody else :-)
>
> Sure there is. UML does exactly
Somehow an smp_processor_id() survived the transition to passing the
cpu around.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Cc: Jan Beulich <[EMAIL PROTECTED]>
---
arch/i386/xen/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 6/6/07, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
Lennart Sorensen wrote:
>
> Seems like an improvement to me. To fully explain how it could be 3 or
> 3.5 or 3.25 or who knows how many GB you can actually use without PAE
> would probably require writing a small novel. Certainly talking
On Wed, 6 Jun 2007 15:28:43 -0700 Jesse Barnes wrote:
> On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
> > Nope, I booted with only netconsole= options. I have a lot of HW in
> > the box and I guess the buffer is too small. Not sure where to
> > change it in the kernel. Looking..
>
>
Quoting Paul Jackson ([EMAIL PROTECTED]):
> > Would it then make sense to just
> > default to (parent_set - sibling_exclusive_set) for a new sibling's
> > value?
>
> Which could well be empty, which in turn puts one back in the position
> of dealing with a newborn cpuset that is empty (of cpus or
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
Nope, I booted with only netconsole= options. I have a lot of HW in
the box and I guess the buffer is too small. Not sure where to
change it in the kernel. Looking..
It's called "kernel log
On Wed, Jun 06, 2007 at 04:36:22PM -0500, Eric Sandeen wrote:
> Chris Wright wrote:
> > * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> >> From: Eric Sandeen <[EMAIL PROTECTED]>
> >> Subject: sysfs: store sysfs inode nrs in s_ino to avoid readdir oopses
> >>
> >> Backport of
> >>
[ Expand, correct and clarify comments; minor code change. ]
Most of the time we can simply use the iret instruction to exit the
kernel, rather than having to use the iret hypercall - the only
exception is if we're returning into vm86 mode, or from delivering an
NMI (which we don't support yet).
On Wed, 6 Jun 2007, Benjamin Herrenschmidt wrote:
> On Tue, 2007-06-05 at 20:37 -0700, Linus Torvalds wrote:
>
> > I agree that it would be a limitation, but it would be a sane one.
> >
> > How about we try to live with that limitation, if only to avoid the issue
> > of having the private
Strays left over from the first implementation of
paravirt_disable_iospace().
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/i386/xen/setup.c |2 --
1 file changed, 2 deletions(-)
===
---
Make sure everything is backed out if it fails.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/i386/kernel/paravirt.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
===
---
This laptop have a nVidia 10de:0244 with 256Mb of RAM. No shared memory.
Reinaldo de Carvalho
00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express
Bridge (rev a2) (prog-if 00 [VGA])
Subsystem: Hewlett-Packard Company Unknown device 30b5
Control: I/O+ Mem+
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
Nope, I booted with only netconsole= options. I have a lot of HW in
the box and I guess the buffer is too small. Not sure where to
change it in the kernel. Looking..
It's called "kernel log
Wire the new sys_socket2 system call to the x86-64 architecture.
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
Index: linux-2.6.mod/arch/x86_64/ia32/ia32entry.S
===
---
This patch implement a new syscall sys_socket2(), that accepts an
extra "flags" parameter:
int socket2(int domain, int type, int protocol, int flags);
The flags parameter is used to pass extra flags to the kernel, and is
at the moment used to select the file descriptor allocations inside
the
Wire the new sys_nonseqfd system call to the x86-64 architecture.
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
Index: linux-2.6.mod/arch/x86_64/ia32/ia32entry.S
===
---
Wire the new sys_nonseqfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
Index: linux-2.6.mod/arch/i386/kernel/syscall_table.S
===
---
This patch makes the kernel use the fdmap allocator for sequential (legacy)
and non-sequential file descriptor allocations. It consolidates all scattered
fdtable internal members accesses into fdmap.{c,h}.
Semantics of sequential file descriptor allocations remains unchanged. They
are still
This patch implement a new syscall sys_nonseqfd():
int nonseqfd(int fd, int flags);
The sys_nonseqfd() syscall can be used to map an existing file
descriptor inside the non-sequential fd area.
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
Index: linux-2.6.mod/fs/fcntl.c
This patch introduces a new O_NONSEQFD flag for the sys_open()
system call. Using such flag, the caller can ask the kernel to allocate
the file descriptor inside the non-sequential area.
Signed-off-by: Davide Libenzi <[EMAIL PROTECTED]>
- Davide
Index: linux-2.6.mod/fs/open.c
Core code for the fdmap implementation. Random allocation, exact allocation,
de-allocation and lookup are all O(1) operations. It also support the "legacy"
sequential (compact) file descriptor allocation, that is O(N) like the old
fdtable implementation.
Like the old "struct fdtable", fdmap is RCU
On Wednesday, June 6, 2007 3:26 pm Justin Piszcz wrote:
> Nope, I booted with only netconsole= options. I have a lot of HW in
> the box and I guess the buffer is too small. Not sure where to
> change it in the kernel. Looking..
It's called "kernel log buffer size" and it's in "General setup".
David,
On Tue, Jun 05, 2007 at 06:34:56PM -0700, David Rientjes wrote:
>
> > > > +int pfm_get_task(struct pfm_context *ctx, pid_t pid, struct
> > > > task_struct **task)
> > > > +{
> > >
> > > This function could be marked static even though it's exported through
> > > perfmon.h in patch 13.
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:13 pm Justin Piszcz wrote:
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:03 pm Justin Piszcz wrote:
Mem: 8039620k total, 7936472k used, 103148k free, 708k
buffers Mem: 8039608k total,
On Wednesday, June 6, 2007 3:13 pm Justin Piszcz wrote:
> On Wed, 6 Jun 2007, Jesse Barnes wrote:
> > On Wednesday, June 6, 2007 3:03 pm Justin Piszcz wrote:
> >> Mem: 8039620k total, 7936472k used, 103148k free, 708k
> >> buffers Mem: 8039608k total, 969380k used, 7070228k free,
>
Quoting Matt Helsley ([EMAIL PROTECTED]):
> This patch avoids holding the mmap semaphore while walking VMAs in response to
> programs which read or follow the /proc//exe symlink. This also
> allows
> us to merge mmu and nommu proc_exe_link() functions. The costs are holding the
> task lock, a
As a followup to the message I posted earlier, I found that the
following patch restores the old behavior of allowing maxcpus to
effectively turn off hyperthreading. In case you missed my earlier
message, in 2.6.16 through at least 2.6.19 using the maxcpus trick
will fail to use all of
On Wed, 2007-06-06 at 20:48 +0200, Michal Piotrowski wrote:
> Andrew Morton pisze:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> >
>
> Kay, your patch gregkh-driver-block-device.patch breaks Fedora 7 initrd
>
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:03 pm Justin Piszcz wrote:
Mem: 8039620k total, 7936472k used, 103148k free, 708k
buffers Mem: 8039608k total, 969380k used, 7070228k free,
1232k buffers
I am curious, why does the patch != the mem=8832M?
Lennart Sorensen wrote:
>
> Seems like an improvement to me. To fully explain how it could be 3 or
> 3.5 or 3.25 or who knows how many GB you can actually use without PAE
> would probably require writing a small novel. Certainly talking about
> address space instead of amounts of physical
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix printk format warnings for schedstats:
fs/proc/base.c:309: warning: format '%lu' expects type 'long unsigned int', but
argument 3 has type 'long long unsigned int'
fs/proc/base.c:309: warning: format '%lu' expects type 'long unsigned int', but
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 3:03 pm Justin Piszcz wrote:
Mem: 8039620k total, 7936472k used, 103148k free, 708k
buffers Mem: 8039608k total, 969380k used, 7070228k free,
1232k buffers
I am curious, why does the patch != the mem=8832M?
On Wednesday, June 6, 2007 3:03 pm Justin Piszcz wrote:
> Mem: 8039620k total, 7936472k used, 103148k free, 708k
> buffers Mem: 8039608k total, 969380k used, 7070228k free,
> 1232k buffers
>
> I am curious, why does the patch != the mem=8832M?
I'm not sure... can you post your
* Eric Sandeen ([EMAIL PROTECTED]) wrote:
> Well, my backport of Tejun's patch explicitly doesn't use ida for just
> that reason...
>
> It uses a simple counter instead (which may give dup inode numbers, but
> I think we have that today, and at least this shouldn't oops...)
Right, my point is
On 06/06/2007 11:26 PM, Pavel Machek wrote:
Yes, it's internal but given that this is open-source
which, optimistically, is read many more times than it's
written one should still strive for code that reads nice
as far as I'm concerned. It's obviously also not hugely
important but it's just
Mem: 8039620k total, 7936472k used, 103148k free, 708k buffers
Mem: 8039608k total, 969380k used, 7070228k free, 1232k buffers
I am curious, why does the patch != the mem=8832M?
Justin.
On Wed, 6 Jun 2007, Justin Piszcz wrote:
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On
1. I use netconsole on almost all of my machines.
2. When I reboot one of them, it sends the kernel messages to the console
logging server.
3. However, whenever I reboot it spams the console and every xterm open
with the following:
Message from [EMAIL PROTECTED] at Wed Jun 6 17:43:10 2007
On Wed, Jun 06, 2007 at 01:56:41PM -0700, Venki Pallipadi wrote:
>
>
> Documentation changes based on Pavel's feedback.
Can you also update Documentation/00-INDEX file please.
-Anil
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Lennart Sorensen wrote:
> On Wed, Jun 06, 2007 at 02:12:22PM +0200, Bodo Eggert wrote:
> > Change the description of CONFIG_*HIGHMEM* to reflect "lost" memory due to
> > PCI space and the existence of the NX flag.
> >
> > Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
> > ---
> > I made this
On Wed, 06 Jun 2007, Björn Steinbrink wrote:
> HDAPS support is available, revision is MB2IA60A.
That would usually rule out the possibility of it being the firmware, but we
have different disks, so different firmware.
It looks like I will have to try 2.6.22 to know for sure.
--
"One disk to
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On some machines, buggy BIOSes don't properly setup WB MTRRs to
cover all available RAM, meaning the last few megs (or even gigs)
of memory will be marked uncached. Since Linux tends to allocate
from high memory addresses first, this causes the machine
[Please Cc on reply]
Hi,
I recently bought an USB MIDI interface from ESI (called “ESI MIDI Mate”). It
claims to work with Linux, but doesn't -- I've already asked the manufacturer
for an explanation, but as I was impatient, I hacked a bit on the drivers to
actually make it work...
The
On Wed, 2007-06-06 at 23:33 +0200, Martin Peschke wrote:
>
> struct statistic_interface {
> /* private: */
> struct list_head list;
> - struct dentry *debugfs_dir;
> - struct dentry *data_file;
> - struct dentry *def_file;
> +
Chris Wright wrote:
> * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>> From: Eric Sandeen <[EMAIL PROTECTED]>
>> Subject: sysfs: store sysfs inode nrs in s_ino to avoid readdir oopses
>>
>> Backport of
>>
On 2007.06.06 18:03:37 -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 06 Jun 2007, Björn Steinbrink wrote:
> > On 2007.06.06 13:48:54 -0300, Henrique de Moraes Holschuh wrote:
> > > I am also using libata PIIX like the first person reporting the problem,
> > > but
> > > it is a PATA drive
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> From: Eric Sandeen <[EMAIL PROTECTED]>
> Subject: sysfs: store sysfs inode nrs in s_ino to avoid readdir oopses
>
> Backport of
>
This patch converts the lock statistics to a user of lib/statistic.c,
resulting in somewhat simpler code (a 300 lines-of-code diet).
Anyone interested in the details of code duplication might want to study:
- lock_time_inc() vs. statistic_add_util()
- lock_stats() vs. statistic_merge()
-
This patch chips a structure describing a set of statistics from the
structure used to manage the user interface (files) for a set of
statistics. The benefit of this split and small API change is that
users can have multiple sets of statistics per file.
For example, a user which reports
Hi!
> >>No, what we have is a sizeof(pointer) sized pointer
> >>pointing to an
> >>object of size zero. ZERO_SIZE_PTR is butt-ugly. With
> >>a really ugly butt.
> >
> >It doesn't matter. It will never, ever, be used by
> >anything except the
> >kmalloc internals. No client code should ever
Cleaning up inclusion of header files. Don't want to create
an include hell for users.
Maintain void pointers instead of dentry pointers for debugfs files.
We never poke inside those dentries anyway. We just keep them in order
to pass them back as a kind of handle to debugfs on cleanup.
Getting
Statistics code cleanups. Would not have been needed for the following
changes - just done along the way.
- make function void
- found more handy names for a few identifiers
Signed-off-by: Martin Peschke <[EMAIL PROTECTED]>
---
drivers/s390/scsi/zfcp_def.h |4
include/linux/statistic.h
>From browsing through file2alias.c, I have the impression there's a
missing TO_NATIVE() conversion in the handling of 16-bit (hence,
endian-affected) i2c IDs.
This will cause the module aliases to be incorrect when cross-compiling
for a system with a different endianness. Is that correct?
If
We can save many lines of code in the lock contention tracking patches
by using some common code which implements statistics in a generic way.
Data is still gathered per cpu; output goes to debugfs files. Several
ideas that went into the lock contention tracking patches can be found
in the
On Wed, Jun 06, 2007 at 01:24:39PM -0700, Andrew Morton wrote:
>
> > And for some reason the whole Cryptographic API is under the main level of
> > menu
> > (please find .config and menu.png attached).
>
> err, yes. git-cryptodev.patch did that. Herbert is being immodest ;)
Is it this patch?
On Wed, Jun 06, 2007 at 05:21:51PM -0400, Jeff Garzik wrote:
> > Ok, patch fixed, works for me with Calgary. Andi, it looks like you
> > added the acpi.c NUMA bits originally, perhaps you could test and/or
> > ack them?
>
> Just so there is no misunderstanding, I added the allocation bits.
>
>
Will give it a shot.
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 1:37 pm Justin Piszcz wrote:
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 1:28 pm Jesse Barnes wrote:
Against what kernel version does this patch apply?
Um... git as of
On Wed, Jun 06, 2007 at 01:29:34PM -0700, Andrew Morton wrote:
> >asmlinkage long sys_time_pps_find(int cmd, int __user *source,
> > char __user *name, int namelen,
> > char __user *path, int pathlen);
Try to
From: Randy Dunlap <[EMAIL PROTECTED]>
__exit function is used by both init and exit routines, so it cannot
be marked __init. (from allyesconfig)
WARNING: drivers/built-in.o(.text+0x9b83cf): Section mismatch: reference to
.exit.text: (between 'divasfunc_exit' and 'didd_callback')
> Ok, patch fixed, works for me with Calgary. Andi, it looks like you
> added the acpi.c NUMA bits originally, perhaps you could test and/or
> ack them?
Just so there is no misunderstanding, I added the allocation bits.
No idea who added the direct usage of ->sysdata for NUMA info.
> diff -r
On 6/6/07, Lennart Sorensen <[EMAIL PROTECTED]> wrote:
[...]
A better description would be:
"Select this if you have a 32-bit processor and memory mapped in the 1GB
to 4GB address range."
[...]
That one would be better as:
"Select this if you have a 32-bit processor and ram mapped in the
On Wed, Jun 06, 2007 at 11:02:45PM +0200, Filippo Carletti wrote:
> > Just for information, have you built it already ?
>
> I successfully built the kernel but I haven't tested it because I have
> only an ICH8 based mb.
OK fine. It will save me a build then. I do not have the hardware either.
I
Ack.
Thanks,
Venki
>-Original Message-
>From: Thomas Gleixner [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, June 06, 2007 2:38 AM
>To: Andrew Morton
>Cc: Pallipadi, Venkatesh; Stable Team; LKML; Len Brown; Ingo
>Molnar; Arjan van de Ven; Andi Kleen; Udo A. Steinberg; Dave Jones
On Tue, Jun 05, 2007 at 01:29:05PM +0300, Muli Ben-Yehuda wrote:
> On Mon, Jun 04, 2007 at 05:05:51PM -0400, Jeff Garzik wrote:
> >
> > This patch introduces struct pci_sysdata to x86 and x86-64, and
> > converts the existing two users (NUMA, Calgary) to use it.
> >
> > This eliminates the
On Wed, 06 Jun 2007, Björn Steinbrink wrote:
> On 2007.06.06 13:48:54 -0300, Henrique de Moraes Holschuh wrote:
> > On Wed, 06 Jun 2007, Björn Steinbrink wrote:
> > > On 2007.06.06 12:44:42 -0300, Henrique de Moraes Holschuh wrote:
> > > > On Wed, 06 Jun 2007, Robert Hancock wrote:
> > > > > >I
> Just for information, have you built it already ?
I successfully built the kernel but I haven't tested it because I have
only an ICH8 based mb.
Ciao,
Filippo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Documentation changes based on Pavel's feedback.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/Documentation/cpuidle/sysfs.txt
===
--- linux-2.6.22-rc-mm.orig/Documentation/cpuidle/sysfs.txt
On Wednesday 06 June 2007 10:07:37 Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
Patch 'usb-try-to-debug-bug-8561' triggers when I plug in a usb flash drive:
[10998.881000] usb 1-10: new high speed USB device using ehci_hcd and
Introduce a governor rating scheme to pick the right governor by default.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/include/linux/cpuidle.h
===
---
Make default cpuidle sysfs to show current_governor and current_driver in
read-only mode. More elaborate available_governors and available_drivers with
writeable current_governor and current_driver interface only appear with
"cpuidle_sysfs_switch" boot parameter.
Signed-off-by: Venkatesh
Change the C-state early break out algorithm in menu governor.
We only look at early breakouts that result in wakeups shorter than idle state's
target_residency. If such a breakout is frequent enough, eliminate the
particular idle state upto a timeout period.
Signed-off-by: Venkatesh Pallipadi
Fix the uninitialized usage of ret.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/drivers/cpuidle/sysfs.c
===
--- linux-2.6.22-rc-mm.orig/drivers/cpuidle/sysfs.c 2007-06-04
On Wed, Jun 06, 2007 at 10:16:14PM +0200, Filippo Carletti wrote:
> >>> The original patch contained also this lines (that I omitted):
> >>> + /* JMicron-specific fixup: make sure we're in AHCI mode */
> >>> + if (pdev->vendor == 0x197b)
> >>> +
Keep /proc/acpi/processor/CPU*/power around for a while as powertop depends
on it. It will be marked deprecated and removed in future. powertop can use
cpuidle interfaces instead.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/drivers/acpi/processor_idle.c
Compile fix for menu governor.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc-mm/drivers/cpuidle/governors/menu.c
===
--- linux-2.6.22-rc-mm.orig/drivers/cpuidle/governors/menu.c2007-06-01
Len,
Following are a bunch of small changes to cpuidle trying to prepare it
for mainline. Some of the changes are just the compile timer errors/warnings
and you probably already have them in acpi-test.
Should apply cleanly to latest acpi-test. Please include in acpi-test.
Thanks,
Venki
This
Hi all,
I've just released Linux 2.4.34.5, with extracts from 2.4.35-pre5.
The most important one is the fix for the regression I introduced
while fixing CVE-2007-1353 (bluetooth). Basically, I turned a memory
leak bug into a memory corruption bug. Two minor bluetooth fixes have
all been
Hi
On 6/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Wed, 6 Jun 2007 21:32:36 +0200 Mariusz Kozlowski <[EMAIL PROTECTED]> wrote:
> Hello,
>
> This is from my P4 sony vaio laptop.
>
> These warnings still there:
>
> drivers/input/keyboard/Kconfig:170:warning: 'select' used by config
On Wednesday, June 6, 2007 1:37 pm Justin Piszcz wrote:
> On Wed, 6 Jun 2007, Jesse Barnes wrote:
> > On Wednesday, June 6, 2007 1:28 pm Jesse Barnes wrote:
> >>> Against what kernel version does this patch apply?
> >>
> >> Um... git as of b4946ffb1860597b187d78d61ac6504177eb0ff8. Sorry I
> >>
On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> On Tuesday 05 June 2007 09:29:11 pm Andrey Borzenkov wrote:
> > On Wednesday 06 June 2007, Bjorn Helgaas wrote:
> > > Something's wrong with this strategy. The BIOS is telling us that an
> > > SMCf010 device is present, active, and responds at io
Hi all,
I've just released Linux 2.4.35-pre5.
It contains two important fixes. One is a fix for a regression I
introduced when trying to fix CVE-2007-1353 (bluetooth), which
fortunately was noticed by Marcel Holtmann. Basically, I turned
a memory leak bug into a memory corruption bug :-(
The
On Wed, 6 Jun 2007, Jesse Barnes wrote:
On Wednesday, June 6, 2007 1:28 pm Jesse Barnes wrote:
Against what kernel version does this patch apply?
Um... git as of b4946ffb1860597b187d78d61ac6504177eb0ff8. Sorry I
should have updated before spinning the patch (will do now).
Appears to
On Wednesday, June 6, 2007 1:28 pm Jesse Barnes wrote:
> > Against what kernel version does this patch apply?
>
> Um... git as of b4946ffb1860597b187d78d61ac6504177eb0ff8. Sorry I
> should have updated before spinning the patch (will do now).
Appears to apply cleanly to git head as of a minute
On Tue, 5 Jun 2007 09:25:01 +0200 Rodolfo Giometti <[EMAIL PROTECTED]> wrote:
> Hello,
>
> after a little studing on new generic netlink interface and some
> letters with Andrew Morton I decided to drop using the netlink API at
> all and start using new specific syscalls.
>
> Looking at current
On Wednesday, June 6, 2007 1:26 pm Justin Piszcz wrote:
> On Wed, 6 Jun 2007, Jesse Barnes wrote:
> > On some machines, buggy BIOSes don't properly setup WB MTRRs to
> > cover all available RAM, meaning the last few megs (or even gigs)
> > of memory will be marked uncached. Since Linux tends to
Hello,
This patch balances parenthesis in i5000 edac code.
Signed-off-by: Mariusz Kozlowski <[EMAIL PROTECTED]>
drivers/edac/i5000_edac.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -upr linux-2.6.22-rc4-mm1-a/drivers/edac/i5000_edac.c
Alan Cox wrote:
http://thread.gmane.org/gmane.linux.kernel/530099
It seems we're losing interrupts from the CFA device. Any ideas?
Alan probably knows more, but ISTR some CFA PCMCIA devices that needed
polling...
Not that I know of. Not devices anyway - there are embedded
101 - 200 of 1053 matches
Mail list logo
