> > Hi!
> >
> > > From: Miklos Szeredi <[EMAIL PROTECTED]>
> > >
> > > This patch adds support for finding out the current file position,
> > > open flags and possibly other info in the future.
> > >
> > > These new entries are added:
> > >
> > > /proc/PID/fdinfo/FD
> > >
On Tue, 27 Mar 2007 23:29:34 +0200
Eric Dumazet <[EMAIL PROTECTED]> wrote:
> Andrew Morton a écrit :
> >
> > The wheel spins around, slows then settles on
> > time-smp-friendly-alignment-of-struct-clocksource.patch!
> >
> > Presumably because the cacheline_aligned made
On Tue, 27 Mar 2007 21:24:20 +
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
>
> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >
> > This patch adds support for finding out the current file position,
> > open flags and possibly other info in the future.
> >
> > These new entries are added:
On Tue, 27 March 2007 21:24:20 +, Pavel Machek wrote:
> > From: Miklos Szeredi <[EMAIL PROTECTED]>
> >
> > This patch adds support for finding out the current file position,
> > open flags and possibly other info in the future.
> >
> > These new entries are added:
> >
> >
Hi!
> From: Heiko Carstens <[EMAIL PROTECTED]>
>
> Emit a warning if cpu capability changes e.g. because the cpus are
> overheating. The new cpu capability can be read via /proc/sysinfo.
>
> Signed-off-by: Martin Schwidefsky <[EMAIL PROTECTED]>
> Signed-off-by: Heiko Carstens <[EMAIL
On 3/27/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
Ok, so how to deal with these devices? Does anybody have some idea? That's
what I was talking about somewhere in the beginning of this thread, the raw
values, because it seems too specific for letting kernel to cope with each
of these devices
Andrew Morton a écrit :
The wheel spins around, slows then settles on
time-smp-friendly-alignment-of-struct-clocksource.patch!
Presumably because the cacheline_aligned made vsyscall_gtod_data_t get
too big. Or something.
Very strange, since here I have plenty of available room
Hi there,
the USB configuration selection code in drivers/usb/core/generic.c will
refuse to use an RNDIS-only device if the RNDIS driver is compiled as a
module. The straightforward solution would be to change the #ifndef test
to include CONFIG_USB_NET_RNDIS_HOST_MODULE as well, but I'd rather
On Monday 26 March 2007 09:52, Thomas Gleixner wrote:
> On Mon, 2007-03-26 at 12:31 +, Pavel Machek wrote:
> > > + lapic_timer_c2_ok [IA-32,APIC] trust the local apic timer in
> > > + C2 power state.
> > > +
> I still twist my brain how to autodetect that in a safe way,
On Tuesday 27 March 2007 23:26, Adrian Bunk wrote:
> On Mon, Mar 26, 2007 at 08:57:06PM -0800, Andrew Morton wrote:
> >...
> > Changes since 2.6.21-rc4-mm1:
> >...
> > +move-die-notifier-handling-to-common-code.patch
> >...
> > Misc
> >...
>
> Is the removal of the vmalloc_sync_all() call in
Hi!
> From: Miklos Szeredi <[EMAIL PROTECTED]>
>
> This patch adds support for finding out the current file position,
> open flags and possibly other info in the future.
>
> These new entries are added:
>
> /proc/PID/fdinfo/FD
> /proc/PID/task/TID/fdinfo/FD
>
> For each fd the information
On Mon, Mar 26, 2007 at 08:57:06PM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc4-mm1:
>...
> +move-die-notifier-handling-to-common-code.patch
>...
> Misc
>...
Is the removal of the vmalloc_sync_all() call in register_die_notifier()
on i386 and x86_64 both intentional and correct?
>
> - You may see this:
>
> init/missing_syscalls.c:5:27: error: linux/compile.h: No such file or
> directory
>
> during compilation. It's probably a parallel-build bug in Sam's tree.
> Just type make again.
I ended up redoing the check-for-missing-sys-calls patch and backed out the
The following patch adds some extra clarification to the CONFIG_DEBUG_INFO
Kconfig help text. The current text is mostly a recursive definition and
doesn't really say much of anything. When I first read this I thought it
was going to enable extra verbosity in debug messages or something, but it
"Williams, Mitch A" <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>>
>>> Because enabling and disabling the MSI interrupt is done through
>>> config space, and config space writes are not posted. So we won't
>>> see the problem that we do with MSI-X.
>>
>>Normally this is true.
On Tue, 2007-03-27 at 13:12 -0700, Andrew Morton wrote:
> On Tue, 27 Mar 2007 09:57:50 -0800
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2007-03-27 at 08:48 -0800, Andrew Morton wrote:
> > > On Tue, 27 Mar 2007 09:39:33 -0800 Badari Pulavarty <[EMAIL PROTECTED]>
> > > wrote:
> >
On 03/27, Venki Pallipadi wrote:
>
> for (;;) {
> - base = timer->base;
> + tvec_base_t *prelock_base = timer->base;
> + base = timer_get_base(timer);
> if (likely(base != NULL)) {
> spin_lock_irqsave(>lock, *flags);
> -
Jiri Kosina schrieb:
> On Sun, 18 Mar 2007, Thomas Meyer wrote:
>
>
>> Appletouch is bound to the device:
>>
>
> OK, so the quirk actually works fine ...
>
Yes, it works fine, but...
>
>> But the X server touchpad driver doesn't work anymore, that means i
>> can't emulte a right
Marcus Better <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>
>> >> Patch : http://lkml.org/lkml/2007/3/24/136
>
>> Marcus any chance I could see an oops?
>
> I didn't see anything, it froze with the yellow "Linux!" sign. Any idea how
> to
> get a oops?
>
>> Or you could try the
johann deneux napsal(a):
> On 3/27/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
>> johann deneux napsal(a):
>> > Are we
>> > misunderstanding eachother maybe? By "vector" I mean a triplet of
>> > numbers, when you say "torques" and "forces vector", do you mean that
>> > each effect is composed of a
Add IRQF_IRQPOLL to the timer interrupt on parisc.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/parisc/kernel/irq.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.21-rc5-mm2/arch/parisc/kernel/irq.c
Add IRQF_IRQPOLL on each timer interrupt on SH2.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/sh/kernel/timers/timer-cmt.c |2 +-
arch/sh/kernel/timers/timer-mtu2.c |2 +-
arch/sh/kernel/timers/timer-tmu.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
This patch adds a IRQF_IRQPOLL flag that the interrupt registration code
could use for the interrupt it wants to use for IRQ polling.
Because this must not be the timer interrupt, an additional flag was added
instead of re-using the IRQF_TIMER constant. Until all architectures will have
an
Add IRQF_IRQPOLL for the timer interrupt on x86_64.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/time.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
Index: linux-2.6.21-rc5-mm2/arch/x86_64/kernel/time.c
On 27 Mar 2007 16:09:33 -0400
[EMAIL PROTECTED] wrote:
> What part of "The msync() function writes all modified data to
> permanent storage locations [...] For mappings to files, the msync()
> function ensures that all write operations are completed as defined
> for synchronised I/O data
Add IRQF_IRQPOLL for the timer interrupt on IA64.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/ia64/kernel/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.21-rc5-mm2/arch/ia64/kernel/time.c
irqpoll is broken on some architectures that don't use the IRQ 0 for the timer
interrupt like IA64. This patch adds a IRQF_IRQPOLL flag.
Each architecture is handled in a separate pach. As I left the irq == 0 as
condition, this should not break existing architectures that use timer_irq == 0
and
Add IRQF_IRQPOLL to timer interrupts on i386.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
Cc: Andi Kleen <[EMAIL PROTECTED]>
---
arch/i386/mach-default/setup.c |2 +-
arch/i386/mach-visws/setup.c |2 +-
arch/i386/mach-voyager/setup.c |7 ++-
3 files changed, 8
Add IRQF_IRQPOLL for each timer interrupt.
Signed-off-by: Bernhard Walle <[EMAIL PROTECTED]>
---
arch/arm/mach-aaec2000/core.c|2 +-
arch/arm/mach-at91/at91rm9200_time.c |2 +-
arch/arm/mach-at91/at91sam926x_time.c|2 +-
arch/arm/mach-clps711x/time.c|
On Thu, Mar 22, 2007 at 07:13:55PM +0300, Oleg Nesterov wrote:
>
> Perhaps we can do something like this,
>
> struct deferrable_timer {
> struct timer_list timer;
> void (*real_function)(struct deferrable_timer *self);
> };
>
> static void
On 3/27/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
johann deneux napsal(a):
> On 3/27/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
>> Dmitry Torokhov napsal(a):
>> > On Wednesday 21 March 2007 18:03, johann deneux wrote:
>> >> I have forgotten the details of ioctl: Wouldn't the
>> >> following work?
On 3/27/07, John <[EMAIL PROTECTED]> wrote:
I'm runnning 2.6.20.3 patched with -rt8 (and glibc 2.3.6).
http://people.redhat.com/mingo/realtime-preempt/older/patch-2.6.20-rt8
I've written a program to highlight a phenomenon I don't understand.
This system includes a PCI board that provides data
Andrew Morton a écrit :
On Tue, 27 Mar 2007 09:57:50 -0800
Badari Pulavarty <[EMAIL PROTECTED]> wrote:
On Tue, 2007-03-27 at 08:48 -0800, Andrew Morton wrote:
On Tue, 27 Mar 2007 09:39:33 -0800 Badari Pulavarty <[EMAIL PROTECTED]> wrote:
On Mon, 2007-03-26 at 20:57 -0800, Andrew Morton
On Tue, Mar 27, 2007 at 11:40:48AM -0700, Phy Prabab wrote:
> Hello,
>
> I am currently running 2.6.21-rc5 and I am seeing quite a bit of this
> message in my log files:
> kernel: rpcsvc: received unknown control message:-2144992132/-1
>
> This machine is an dual dual core opteron with 3Ware
Hello once again!
Here is a little bit more information on my issue with slowlaris and
knfs 2.6.21-rc4/5 (actually appears in 2.4.20.x). Running this from
the client (x.org source code):
ls -l xc/lib/Xmu/Xct.h
-rw-rw-r-- 1 phy bdf 0 2006-01-09 06:59 xc/lib/Xmu/Xct.h
file xc/lib/Xmu/Xct.h
> > Suggest you use msync(MS_ASYNC), then
> > sync_file_range(SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE).
>
> Thank you; I didn't know about that. And I can handle -ENOSYS by falling
> back to the old behavior.
>
> > We can fix your application, and we'll break someone else's.
>
> If
On Tue, 27 Mar 2007 09:54:07 -0800
Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-03-26 at 20:57 -0800, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc5/2.6.21-rc5-mm1/
> >
> >
>
> CC [M] drivers/parport/parport_pc.o
> In file
On Tue, 27 Mar 2007 09:57:50 -0800
Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-03-27 at 08:48 -0800, Andrew Morton wrote:
> > On Tue, 27 Mar 2007 09:39:33 -0800 Badari Pulavarty <[EMAIL PROTECTED]>
> > wrote:
> >
> > > On Mon, 2007-03-26 at 20:57 -0800, Andrew Morton wrote:
> > >
On Mar 26, 2007, at 7:52 PM, Marcelo Tosatti wrote:
Shall this driver be removed?
May as well. I'm probably the only one in the
world with the hardware. If I need a driver I'll
just write another one :-)
Thanks.
-- Dan
-
To unsubscribe from this list: send the line "unsubscribe
Ignatich wrote:
Subject:
reiser4 bugs in 2.6.21-rc4
From:
Ignatich <[EMAIL PROTECTED]>
Date:
Tue, 27 Mar 2007 23:29:18 +0400
To:
linux-kernel@vger.kernel.org
To:
linux-kernel@vger.kernel.org
Message-ID:
<[EMAIL
johann deneux napsal(a):
> On 3/27/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
>> Dmitry Torokhov napsal(a):
>> > On Wednesday 21 March 2007 18:03, johann deneux wrote:
>> >> I have forgotten the details of ioctl: Wouldn't the
>> >> following work?
>>
>> No, at least, as far as I understand this. I
> Suggest you use msync(MS_ASYNC), then
> sync_file_range(SYNC_FILE_RANGE_WAIT_BEFORE|SYNC_FILE_RANGE_WRITE).
Thank you; I didn't know about that. And I can handle -ENOSYS by falling
back to the old behavior.
> We can fix your application, and we'll break someone else's.
If you can point to an
Signed-off-by: Deepak Saxena <[EMAIL PROTECTED]>
Index: linux-2.6.21-rc5/arch/arm/Kconfig
===
--- linux-2.6.21-rc5.orig/arch/arm/Kconfig
+++ linux-2.6.21-rc5/arch/arm/Kconfig
@@ -33,10 +33,6 @@ config GENERIC_CLOCKEVENTS
bool
Great, thanks ... I'm not sure which of the 2 patches fixed things,
but I now got the following trace. I've not really analyzed this, but
it definitely looks like tun_init() is doing something
fishy... ("149776 us maximum-latency"!!)
- R.
[ 272.392694] tun: Universal TUN/TAP device driver,
On Tue, 2007-03-27 at 21:15 +0200, Andreas Mohr wrote:
> Maybe fix up all the other myriads of sysctl entries which use a rather
> non-precise generic sizeof(int) as well?
> Or doesn't that make sense?
No, it does make sense
> Maybe this is because it's security relevant and you'd better make
On 27 Mar 2007 15:24:52 -0400
[EMAIL PROTECTED] wrote:
> > * MS_ASYNC does not start I/O (it used to, up to 2.5.67).
>
> Yes, I noticed. See
> http://www.ussg.iu.edu/hypermail/linux/kernel/0602.1/0450.html
> for a bug report on the subject February 2006.
Suggest you use msync(MS_ASYNC), then
Hello,
[ ... Fixed two minor typos. ...]
The following patch (it's also attached tho) is against 2.6.21-rc5 :
--- linux-2.6.20-o/drivers/block/Kconfig2007-03-18 00:04:53.0
+0100
+++ linux-2.6.20/drivers/block/Kconfig 2007-03-25 03:35:19.0 +0200
@@ -383,7 +383,7 @@
There are two bugs I found in current -mm reiser4 code.
1. Some files seem to be zeroed out randomly. Usually it's
/lib/security/pam_limits.so and /lib/security/pam_deny.so. As
fsck.reiser4 didn't find anything wrong I decided to create clean
installation in vmware and see if this bug appears
> * MS_ASYNC does not start I/O (it used to, up to 2.5.67).
Yes, I noticed. See
http://www.ussg.iu.edu/hypermail/linux/kernel/0602.1/0450.html
for a bug report on the subject February 2006.
That's why this application is still running on 2.4.
As I mentioned at the time, the SUS says:
On Mon, 2007-03-26 at 13:36 +0800, Shaohua Li wrote:
> Hi,
> On Sat, 2007-03-24 at 03:47 -0400, Adam Belay wrote:
> > This patch adds the 'menu' governor, as was described in my first email.
> >
>
> > +/**
> > + * menu_select - selects the next idle state to enter
> > + * @dev: the CPU
> > + */
* Roland Dreier <[EMAIL PROTECTED]> wrote:
> > I finally got curious enough to want to debug why starting kvm with
> > tun/tap networking produces a bunch of
> >
> > rtc: lost some interrupts at 1024Hz.
> >
> > messages. So I'm assuming it's a ~millisecond irqs-off section
> >
* Roland Dreier <[EMAIL PROTECTED]> wrote:
> Any suggestion of where to look? My /proc/latency_trace stays
> stubbornly empty -- are there any sysctls I need to change from their
> default to get latency tracing? I'm a complete noob when it comes to
> the -rt patch, so I'm not sure what the
I am getting a BUG report on the following SuSE 10.2 system:
$ uname -a
Linux ascbackup 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006
i686 i686 i386 GNU/Linux
The only clear effect I'm seeing is that the system beeps and dumps the
following message in /var/log/messages every 5 to 15
Hi,
On Tue, Mar 27, 2007 at 01:19:07PM -0400, Steven Rostedt wrote:
> Ingo,
>
> I wasn't able to turn on latency tracing on a x86_64 box. Using logdev
> to see what was happening, I found that echoing 0
> into /proc/sys/kernel/preempt_max_latency would only change the max from
> -1ULL to
* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> Ingo,
>
> I wasn't able to turn on latency tracing on a x86_64 box. Using logdev
> to see what was happening, I found that echoing 0 into
> /proc/sys/kernel/preempt_max_latency would only change the max from
> -1ULL to 0x. Which
* Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
> Hi Ingo and all,
>
> When I was executing massive interactive processes, I found that some
> of them occupy CPU time and the others hardly run.
yeah.
> I also attach the test program which easily recreates this problem.
thanks, this is really
Oliver Joa wrote:
I also often get a sata-bus-reset with the kernels 2.6.19.2
and 2.6.20.2.
What can I do to find the problem? I think about to change
from xfs to ext2 but the filesystemcheck every 30 mounts lasts
a long time.
Do you have any Idea?
In this whole message I can only help on
Mike Frysinger <[EMAIL PROTECTED]> wrote:
> > That sounds reasonable. However, I suspect that most NOMMU CPUs won't be
> > able to do that. In effect you're creating a third option, I think (MMU,
> > NOMMU, MPU).
>
> sure, but i'm not sure the MPU option would be mutually exclusive with
>
On Tue, 27 Mar 2007 20:55:51 +0200
Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> It's actually wrong about FADV_DONTNEED, which I think doesn't start
> writeout either.
case POSIX_FADV_DONTNEED:
if (!bdi_write_congested(mapping->backing_dev_info))
> > I agree that msync(MS_ASYNC) has no semantics if time is ignored.
> > But it's a useful way to tell the OS that the page is not going
> > to be dirtied again.
>
> Just to clarify, here's the header comment for sys_msync():
>
> /*
> * MS_SYNC syncs the entire file - including mappings.
> *
> > Yes, this will make msync(MS_ASYNC) more heavyweight again. But if an
> > application doesn't want to update the timestamps, it should just omit
> > this call, since it does nothing else.
>
> Er... FWIW, I have an application that makes heavy use of msync(MS_ASYNC)
> and doesn't care about
Linus Torvalds napisał(a):
> There's various fixes here, ranging from some architecture updates (ia64,
> ARM, MIPS, SH, Sparc64) to KVM, networking and network drivers.
>
> And random one-liners.
>
I found this in mm snapshot
http://www.ussg.iu.edu/hypermail/linux/kernel/0703.2/1367.html
it's
On Tue, Mar 27, 2007 at 11:27:14AM -0700, Ethan Solomita wrote:
> Hi Maneesh -- I will start testing with the patch you provided. If
> you come up with any further issues please let me know. Also, if you
> could
> suggest some additional BUG() lines that I could insert I would
>
Linus Torvalds wrote:
On Tue, 27 Mar 2007, Jeff Garzik wrote:
FWIW, I'm still leaning towards disabling libata ACPI support by default for
2.6.21.
Hey, I'm not going to argue against anything that says "disable ACPI". Of
*course* it should be disabled if there aren't thousands of machines
Hello,
I am currently running 2.6.21-rc5 and I am seeing quite a bit of this
message in my log files:
kernel: rpcsvc: received unknown control message:-2144992132/-1
This machine is an dual dual core opteron with 3Ware 9650 (14 disk
RAID10), 4G RAM, 64bit kernel, nfsutils-1.0.12 running knfsd.
> Yes, this will make msync(MS_ASYNC) more heavyweight again. But if an
> application doesn't want to update the timestamps, it should just omit
> this call, since it does nothing else.
Er... FWIW, I have an application that makes heavy use of msync(MS_ASYNC)
and doesn't care about timestamps.
Mark Rustad wrote:
reorder any queued operations. Of course if you really care about your
data, you don't really want to turn write cache on.
That's a gross exaggeration. FLUSH CACHE and FUA both ensure data
integrity as well.
Turning write cache off has always been a performance-killing
Hi,
On 26/03/07, Linus Torvalds <[EMAIL PROTECTED]> wrote:
There's various fixes here, ranging from some architecture updates (ia64,
ARM, MIPS, SH, Sparc64) to KVM, networking and network drivers.
Suspend to disk doesn't work for me with this patch. It hangs after
PM: Preparing devices for
On 3/27/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
Dmitry Torokhov napsal(a):
> On Wednesday 21 March 2007 18:03, johann deneux wrote:
>> On 3/21/07, Jiri Slaby <[EMAIL PROTECTED]> wrote:
>>> Dmitry Torokhov napsal(a):
On 3/21/07, johann deneux <[EMAIL PROTECTED]> wrote:
> I would
I started getting warnings from atomic.h about cmpxchg not having a
prototype. It's declared in system.h, so including that fixes the UML
build warnings and has no noticable ill effects on the i386 build.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
include/asm-i386/atomic.h |1 +
1 file
These are all 2.6.22 material. Patch 1 fixes what appears to be a
i386 compilation bug, so we'll want Andi's ack on that, probably.
Jeff
--
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
From: Jason Lunz <[EMAIL PROTECTED]>
Permit lvm to create logical volumes without crashing UML.
When device-mapper's DM_DEV_CREATE_CMD ioctl is called to create a new
device, dev_create()->dm_create()->alloc_dev()->
blk_queue_bounce_limit(md->queue, BLK_BOUNCE_ANY) is called.
From: Miklos Szeredi <[EMAIL PROTECTED]>
_PAGE_PROTNONE conflicts with the lowest bit of pgoff. This causes
all sorts of weirdness when nonlinear mappings are used.
Took me a good half day to track this down.
Signed-off-by: Miklos Szeredi <[EMAIL PROTECTED]>
Signed-off-by: Jeff Dike <[EMAIL
Fix a few miscellaneous compilation problems -
an assignment with mismatched types in ldt.c
a missing include in mconsole.h which needs a definition of uml_pt_regs
when auditing is configured there are some mismatched types in ptrace.c
I missed removing an include
Fix a NULL dereference when unplugging a device. The default value of
err_msg wants to be "" in case the driver doesn't modify it.
Signed-off-by: Jeff Dike <[EMAIL PROTECTED]>
--
arch/um/drivers/mconsole_kern.c |3 +++
1 file changed, 3 insertions(+)
Index:
As the comment immediately preceding this points out, this list is
changed in irq context, so it needs to be protected with
spin_lock_irqsave in process context when it is processed.
Sometimes, gcc should just compile the comments and forget the code.
The IRQ side of this was better, in the
> that's simpler ;) Is it correct enough though? The place where it will
> become inaccurate is for repeated modification via an established map. ie:
>
> p = mmap(..., MAP_SHARED);
> for ( ; ; )
> *p = 1;
>
> in which case I think the timestamp will only get updated
Minor point: the chip part numbers are actually IT887x, not ITE887x.
I STFW for a data sheet, but didn't have immediate luck. Does anyone know
where to find
documentation?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Hi Maneesh -- I will start testing with the patch you provided. If you
come up with any further issues please let me know. Also, if you could
suggest some additional BUG() lines that I could insert I would
appreciate it. Since the bug is hard to reproduce, it may be easier to
catch a race
[Pete Zaitcev - Tue, Mar 27, 2007 at 10:51:16AM -0700]
| On Tue, 27 Mar 2007 19:14:05 +0400, Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
|
| > --- a/drivers/usb/misc/ftdi-elan.c
| > @@ -2903,7 +2903,7 @@ static struct usb_driver ftdi_elan_driver = {
| > };
| > static int __init
On Mar 27, 2007, at 12:59 AM, Jeff Garzik wrote:
Justin Piszcz wrote:
Without NCQ, performance is MUCH better on almost every operation,
with the exception of 2-3 items.
Variables to take into account:
* the drive (NCQ performance wildly varies)
* the IO scheduler
* the filesystem (if not
On Sun, Mar 25, 2007 at 02:36:09PM -0800, Andrew Morton wrote:
> On Sun, 25 Mar 2007 23:02:21 +0400 Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> > Some drivers do register_chrdev() before lock or semaphore used in
> > corresponding file_operations is initialized.
> > --- a/drivers/char/tb0219.c
>
On Tue, 27 Mar 2007 13:15:14 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]> wrote:
> > Suspend to disk still causes "virtual replugging" and I think that
> > controller is reset and will unplug/replug devices anyway
> > Resolving this problem is very difficult. Maybe it possible to check on
> >
On 27 Mar 2007 17:01:01 +0200, Andi Kleen <[EMAIL PROTECTED]> wrote:
What is the problem? You have cache misses on the the hash table
or are the instructions really an issue on a modern CPU?
It was page_to_pfn() on numa system. I think it's cache misses on per
node pgdat lookup with node
On Tuesday 27 March 2007 19:15:14 Alan Stern wrote:
> On Tue, 27 Mar 2007, Maxim Levitsky wrote:
>
> > Hi,
> > I noticed that after suspend/resume cycle all my usb devices are
> > unplugged/replugged by uhci driver.
> > While it is not that big problem to me, that can be a real problem if a
Jesse Huang wrote:
Dear all:
Would someone tell me the current status of IP1000A Linux Driver?
Would it be putted into Linux Kernel or not?
I forgot what the status of this was? Didn't it need some cleanups?
Maybe Francois has a better memory than me.
Jeff
-
To unsubscribe from
On Tue, 27 Mar 2007 19:14:05 +0400, Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
> --- a/drivers/usb/misc/ftdi-elan.c
> @@ -2903,7 +2903,7 @@ static struct usb_driver ftdi_elan_driver = {
> };
> static int __init ftdi_elan_init(void)
> {
> -int result;
> +int result = 0;
Why do
On Tue, 27 Mar 2007 11:23:06 +0200 Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> > > > > But Peter Staubach says a RH custumer has files written thorugh mmap,
> > > > > which are not being backed up.
> > > >
> > > > Yes, I expect the backup problem is the major real-world hurt arising
> > > >
On 3/26/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
LTP's vmsplice01 triggers the below:
Unable to handle kernel NULL pointer dereference at 0130 RIP:
[] pipe_to_file+0x1f3/0x2a6
Ouch, generic_pipe_buf_map() and unmap is used by both pipe and
splice, I better constrain all
[Luiz Fernando N. Capitulino - Tue, Mar 27, 2007 at 02:29:04PM -0300]
| Em Tue, 27 Mar 2007 21:01:25 +0400
| Cyrill Gorcunov <[EMAIL PROTECTED]> escreveu:
|
| | [Luiz Fernando N. Capitulino - Tue, Mar 27, 2007 at 01:28:39PM -0300]
| | | Em Tue, 27 Mar 2007 19:14:05 +0400
| | | Cyrill Gorcunov
Tom Horsley <[EMAIL PROTECTED]> writes:
>
> Should core files have NOTE entries added for some sort of
> thread local storage info to be recorded? (Whatever the
> kernel happens to know that won't be accessible anymore
> after the process is gone, which would probably vary
> from architecture to
Jeremy Fitzhardinge wrote:
diff -r 4c81d8cafb67 drivers/char/sysrq.c
--- a/drivers/char/sysrq.c Tue Mar 27 01:16:07 2007 -0700
+++ b/drivers/char/sysrq.c Tue Mar 27 01:18:05 2007 -0700
@@ -408,6 +408,8 @@ void __handle_sysrq(int key, struct tty_
int i;
unsigned long
On Thu, 2007-03-22 at 23:19 +, Pavel Machek wrote:
> > There are some papers and related userspace code at
> >http://www.research.ibm.com/gsal/tcpa
> > which describe the architecture in more detail, but basically this
> > integrity provider is designed to complement mandatory access
Em Tue, 27 Mar 2007 21:01:25 +0400
Cyrill Gorcunov <[EMAIL PROTECTED]> escreveu:
| [Luiz Fernando N. Capitulino - Tue, Mar 27, 2007 at 01:28:39PM -0300]
| | Em Tue, 27 Mar 2007 19:14:05 +0400
| | Cyrill Gorcunov <[EMAIL PROTECTED]> escreveu:
| |
| | | Pete, Luiz
| | |
| | | what about this one?
On Tue, Mar 27, 2007 at 01:11:50PM -0400, Mathieu Desnoyers wrote:
> Hi Adrian,
>
> Since kdebug.h seems to have moved from asm/ to linux/ in Andrew's tree, I
> guess the #include should be removed ? linux/kdebug.h
> already includes asm/kdebug.h.
Yes, exactly.
-
To unsubscribe from this list:
Jeremy Fitzhardinge wrote:
Prarit Bhargava wrote:
Jeremy Fitzhardinge wrote:
Prarit Bhargava wrote:
I'd like to see this patch implement/fix touch_cpu_softlockup_watchdog
and touch_softlockup_watchdog to mimic touch_nmi_watchdog's behaviour.
Prarit Bhargava wrote:
> Jeremy Fitzhardinge wrote:
>
>> Prarit Bhargava wrote:
>>
>>
>>> I'd like to see this patch implement/fix touch_cpu_softlockup_watchdog
>>> and touch_softlockup_watchdog to mimic touch_nmi_watchdog's behaviour.
>>>
>>>
>> Why? Is that more correct?
Ingo,
I wasn't able to turn on latency tracing on a x86_64 box. Using logdev
to see what was happening, I found that echoing 0
into /proc/sys/kernel/preempt_max_latency would only change the max from
-1ULL to 0x. Which would keep the max pretty high still.
The problem is in
Eric W. Biederman wrote:
>
>> Because enabling and disabling the MSI interrupt is done through
>> config space, and config space writes are not posted. So we won't
>> see the problem that we do with MSI-X.
>
>Normally this is true. However when we have memory mapped pci config
>space the
On Tue, 27 Mar 2007 11:25:57 +0200,
"Kay Sievers" <[EMAIL PROTECTED]> wrote:
> I don't see any point in deregistering a kernel device, if the event
> to userspace goes wrong, or a subsytem returns a non-zero value in the
> filter.
But if we filter the event, we just return 0?
> Checking the
101 - 200 of 676 matches
Mail list logo
