On Mon, Feb 12, 2007 at 10:51:44AM -0800, Tejun Heo wrote:
> Conversion to resource-managed iomap was buggy causing init failures
> on both vt6420 and 6421 - BAR5 wasn't mapped for both controllers
> while on vt6420 sata_via tried to map BAR0-4 twice. Fix it.
>
> DO NOT APPLY YET.
> ---
> Markus,
On 2/12/07, Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
On Mon, Feb 12, 2007 at 12:15:22AM -0800, [EMAIL PROTECTED] wrote:
> +void container_fork(struct task_struct *child)
> +{
> + task_lock(current);
Can't this be just rcu_read_lock()?
In this particular patch (which is an almost verb
> > Index: linux/arch/i386/kernel/alternative.c
> > ===
> > --- linux.orig/arch/i386/kernel/alternative.c
> > +++ linux/arch/i386/kernel/alternative.c
> > @@ -4,7 +4,6 @@
> > #include
> > #include
> > #include
> > -#include
> >
Hesse, Christian wrote:
On Saturday 10 February 2007 14:23, Hesse, Christian wrote:
On Friday 09 February 2007 22:12, James Ketrenos wrote:
We are pleased to announce the availability of a new driver for the
Intel PRO/Wireless 3945ABG Network Connection adapter.
...
Oh, I forgot one note: "mak
Documentation for cpuidle infrastructure
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Signed-off-by: Adam Belay <[EMAIL PROTECTED]>
Signed-off-by: Shaohua Li <[EMAIL PROTECTED]>
Index: linux-2.6.21-rc-mm/Documentation/cpuidle/core.txt
==
On Mon, Feb 12, 2007 at 06:37:38PM +0100, Mark de Vries wrote:
> I've been googeling for about an hour now and can't find an answer to:
> What type of CPU should I select when compiling a recent 2.6 kernel if I
> have a VIA Esther CPU?
> stepping: 9
config MVIAC3_2
bool "VIA C3-2
Hookup ACPI C-states onto generic cpuidle infrastructure.
drivers/acpi/procesor_idle.c is now a ACPI C-states driver that registers as
a driver in cpuidle infrastructure and the policy part is removed from
drivers/acpi/processor_idle.c. We use governor in cpuidle instead.
Signed-off-by: Shaohua
Introducing 'cpuidle', a new CPU power management infrastructure to manage
idle CPUs in a clean and efficient manner.
cpuidle separates out the drivers that can provide support for multiple types
of idle states and policy governors that decide on what idle state to use
at run time.
A cpuidle drive
There is no prompt for STACKTRACE, so it is enabled only when 'select'ed.
FAULT_INJECTION depends on it, while LOCKDEP selects it. So FAULT_INJECTION
becomes visible in Kconfig only when LOCKDEP is enabled.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
Index: linux-2.6.git/lib/
On 12 Feb 2007 10:01:24 GMT, Miquel van Smoorenburg <[EMAIL PROTECTED]>
Check out /usr/include/bits/stat.h
Mike,
Thanks for the pointer. Got it. But as I mentioned to Andi, it doesn't
work with my filesystems (ext2, reiserfs). But at least it save me
from upgrading my glibc!
Thanks,
Jeff.
-
On Mon, 12 Feb 2007 18:56:29 +0100
"Martin A. Fink" <[EMAIL PROTECTED]> wrote:
> I have to store big amounts of data coming from 2 digital cameras to disk.
> Thus I have to write blocks of around 1 MB at 30 to 50 frames per second for
> a long period of time. So it is important for me that the h
After last week's experiment reducing size of task_struct on I was
curious to see what things are using up memory on the system and which
structs have the largest impact on the space used. /proc/slabinfo
provides information about the number objects allocated and their
sizes. With one line script
On 2/12/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
It should be always available in padding, even on older glibc. Given a
sufficiently
new kernel. The bigger problem is getting a file system that supports it.
Manpages are often outdated.
Andi,
Ok, found it. Thanks. You're right. ext2, reiserf
Conversion to resource-managed iomap was buggy causing init failures
on both vt6420 and 6421 - BAR5 wasn't mapped for both controllers
while on vt6420 sata_via tried to map BAR0-4 twice. Fix it.
DO NOT APPLY YET.
---
Markus, does this fix your problem?
diff --git a/drivers/ata/sata_via.c b/driv
On Fri, 9 Feb 2007, Jan Engelhardt wrote:
>
> On Feb 9 2007 15:29, linux-os (Dick Johnson) wrote:
>>>
>>> I was referring to "absolute memory", not the offset magic that assembler
>>> allows. After all, (reg+relativeOffset) will yield an absolute address.
>>> What I was out at: for machines that
On 2/12/07, Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
On Mon, Feb 12, 2007 at 12:15:27AM -0800, [EMAIL PROTECTED] wrote:
> This patch implements the BeanCounter resource control abstraction
> over generic process containers.
Forgive my confusion, but do we really need two-levels of resource
On Sun, Feb 04, 2007 at 01:26:48AM +0100, Tilman Schmidt wrote:
> Am 03.02.2007 17:09 schrieb Greg KH:
> > On Thu, Feb 01, 2007 at 05:13:45PM -0800, Andrew Morton wrote:
> >>> +/* dummy to shut up framework warning */
> >>> +static void gigaset_device_release(struct device *dev)
> >>> +{
> >>> + //
So, Linus,
when I get done porting 1.2.13 to my assembler-in-Bash, do you want me calling
it
"Linux"?
The scheduler will be a bit more nimble, of course, there will be a 3-stack
Forth-like interface to kernelspace, and the meta-superuser will run in Forreal
Mode, the
true 32-bit-unprotected mo
Hi all,
After latest ACPI merge /proc/acpi/ac_adapter/AC has gone fishing :
[~]> ls -al /proc/acpi/ac_adapter/
dr-xr-xr-x 2 root root 0 Şub 12 20:44 ADP1
[~]> ls -al /proc/acpi/ac_adapter/ADP1
-r--r--r-- 1 root root 0 Şub 12 20:44 state
This at least breaks HAL which thinks AC is always plugge
On 2/12/07, Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
On Mon, Feb 12, 2007 at 12:15:24AM -0800, [EMAIL PROTECTED] wrote:
> +/*
> + * Call css_get() to hold a reference on the container; following a
> + * return of 0, this container subsystem state object is guaranteed
> + * not to be destroye
On Mon, Feb 12, 2007 at 01:16:59AM -0500, Jeff Garzik wrote:
> On Sun, Feb 11, 2007 at 10:47:27AM -0800, Greg KH wrote:
> > It's in my queue and is on track to get in before 2.6.21-rc1 is out.
>
> It breaks the build for everyone, please fast-forward the merging of
> this.
It's now in Linus's tre
On Tue, Feb 06, 2007 at 10:37:37AM +, Christoph Hellwig wrote:
> On Tue, Feb 06, 2007 at 09:26:14PM +1100, Neil Brown wrote:
> > What would be the benefit of having private non-visible vfsmounts?
> > Sounds like a recipe for confusion?
> >
> > It is possible that mountd might start doing bind-
On 2/12/07, Cedric Le Goater <[EMAIL PROTECTED]> wrote:
>> +#include
>
> I did have a problem with this include. On s390 it didn't exist so I've
> just been running without it (with no problems). A quick 'find'
> suggests it only exists on x86_64, so I'd expect failures on all other
> arches.
Using The Misc filesystems sub-menu for layered/stackable filesystems only
makes it harder for users to find eCryptfs/Unionfs.
Additionally, the menu can be easily turned into a menuconfig, which could
be used to turn on any VFS/VM functionality required by layered filesystems
(there is none at th
From: Erez Zadok <[EMAIL PROTECTED]>
Be little gentler & updated the URLs
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
Signed-off-by: Josef 'Jeff' Sipek <[EMAIL PROTECTED]>
---
Documentation/filesystems/unionfs/00-INDEX |8 --
Documentation/filesystems/unionfs/issues.txt | 23 ++
Signed-off-by: Josef 'Jeff' Sipek <[EMAIL PROTECTED]>
---
fs/unionfs/rdstate.c | 11 ++-
fs/unionfs/union.h |1 +
2 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/fs/unionfs/rdstate.c b/fs/unionfs/rdstate.c
index 16ce1bf..e240285 100644
--- a/fs/unionfs/rdstate.c
+++
The following patches (also available though the git tree) fix few
cleanliness issues with Unionfs.
You can pull from 'master' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/unionfs.git
to receive the following:
Erez Zadok (1):
Unionfs: Documentation update
Josef 'Jeff' Si
On 2/11/07, Németh Márton <[EMAIL PROTECTED]> wrote:
Extend EV_LED handling code so that it can handle not
only two states (on/off) but also others. For example
a LED can blink using hardware acceleration. The code
changed so that it is similar to the code at EV_SND.
Hi,
I am not sure we wou
Hi,
On Feb 12 2007 12:50, Miklos Szeredi wrote:
>Index: linux/fs/filesystems.c
>===
>--- linux.orig/fs/filesystems.c2007-02-12 12:42:55.0 +0100
>+++ linux/fs/filesystems.c 2007-02-12 12:43:00.0 +0100
>@@ -4
Dmitriy Monakhov <[EMAIL PROTECTED]> writes:
> eCryptfs lower file handling code has several issues:
> - Retval from prepare_write()/commit_writ() was't checked to equality
> to AOP_TRUNCATED_PAGE.
> - In some places page was't unmapped and unlocked after error.
it is easy to retproduce:
Martin A. Fink wrote:
> This means, that the CPU is only 7.3 of 52.8 seconds working.
...
> It looks like
> the SATA driver simply blocks the CPU while doing whatever...
The system sleeps while waiting for the disk (actually, for the SATA
host port) to be done with its work.
As Andi explained, i
On 2/12/07, Martin A. Fink <[EMAIL PROTECTED]> wrote:
Am Montag, 12. Februar 2007 19:41 schrieben Sie:
I have to store big amounts of data coming from 2 digital cameras to disk.
Thus I have to write blocks of around 1 MB at 30 to 50 frames per second for
a long period of time. So it is important
On Mon, 12 Feb 2007, Andrew Burgess wrote:
On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
How does the kernel calculates the value it places in `/proc/stat' at
4th position (i.e. "idle: twiddling thumbs")?
..
Later small kernel module was developed that tried to time how much
time
On Mon, 12 Feb 2007, Con Kolivas wrote:
On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
Hello,
[..snip..]
The kernel looks at what is using cpu _only_ during the timer
interrupt. Which means if your HZ is 1000 it looks at what is running
at precisely the moment those 1000 timer tick
>i upgraded to vanilla kernel 2.6.20 and while i was using strongswan
>2.8.2 to setup an IPSEC VPN i got the following kernel Ooops.
>I had successfully established the same tunnel a few times, but key
>renegotiation caused a problem ( both ends did not renegotiate at the
>same time so the tunne
On Mon, 12 February 2007 17:51:30 +0100, Andi Kleen wrote:
>
> From: Andrew Morton <[EMAIL PROTECTED]>
>
> That stupid non-inlined-static function in bugs.h causes:
>
> include/asm/bugs.h:186: warning: 'check_bugs' defined but not used
>
> But fortunately the include isn't needed.
>
> Cc: Andi
On Mon, 12 February 2007 18:49:39 +0100, Jan Engelhardt wrote:
> On Feb 12 2007 10:40, Dave Jones wrote:
> >
> >The one problem with noatime is that mutt's 'new mail arrived' breaks
>
> Just why does not it use mtime then to check for New Mail Arrived, like
> bash does?
Just a guess: because it
Am Montag, 12. Februar 2007 19:41 schrieben Sie:
> "Martin A. Fink" <[EMAIL PROTECTED]> writes:
>
> Your mailer seems to be broken. It drops cc.
> >
> > If you call fsync in BSD then you get what you expect. anything that is
still
> > not on disk will be written. Afterwards fsync returns... So
Hello.
Marc St-Jean wrote:
>> > Fourth attempt at the serial driver patch for the PMC-Sierra MSP71xx
>>device.
I think you need to submit your patch to Andrew Morton since it
requires a patch from his tree.
OK, will do.
In fact, since the serial drivers are not maintained anymore,
Hi,
On Feb 12 2007 10:40, Dave Jones wrote:
> > > Whilst on the subject of RELATIME, is there any good reason why
> > > not to make this a default mount option ?
> >
> > Ubuntu has been shipping with noatime as the default for some time
> > now, with no obvious problems (I'm running Ubuntu). I s
Hi,
I've been googeling for about an hour now and can't find an answer to:
What type of CPU should I select when compiling a recent 2.6 kernel if I
have a VIA Esther CPU?
Please CC me, I'm not on the list.
Thanks & Regards,
Mark.
~$ cat /proc/cpuinfo
processor : 0
vendor_id : Centau
Sergei Shtylyov wrote:
> Hello.
>
> Marc St-Jean wrote:
>
> >> > Fourth attempt at the serial driver patch for the PMC-Sierra MSP71xx
> >>device.
>
> I think you need to submit your patch to Andrew Morton since it
> requires a patch from his tree.
OK, will do.
> >> > @@ -1383,6 +139
System Details:
dmesg: (parts)
Bootdata ok (command line is root=/dev/sda7 vga=0x31aresume=/dev/sda5
splash=silent)
Linux version 2.6.18.2-34-default ([EMAIL PROTECTED]) (gcc version 4.1.2
20061115 (prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006
...
Using ACPI (MADT) for SMP
"Martin A. Fink" <[EMAIL PROTECTED]> writes:
Your mailer seems to be broken. It drops cc.
>
> If you call fsync in BSD then you get what you expect. anything that is still
> not on disk will be written. Afterwards fsync returns... So this should be
> the same like with linux?!
Not necessarily.
Is not it too much fore a trivial two lines patch to a single file?
{pts/1}% stg import
~/patch/Re_2_6_20_rc6_libata_PATA_ATAPI_CDROM_is_not_working.patch
Importing
patch "Re_2_6_20_rc6_libata_PATA_ATAPI_CDROM_is_not_working.patch"... done
Now at patch "Re_2_6_20_rc6_libata_PATA_ATAPI_CDROM_is_n
> If you will have time for newbie, to explain in a few words, what is it need
> for (whole idea, or key detail), and, maybe, why it is generated so ...
> interestingly:
>
> asm-offsets.c -> *.s -> *.h
> (but this looks like interconnecting C and assembler, obviously)
>
> I will gla
> On Mon, 12 Feb 2007 13:35:10 +0300 Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> Andrew, do you consider kevent for inclusion or declining?
I haven't had time to think about it in the past month or two, sorry.
However we might as well get it back in there for review-and-test - please
send a new
Greg KH <[EMAIL PROTECTED]> writes:
> On Mon, Feb 12, 2007 at 03:30:22PM +0100, Rainer Weikusat wrote:
[...]
>> If you want to fix it only if you can claim to have written the code,
>> fine.
>
> I do not claim I have rewritten the code, if you look, you get full
> authorship credit for this fix,
On Mon, Feb 12, 2007 at 07:30:55AM +, Jan Beulich wrote:
>
> As the topic says - the goal is to support Xen. But yes, I was afraid someone
> would
> claim this make the code look ugly. And no, I currently don't have ideas to
> address
> any of your comments without breaking functionality on
>Yup. How does this patch look to you? We set error_code and trap_no
>for userspace faults and kernel faults which call die(). We don't set
>them for kernelspace faults which are fixed up.
That seems a reasonable approach.
Thanks, Jan
-
To unsubscribe from this list: send the line "unsubscribe
From: TAKADA Yoshihito <[EMAIL PROTECTED]>
Original code doesn't write back to CCR4 register. This patch reflects a
value of a register.
Cc: Jordan Crouse <[EMAIL PROTECTED]>
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED
From: Jeff Dike <[EMAIL PROTECTED]>
The 32-bit sysenter entry point mangles the sixth system call argument for
both 32-bit and 64-bit ptrace. In both cases, strace shows the frame
pointer (ebp) as the sixth argument.
Here's a snippet of a 64-bit strace of a 32-bit test program which
calls mmap
Not needed because fastcall is always default now
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/paravirt.c | 102 -
include/asm-i386/paravirt.h | 136 ++--
2 files changed, 119 insertions(+), 119 dele
From: Randy Dunlap <[EMAIL PROTECTED]>
setcc() in math-emu is written as a gcc extension statement expression
macro that returns a value. However, it's not used that way and it's not
needed like that, so just make it a do-while non-extension macro so that we
don't use an extension when it's not
From: "Bob Picco" <[EMAIL PROTECTED]>
Eliminate arch specific memory_present call x86_64 NUMA by utilizing
sparse_memory_present_with_active_regions.
Acked-by: Mel Gorman <[EMAIL PROTECTED]>
Signed-off-by: Bob Picco <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi Kleen
On 12/02/07, Vassili Karpov <[EMAIL PROTECTED]> wrote:
>
> How does the kernel calculates the value it places in `/proc/stat' at
> 4th position (i.e. "idle: twiddling thumbs")?
>
..
>
> Later small kernel module was developed that tried to time how much
> time is spent in the idle handler inside th
gcc 5.0 will likely not have the constraint problem
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
include/asm-x86_64/bitops.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/include/asm-x86_64/bitops.h
===
From: Andrew Morton <[EMAIL PROTECTED]>
That stupid non-inlined-static function in bugs.h causes:
include/asm/bugs.h:186: warning: 'check_bugs' defined but not used
But fortunately the include isn't needed.
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Sig
From: takada <[EMAIL PROTECTED]>
I hope to support "classic" MediaGXm in kernel.
The DIR1 register of MediaGXm( or Geode) shows the following values for
identify CPU. For example, My MediaGXm shows 0x42.
We can read National Semiconductor's datasheet without any NDAs.
http://www.national.com
From: Evgeniy Polyakov <[EMAIL PROTECTED]>
If DEBUG_SIG is enbaled in source code, ia32_signal.c compiles with warning
due to wrong format string. Attached patch fixes that. It is quite minor
update, since by default DEBUG_SIG is not enabled and can not be turned on
without code modification.
From: "Robert P. J. Day" <[EMAIL PROTECTED]>
Remove the unused kernel config option X86_XADD, which is unused in any
source or header file.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Andrew M
From: "Jan Beulich" <[EMAIL PROTECTED]>
Annotate i386/kernel/entry.S with END/ENDPROC to assist disassemblers and
other analysis tools.
Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[E
Hi!
> > > > "If the device requires that, implement .suspend and .resume or at least
> > >
> > > > define .suspend that will always return -ENOSYS (then people will know
> > > > they
> > > ^^^
For i386/x86-64.
Straight forward -- just reuse the Family 0xf code.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/nmi.c |6 --
arch/x86_64/kernel/nmi.c |2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
Index: linux/arch/i386/kernel/nmi.c
=
From: Chuck Ebbert <[EMAIL PROTECTED]>
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]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
Cc: Andi
Just various new acronyms. The new popcnt bit is in the middle
of Intel space. This looks a little weird, but I've been assured
it's ok.
Also I fixed RDTSCP for i386 which was at the wrong place.
For i386 and x86-64.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/cpu/proc.
From: Rusty Russell <[EMAIL PROTECTED]>
Allows external actors to disable mce.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
===
---
arch/i386/kernel/cpu/mcheck/mce.h |2 +-
incl
Trivial cleanup.
Only change is that it is always compiled in now on x86-64 like on i386.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/Makefile|1 +
arch/i386/kernel/pcspeaker.c | 20
arch/i386/kernel/setup.c | 26
From: Rusty Russell <[EMAIL PROTECTED]>
Extern declarations belong in headers. Times, they are a'changin.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
===
---
arch/i386/mm/disconti
From: Rusty Russell <[EMAIL PROTECTED]>
The current code simply calls "start_kernel" directly if we're under a
hypervisor and no paravirt_ops backend wants us, because paravirt.c
registers that as a backend.
This was always a vain hope; start_kernel won't get far without setup.
It's also impossib
From: Benjamin Romer <[EMAIL PROTECTED]>
On the Unisys ES7000/ONE system, we encountered a problem where performing
a kexec reboot or dump on any cell other than cell 0 causes the system
timer to stop working, resulting in a hang during timer calibration in the
new kernel.
We traced the problem
and in other strange binfmts. vDSO is not necessarily mapped there.
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/signal.c |6 +-
arch/x86_64/ia32/ia32_signal.c |7 ++-
fs/binfmt_elf.c|3 ++-
include/linux/binfmts.h|1 +
Fix bogus warning
linux/arch/i386/kernel/cpu/transmeta.c:12: warning: âcpu_freqâ may be used
uninitialized in this function
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/cpu/transmeta.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/i386/k
Hi!
> > > > > Neither am I. I'm just asking that new drivers have power management
> > > > > as
> > > > > standard.
> > >
> > > > What if the hardware doesn't support power management ?
> > >
> > > You would still want to do the cleanup and configuration that you'd do
> > > for module load/unload
Fix bogus gcc warning
linux/arch/i386/kernel/microcode.c:387: warning: ânew_mcâ may be used
uninitialized in this function
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/microcode.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/i386/kerne
From: Ralf Baechle <[EMAIL PROTECTED]>
On Sat, Feb 10, 2007 at 11:22:05AM +0100, Heiko Carstens wrote:
> Which remembers me that I think that MIPS is using the non-compat version
> of sys_epoll_pwait for compat syscalls. But maybe MIPS doesn't need a compat
> syscall for some reason. Dunno.
Whic
With that an L3 cache is correctly reported in the cache information in /sys
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/cpu/intel_cacheinfo.c | 65 +
1 file changed, 50 insertions(+), 15 deletions(-)
Index: linux/arch/i386/kernel/cpu/in
From: Rusty Russell <[EMAIL PROTECTED]>
When I implemented the DECLARE_PER_CPU(var) macros, I was careful that
people couldn't use "var" in a non-percpu context, by prepending
percpu__. I never considered that this would allow them to overload
the same name for a per-cpu and a non-percpu variable
From: Roland Dreier <[EMAIL PROTECTED]>
I've seen my box paralyzed by an endless spew of
rtc: lost some interrupts at 1024Hz.
messages on the serial console. What seems to be happening is that
something real causes an interrupt to be lost and triggers the
message. But then printing the me
On Mon, Feb 12, 2007 at 09:32:10AM +, Jan Beulich wrote:
> This breaks consumers of notify_die() relying on the proper trap number being
> passed, as the call to notify_die() from die() currently reads
> current->thread.trap_no.
Rats, good point.
> Also, you seem to leave other places where t
From: Adrian Bunk <[EMAIL PROTECTED]>
Every file should include the headers containing the prototypes for its
global functions.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/kernel/al
atomic_add_unless as inline. Remove system.h atomic.h circular dependency.
I agree (with Andi Kleen) this typeof is not needed and more error
prone. All the original atomic.h code that uses cmpxchg (which includes
the atomic_add_unless) uses defines instead of inline functions,
probably to circumv
On Mon, 12 Feb 2007 12:42:22 +0100 Milan Markovic wrote:
> I upgraded the kernel on my Kubuntu 6.10 to 2.6.17-11-generic and had
> a lot of trouble compiling my softmodem driver.
> Apparently it was, among others, because of a mistake in kernel-headers
> this is what I've found in tty.h
>
> $ cat
* Andi Kleen ([EMAIL PROTECTED]) wrote:
> Mathieu Desnoyers <[EMAIL PROTECTED]> writes:
> >
> > /**
> > @@ -402,7 +405,7 @@ static __inline__ long atomic64_sub_return(long i,
> > atomic64_t *v)
> > */
> > #define atomic_add_unless(v, a, u) \
> > ({
On Sun, 2007-02-11 at 16:46 -0600, Milton Miller wrote:
[cut]
>
> As far as I understand, you are providing access to a completely new
> hardware that is related to the PMU hardware by the fact that it
> collects a program counter. It doesn't use the PMU counters nor the
> PMU event selection.
Some more info:
:~> strace -c -T -o trace.out dd if=/dev/zero of=test.txt bs=10MB count=200
200+0 Datensätze ein
200+0 Datensätze aus
20 bytes (2,0 GB) copied, 52,8632 seconds, 37,8 MB/s
test.txt:
% time seconds usecs/call callserrors syscall
-- --- ---
On Mon, Feb 12, 2007 at 03:30:22PM +0100, Rainer Weikusat wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> > On Tue, Jan 30, 2007 at 06:40:10PM +0100, Rainer Weikusat wrote:
> >> Greg KH <[EMAIL PROTECTED]> writes:
> >>
> >> [...]
> >>
> >> > Rainer's problem is a real bug in the USB driver code, w
> > This is all scary and generally not needed spew but handy for debug.
> >
> > Looks like a PCMCIA layer bug. It should be respecting IRQ assignment
> > (not just allocation) by other resource configuration layers.
>
> Ah thanks for taking a look. I was slowly getting the impression from older
Hesse, Christian wrote:
On Saturday 10 February 2007 14:23, Hesse, Christian wrote:
On Friday 09 February 2007 22:12, James Ketrenos wrote:
We are pleased to announce the availability of a new driver for the
Intel PRO/Wireless 3945ABG Network Connection adapter.
Wow, great news
> Closed modules are allowed only because an exception was made
> in the licencing. That didn't have to happen at all. Closed modules
This statement is false. Sorry but the law and my legal advice recommend
that I jump in and repeat the correction every time people repeat this
myth. As one of th
>However
>this "kernel BUG" is something newly introduced in 2.6.20 which should
>be fixed in 2.6.20.1. Patch is below.
I am using raid6. Am I at risk after applying this patch?
Thanks for your time!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
Am Montag, 12. Februar 2007 18:04 schrieb Andi Kleen:
> "Martin A. Fink" <[EMAIL PROTECTED]> writes:
> >
> > What I did:
> > I wrote blocks of 1 MB size to file. Each 1 GB I made a fsync and took the
> > time. For those tests with filesystems I wrote files of 1 GB size,
otherwise
> > I just wro
On Mon, 12 Feb 2007, Sergei Organov wrote:
>
> Why strlen() should be allowed to be called with an incompatible pointer
> type? My point is that gcc should issue *different warning*, -- the same
> warning it issues here:
I agree that "strlen()" per se isn't different.
The issue is not that the
A Dilluns 12 Febrer 2007 10:11, Jean Delvare va escriure:
> Le Samedi 10 Février 2007 15:45, Tejun Heo a écrit :
> > [cc'ing Alan and Jean, Hi!]
> >
> > Leopold Palomo Avellaneda wrote:
> > > A Divendres 09 Febrer 2007 18:13, Leopold Palomo Avellaneda va escriure:
> > >> A Divendres 09 Febrer 2007
ris wrote:
Tejun Heo gmail.com> writes:
iowait != cpu busy. Your cpu idleness stays above 80%.
Ok .. but one of my CPU core are at 99% usage
htop report this
So how to solve this problem ?
The red part of cpu usage bar represents 'iowait' not cpu usage. Fire
up both top
"Martin A. Fink" <[EMAIL PROTECTED]> writes:
>
> What I did:
> I wrote blocks of 1 MB size to file. Each 1 GB I made a fsync and took the
> time. For those tests with filesystems I wrote files of 1 GB size, otherwise
> I just wrote to the raw device.
Newer Linux versions depending on the disk a
FWIW,
I've set up an unofficial git tree with these patches, and will try and
track changes as they're posted.
git://git.infradead.org/~jmorris/lguest-testing.git
Use the 'current' branch.
- James
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscr
On Mon, 12 Feb 2007, Pavel Machek wrote:
> > > "If the device requires that, implement .suspend and .resume or at least
> >
> > > define .suspend that will always return -ENOSYS (then people will know
> > > they
> > ^
>> +#include
>
> I did have a problem with this include. On s390 it didn't exist so I've
> just been running without it (with no problems). A quick 'find'
> suggests it only exists on x86_64, so I'd expect failures on all other
> arches.
confirmed on x86 also.
C.
-
To unsubscribe from this li
On Mon, Feb 12, 2007 at 02:52:01PM +1100, Rusty Russell wrote:
>
> +static void skb_to_dma(const struct sk_buff *skb, unsigned int len,
> +struct lguest_dma *dma)
> +{
> + unsigned int i, seg;
> +
> + for (i = seg = 0; i < len; seg++, i += rest_of_page(skb->data + i)) {
201 - 300 of 422 matches
Mail list logo
