[Bodo Eggert - Sun, Mar 11, 2007 at 06:21:59AM +0100]
| Sam Ravnborg <[EMAIL PROTECTED]> wrote:
| > On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
| >> On Mar 10 2007 22:27, Sam Ravnborg wrote:
| >> >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
|
| >> >>
On Sunday 11 March 2007 03:09, Christoph Lameter wrote:
> x86_64: Convert to use a single quicklists
>
> This adds caching of pgds and puds, pmds, pte. That way we can
> avoid costly zeroing and initialization of special mappings in the
> pgd.
>
> The first patch just adds a simple
On Sat, Mar 10, 2007 at 02:06:28PM +, Simon Arlott wrote:
> On 10/03/07 13:38, Andi Kleen wrote:
> >Simon Arlott <[EMAIL PROTECTED]> writes:
> >
> >>On 09/03/07 20:42, Francois Romieu wrote:
> >>>Simon Arlott <[EMAIL PROTECTED]> :
> When I unplug the cable the system just stops responding
[Sam Ravnborg - Sat, Mar 10, 2007 at 11:45:34PM +0100]
| On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
| >
| > On Mar 10 2007 22:27, Sam Ravnborg wrote:
| > >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
| > >>
| > >> Whether the 'working config file path'
On Sat, Mar 10, 2007 at 07:35:06PM -0600, Matt Mackall wrote:
> I've tested -mm2 against -mm2+noyield and -mm2+rsdl+noyield. The
> noyield patch simply makes the sched_yield syscall return immediately.
> Xorg and all tests are run at nice 0.
[skipped long and precise test report]
> Also note I
> On Sat, 10 Mar 2007 17:27:44 -0500 (EST) "Robert P. J. Day" <[EMAIL
> PROTECTED]> wrote:
>
> Delete apparently unused header file
> sound/pci/cs46xx/imgs/cwcemb80.h.
>
That patch series was rather a mess
- Multiple patches with the same Subject: (I might have lost some as a result)
-
Good Day
Say i want to implement extended set of ATA commands available to
userspace for building diagnostic tools.
I need 0x40 -- read verify and 0x32 -- write long with error handling,
for example. I was trying ide driver through ioctl's, but seems it
lack of functionality and full of gotchas.
On Sat, 10 Mar 2007, Andrew Morton wrote:
> Is this safe to think about applying yet?
Its safe. By default kernels will be build with SLAB. SLUB becomes only a
selectable alternative. It should not become the primary slab until we
know that its really superior overall and have thoroughly
Is this safe to think about applying yet?
We lost the leak detector feature.
It might be nice to create synonyms for PageActive, PageReferenced and
PageError, to make things clearer in the slub core. At the expense of
making things less clear globally. Am unsure.
-
To unsubscribe from this
On Sunday 11 March 2007 15:03, Matt Mackall wrote:
> On Sat, Mar 10, 2007 at 10:01:32PM -0600, Matt Mackall wrote:
> > On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
> > > Ok I don't think there's any actual accounting problem here per se
> > > (although I did just recently post a
On Sat, 2007-03-10 at 21:31 -0800, Linus Torvalds wrote:
>
> On Sat, 10 Mar 2007, Nicholas Miell wrote:
> >
> > Ah, I see. You're just interested in fds as a generic handle concept,
> > and not a more Plan 9 type thing.
>
> Indeed. It's a "handle".
>
> UNIX has pid's for "process" handles, and
On Sat, 10 Mar 2007, Linus Torvalds wrote:
> > Actually, the only place where I can find the itimerspec usefull, is
> > indeed with TFD_TIMER_SEQ. In cases where you want you clock starting at a
> > given time (it_value) *and* with the given frequency (it_interval).
>
> .. and this is where
On Sat, 10 Mar 2007, Davide Libenzi wrote:
> On Sat, 10 Mar 2007, Linus Torvalds wrote:
>
> > (That said, using "struct itimerspec" might be a good idea. That would
> > also obviate the need for TFD_TIMER_SEQ, since an itimerspec automatically
> > has both "base" and "incremental" parts).
>
On Sat, 10 Mar 2007, Nicholas Miell wrote:
>
> Ah, I see. You're just interested in fds as a generic handle concept,
> and not a more Plan 9 type thing.
Indeed. It's a "handle".
UNIX has pid's for "process" handles, and "file descriptors" for just
about everything else.
> If that's the
Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
>> On Mar 10 2007 22:27, Sam Ravnborg wrote:
>> >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
>> >> Whether the 'working config file path' should change when you do
>> >>
Hello, again,
I just saw that my 0.28 patch file was wrongly named 0.26 and that there is a
new version 0.29 of RSDL that just came out... so here is the backported RSDL
0.29 to a 2.6.18.8 kernel.
This does compile but I did not got the time to fully test it yet.
>
> Here is an update for
Hi all,
>
> Here is an update for RSDL to version 0.28
>
> Full patch:
> http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched-
> rsdl-0.28.patch
>
> Series:
> http://ck.kolivas.org/patches/staircase-deadline/2.6.20/
>
> The patch to get you from 0.26 to 0.28:
>
On Saturday 10 March 2007 5:13 am, Haavard Skinnemoen wrote:
> This is a very simple bitbanging i2c bus driver utilizing the new
> arch-neutral GPIO API. ...
> ---
> This patch is different from the first patch in the following ways:
> * Handles pins set up as open drain (aka multidrive) by
On Saturday 10 March 2007 12:15 pm, Jean Delvare wrote:
> Hi Haavard,
>
> On Sat, 10 Mar 2007 14:13:28 +0100, Haavard Skinnemoen wrote:
> > This is a very simple bitbanging i2c bus driver utilizing the new
> > arch-neutral GPIO API. Useful for chips that don't have a built-in
> > i2c controller,
On Fri, 2007-03-09 at 21:41 -0800, Linus Torvalds wrote:
>
> On Sat, 10 Mar 2007, Sergio Monteiro Basto wrote:
> >
> > With this quirk I got this oops on hibernate (but computer still
> > working)
>
> Well, strictly speaking it's a warning, not an oops per se.
>
> What happens is that the
On Sat, Mar 10, 2007 at 10:01:32PM -0600, Matt Mackall wrote:
> On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
> > Ok I don't think there's any actual accounting problem here per se
> > (although I did just recently post a bugfix for rsdl however I think
> > that's unrelated). What I
On Sun, Mar 11, 2007 at 01:28:22PM +1100, Con Kolivas wrote:
> >make -j 5 ccache
> > berylok good awful
> > galeon goodgood bad
> > mp3 goodgood bad
> > terminal goodgood bad/ok
> > mousegoodgood
From: Con Kolivas <[EMAIL PROTECTED]>
Add comprehensive documentation of the RSDL cpu scheduler design.
Signed-off-by: Con Kolivas <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Nick Piggin <[EMAIL PROTECTED]>
Cc: "Siddha, Suresh B" <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton
From: Con Kolivas <[EMAIL PROTECTED]>
Remove the TASK_NONINTERACTIVE flag as it will no longer be used.
Signed-off-by: Con Kolivas <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Nick Piggin <[EMAIL PROTECTED]>
Cc: "Siddha, Suresh B" <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton
From: Con Kolivas <[EMAIL PROTECTED]>
Modify the sched_find_first_bit function to work on a 180bit long bitmap.
Signed-off-by: Con Kolivas <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Nick Piggin <[EMAIL PROTECTED]>
Cc: "Siddha, Suresh B" <[EMAIL PROTECTED]>
Signed-off-by: Andrew
The practice of renicing kernel threads to negative nice values is of
questionable benefit at best, and at worst leads to larger latencies when
kernel threads are busy on behalf of other tasks.
Signed-off-by: Con Kolivas <[EMAIL PROTECTED]>
---
kernel/workqueue.c |1 -
1 file changed, 1
From: Con Kolivas <[EMAIL PROTECTED]>
Add a list_splice_tail variant of list_splice.
Patch-by: Peter Zijlstra <[EMAIL PROTECTED]>
Signed-off-by: Con Kolivas <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Nick Piggin <[EMAIL PROTECTED]>
Cc: "Siddha, Suresh B" <[EMAIL PROTECTED]>
From: Con Kolivas <[EMAIL PROTECTED]>
Remove the sleep_avg field from proc output as it will be removed from the
task_struct.
Signed-off-by: Con Kolivas <[EMAIL PROTECTED]>
Cc: Ingo Molnar <[EMAIL PROTECTED]>
Cc: Nick Piggin <[EMAIL PROTECTED]>
Cc: "Siddha, Suresh B" <[EMAIL PROTECTED]>
What follows this email is a patch series for the latest version of the RSDL
cpu scheduler (ie v0.29). I have addressed all bugs that I am able to
reproduce in this version so if some people would be kind enough to test if
there are any hidden bugs or oops lurking, it would be nice to know in
On Sunday 11 March 2007 14:39, Andrew Morton wrote:
> > On Sun, 11 Mar 2007 14:59:28 +1100 Con Kolivas <[EMAIL PROTECTED]> wrote:
> > > Bottom line: we've had a _lot_ of problems with the new yield()
> > > semantics. We effectively broke back-compatibility by changing its
> > > behaviour a lot,
On Sun, 11 Mar 2007 13:28:22 +1100 "Con Kolivas" <[EMAIL PROTECTED]> wrote:
>> Well... are you advocating we change sched_yield semantics to a
>> gentler form?
On Sat, Mar 10, 2007 at 07:16:14PM -0800, Andrew Morton wrote:
> From a practical POV: our present yield() behaviour is so truly awful
On Sat, 10 Mar 2007, Linus Torvalds wrote:
> (That said, using "struct itimerspec" might be a good idea. That would
> also obviate the need for TFD_TIMER_SEQ, since an itimerspec automatically
> has both "base" and "incremental" parts).
But TFD_TIMER_SEQ is a simple auto-rearm case of
> On Sun, 11 Mar 2007 14:59:28 +1100 Con Kolivas <[EMAIL PROTECTED]> wrote:
> > Bottom line: we've had a _lot_ of problems with the new yield() semantics.
> > We effectively broke back-compatibility by changing its behaviour a lot,
> > and we can't really turn around and blame application
Hi,
Since linux 2.6.20 the kernel log shows at boot time these error. The
system are stable, but shows this, that in 2.6.19.N does not show.
(please CC to my email, i am currently not subscribe to lkml)
Thanks,
Linux version 2.6.20.2 ([EMAIL PROTECTED]) (gcc version 3.4.6) #1 PREEMPT Fri
Mar
On Sunday 11 March 2007 14:16, Andrew Morton wrote:
> > On Sun, 11 Mar 2007 13:28:22 +1100 "Con Kolivas" <[EMAIL PROTECTED]>
> > wrote: Well... are you advocating we change sched_yield semantics to a
> > gentler form?
> >
> >From a practical POV: our present yield() behaviour is so truly awful
On Sat, Mar 10, 2007 at 06:09:34PM -0800, Christoph Lameter wrote:
> i386: Convert to quicklists
> Implement the i386 management of pgd and pmds using quicklists.
I approve, though it would be nice if ptes had an interface operating
on struct page * to use.
On Sat, Mar 10, 2007 at 06:09:34PM
On Sun, 2007-03-11 at 03:58 +0100, Jan Engelhardt wrote:
> >-#define ARRAY_SIZE(x) (sizeof(x) / sizeof((x)[0]))
> >+#define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) +
> >__must_be_array(arr))
> >+
> 80 cols *cough* :)
I think your cough added a column?
Rusty.
-
To unsubscribe from this
> On Sun, 11 Mar 2007 13:28:22 +1100 "Con Kolivas" <[EMAIL PROTECTED]> wrote:
> Well... are you advocating we change sched_yield semantics to a
> gentler form?
>From a practical POV: our present yield() behaviour is so truly awful that
it's basically always a bug to use it. This probably isn't a
On Saturday 10 March 2007 06:30, Jeff Garzik wrote:
> Linux Kernel Mailing List wrote:
> > Gitweb:
> > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=df33c77e3981e71afc8727ee5c432ba1a1bba68c
> > Commit: df33c77e3981e71afc8727ee5c432ba1a1bba68c
> > Parent:
On Mar 11 2007 13:50, Rusty Russell wrote:
>On Sat, 2007-03-10 at 02:04 +0100, Jan Engelhardt wrote:
>> Getting back at the macro, how would you like to have it merged?
>
>Well, this is what I sent to Linus and Andrew (many thanks to those who
>made appropriately whimsical *or* useful comments):
On Sat, 2007-03-10 at 02:04 +0100, Jan Engelhardt wrote:
> Getting back at the macro, how would you like to have it merged?
Well, this is what I sent to Linus and Andrew (many thanks to those who
made appropriately whimsical *or* useful comments):
diff -r 1ccdf46b0f41
On 11/03/07, Matt Mackall <[EMAIL PROTECTED]> wrote:
I've tested -mm2 against -mm2+noyield and -mm2+rsdl+noyield. The
noyield patch simply makes the sched_yield syscall return immediately.
Xorg and all tests are run at nice 0.
Loads:
memload: constant memcpy of 16MB buffer
execload: constant
On Sat, 2007-03-10 at 02:31 -0200, Mauro Carvalho Chehab wrote:
> From: Trent Piepho <[EMAIL PROTECTED]>
>
> When a module uses symbol_get() to increase the ref count of another
> module, there is no record what module called symbol_get(). A module
> can
> show up as having other users, but
This patch wire the timerfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/arch/i386/kernel/syscall_table.S
===
--- linux-2.6.20.ep2.orig/arch/i386/kernel/syscall_table.S
This patch wire the timerfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/arch/x86_64/ia32/ia32entry.S
===
--- linux-2.6.20.ep2.orig/arch/x86_64/ia32/ia32entry.S
This patch implement the necessary compat code for the timerfd system call.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/fs/compat.c
===
--- linux-2.6.20.ep2.orig/fs/compat.c 2007-03-10 15:58:03.0
This patch wire the signalfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/include/asm-x86_64/unistd.h
===
--- linux-2.6.20.ep2.orig/include/asm-x86_64/unistd.h
This patch introduces a new system call for timers events delivered
though file descriptors. This allows timer event to be used with
standard POSIX poll(2), select(2) and read(2). As a consequence of
supporting the Linux f_op->poll subsystem, they can be used with
epoll(2) too.
The system call is
This patch implement the necessary compat code for the signalfd system call.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/fs/compat.c
===
--- linux-2.6.20.ep2.orig/fs/compat.c 2007-03-10 15:57:00.0
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the associated dentries (dentry names will be same for classes of file*).
This patch series implements the new signalfd() system call.
I took part of the original Linus code (and you know how
badly it can be broken :), and I added even more breakage ;)
Signals are fetched from the same signal queue used by the process,
so signalfd will compete with standard kernel
This patch wire the signalfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/arch/i386/kernel/syscall_table.S
===
--- linux-2.6.20.ep2.orig/arch/i386/kernel/syscall_table.S
i386: Use standard list macros.
Get rid of generating a list via page->index and page->private. Use
page->lru instead.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
Index: linux-2.6.21-rc3/arch/i386/mm/pgtable.c
===
---
[PATCH] SLUB The unqueued slab allocator v4
V4->V5:
- Single object slabs only for slabs > slub_max_order otherwise generate
sufficient objects to avoid frequent use of the page allocator. This is
necessary to compensate for fragmentation caused by frequent uses of
the page allocator. We
Enable poisoning / redzoning for slabs with constructors or SLAB_DEWSTROY_BY_RCU
We cannot poison the object itself but we can poison padding spaces and do
the redzoning. For that we introduce another flag controlling object
poisoning.
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
Index:
x86_64: Add quicklist for pgd.
A second quicklist is useful to separate out PGD handling. We can carry
the initialized pgds over to the next process needing them. This
avoids the zeroing of the pgds on free that we had to introduce
in the last patch.
Also clean up the pgd_list handling to use
On Sat, 2007-03-10 at 17:57 -0800, Davide Libenzi wrote:
> On Sat, 10 Mar 2007, Nicholas Miell wrote:
>
> > If that's the goal, somebody should start thinking about reducing the
> > contents of struct file to the bare minimum (i.e. not much more than a
> > file_operations pointer).
>
> That's
Add slub_max_order
Avoid slabs getting to large. Do no longer enforce slub_min_objects
if the slab gets bigger than slub_max_order.
I am not sure if we really want this. Maybe we should make the
selection of the base page size depending on page allocator
defrag behavior? I.e. try to restrict
Slub: Remove special casing for page sized slabs
After we have used quicklist so that arches can avoid using the slab
allocator to manage page table pages we can now remove the special
casing from slub.
This is against SLUB V5
Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
Index:
i386: Convert to quicklists
Implement the i386 management of pgd and pmds using quicklists.
The i386 management of page table pages currently uses page sized slabs.
The page state is therefore mainly determined by the slab code. However,
i386 also uses its own fields in the page struct to mark
Abstract quicklist from the IA64 implementation
Extract the quicklist implementation for IA64, clean it up
and generalize it to:
1. Allow multiple quicklists
2. Add support for constructors and destructors..
Quicklist allocation and frees occur inline. The support
for constructors /
x86_64: Convert to use a single quicklists
This adds caching of pgds and puds, pmds, pte. That way we can
avoid costly zeroing and initialization of special mappings in the
pgd.
The first patch just adds a simple implementation using a single
quicklist. As a consequence we need to zero a pgd
This patchset introduces an arch independent framework to handle lists
of recently used page table pages.
Page table pages have the characteristics that they are typically zero
or in a known state when they are freed. This is usually the exactly
same state as needed after allocation. So it makes
On Sat, 10 Mar 2007, Nicholas Miell wrote:
> If that's the goal, somebody should start thinking about reducing the
> contents of struct file to the bare minimum (i.e. not much more than a
> file_operations pointer).
That's already pretty smal, and the single inode (and maybe dentry) will
make
On Sat, Mar 10, 2007 at 04:21:01PM -0800, Andrew Morton wrote:
> We'd be needing a changelog for that.
Done; sent separately from this email.
> Please update the procfs documentation.
Done.
> Does the patch also cover /proc/pid/smaps?
Yes, and numa_maps.
Thanks!
--
Kees Cook
-
To
On Sat, 2007-03-10 at 16:35 -0800, Linus Torvalds wrote:
>
> On Sat, 10 Mar 2007, Nicholas Miell wrote:
> > >
> > > I'd actually much rather do POSIX timers the other way around: associate
> > > a
> > > generic notification mechanism with the file descriptor, and then
> > > implement
I've tested -mm2 against -mm2+noyield and -mm2+rsdl+noyield. The
noyield patch simply makes the sched_yield syscall return immediately.
Xorg and all tests are run at nice 0.
Loads:
memload: constant memcpy of 16MB buffer
execload: constant re-exec of a trivial shell script
forkload: constant
The /proc/pid/ "maps", "smaps", and "numa_maps" files contain sensitive
information about the memory location and usage of processes. Issues:
- maps should not be world-readable, especially if programs expect any
kind of ASLR protection from local attackers.
- maps cannot just be 0400
On Sat, Mar 10, 2007 at 04:21:01PM -0800, Andrew Morton wrote:
> > On Sat, 10 Mar 2007 10:33:41 -0800 Kees Cook <[EMAIL PROTECTED]> wrote:
> > Here's another revision, with both the "can ptrace" and the global /proc
> > knob;
>
> We'd be needing a changelog for that.
>
> Please update the
On 3/11/07, Thibaut VARENE <[EMAIL PROTECTED]> wrote:
On 3/11/07, Con Kolivas <[EMAIL PROTECTED]> wrote:
> Has anyone had any trouble with RSDL on the stable kernels (ie not -mm)?
Tested fine so far on ppc, ia64 and (mostly) parisc.
I meant ppc64, actually.
Gomen.
--
Thibaut VARENE
On 3/11/07, Con Kolivas <[EMAIL PROTECTED]> wrote:
Has anyone had any trouble with RSDL on the stable kernels (ie not -mm)?
Tested fine so far on ppc, ia64 and (mostly) parisc.
HTH
--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
-
To unsubscribe from this list: send the line
On Sat, 2007-03-10 at 17:16 -0500, Robert P. J. Day wrote:
> Delete apparently unused header file drivers/scsi/pci2000.h.
This was apparently missed by Christoph when he removed the driver ...
I'll add it to the queue. For future SCSI work, could you cc
linux-scsi@vger.kernel.org please? That
Thomas Gleixner wrote:
> It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute
> time, which is read back from the clocksource, even if we use a relative
> value for real hardware clock event devices to program the next event.
> We calculate the delta between the absolute event and
On Sat, 10 Mar 2007, Nicholas Miell wrote:
> >
> > I'd actually much rather do POSIX timers the other way around: associate a
> > generic notification mechanism with the file descriptor, and then
> > implement posix_timer_create() on top of timerfd. Now THAT sounds like a
> > clean unix-like
On Sat, 2007-03-10 at 14:42 -0800, Linus Torvalds wrote:
>
> On Sat, 10 Mar 2007, Nicholas Miell wrote:
> >
> > Care to elaborate on why they're a horrible crock?
>
> It's a *classic* case of an interface that tries to do everything under
> the sun.
>
> Here's a clue: look at any system call
> On Sat, 10 Mar 2007 10:33:41 -0800 Kees Cook <[EMAIL PROTECTED]> wrote:
> Here's another revision, with both the "can ptrace" and the global /proc
> knob;
We'd be needing a changelog for that.
Please update the procfs documentation.
Does the patch also cover /proc/pid/smaps?
-
To unsubscribe
Clean up the handling of low voltage MMC cards.
The latest MMC and SD specs both agree that the low
voltage range is defined as 1.65-1.95V and is signified
by bit 7 in the OCR. An old Sandisk spec implied that
bits 7-0 represented voltages below 2.0V in 1V increments,
and the code was accordingly
On Mar 8 2007 11:45, Kanhu Rauta wrote:
>
> 1>in case of fragmention i am getting only one packet at the
> hook,While analyzing the ip header it says this is the assembled
> packet(skb->len=1528,offset=0,MF=0).
conntrack assembles defragmented packets.
> While dumping the data(for 0 to 1528
Here's a big bugfix for sched rsdl 0.28
---
kernel/sched.c |7 +++
1 file changed, 7 insertions(+)
Index: linux-2.6.21-rc3-mm2/kernel/sched.c
===
--- linux-2.6.21-rc3-mm2.orig/kernel/sched.c2007-03-11 11:04:38.0
Thomas Gleixner wrote:
> The clocksource is not used until the clocksource is installed. Also the
> periodic mode during boot, when the clock event device supports periodic
> mode, is not reading the time. It relies on the clock event device
> getting it straight.
Yes. This could be one source
On Sunday 11 March 2007 06:11, Willy Tarreau wrote:
> On Sat, Mar 10, 2007 at 01:09:35PM -0500, Stephen Clark wrote:
> > Con Kolivas wrote:
> > >Here is an update for RSDL to version 0.28
> > >
> > >Full patch:
> > >http://ck.kolivas.org/patches/staircase-deadline/2.6.20-sched-rsdl-0.28.
> >
On Mar 10 2007 23:45, Sam Ravnborg wrote:
>> >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
>> >>
>> >> Whether the 'working config file path' should change when you do
>> >> 'Save as Alternate' or not, is a menuconfig axiom. Ask Sam Ravnborg
>> >> if you want it changed :-)
>>
On Sunday 11 March 2007 10:34, Con Kolivas wrote:
> On Sunday 11 March 2007 05:21, Mark Lord wrote:
> > Con Kolivas wrote:
> > > On Saturday 10 March 2007 05:07, Mark Lord wrote:
> > >> Mmm.. when it's good, it's *really* good.
> > >> My desktop feels snappier and all of that.
> > >
> > >..
> > >
On Sat, 2007-03-10 at 14:52 -0800, Jeremy Fitzhardinge wrote:
> When booting under Xen, you'll get this if you're using both the xen
> clocksource and clockevent drivers. However, it seems that during boot
> on a NO_HZ HIGHRES_TIMERS system, the kernel does not use the Xen
> clocksource until it
On Sunday 11 March 2007 05:21, Mark Lord wrote:
> Con Kolivas wrote:
> > On Saturday 10 March 2007 05:07, Mark Lord wrote:
> >> Mmm.. when it's good, it's *really* good.
> >> My desktop feels snappier and all of that.
> >
> >..
> >
> >> But when it's bad, it stinks.
> >> Like when a "make -j2"
Hi everybody,
I'm writing a Linux driver for USB Video Class (UVC) devices. Before
submitting it to the kernel, there are still a few rough corners I'd like to
polish. Comments would be appreciated for the following one.
The UVC spec defines a way for device vendors to provide extensions to
I've been thinking a bit more about how useful an absolute timeout is
for a oneshot timer in a virtual environment.
In principle, absolute times are generally preferable. A relative
timeout means "timeout in X ns from now", but the meaning of "now" is
ambiguous, particularly if the vcpu can be
On Sunday 11 March 2007 04:01, James Cloos wrote:
> > "Con" == Con Kolivas <[EMAIL PROTECTED]> writes:
>
> Con> It's sad that sched_yield is still in our graphics card drivers ...
>
> I just did a recursive grep(1) on my mirror of the freedesktop git
> repos for sched_yield. This only checked
On Saturday 10 March 2007 13:16, Mockern wrote:
> I have a problem with cat < /dev/my_ttyS0 (see strace output below).
> cat function is not blocked. I don't understand why it is not stopped
> at read(0, __ and terminated?
> Thank you
Because /dev/my_ttyS0 is probaly a null file.
Please show
On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
>
> On Mar 10 2007 22:27, Sam Ravnborg wrote:
> >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
> >>
> >> Whether the 'working config file path' should change when you do
> >> 'Save as Alternate' or not, is a
On Sat, 10 Mar 2007, Nicholas Miell wrote:
>
> Care to elaborate on why they're a horrible crock?
It's a *classic* case of an interface that tries to do everything under
the sun.
Here's a clue: look at any system call that takes a union as part of its
arguments. Count them. I think we have
On Sunday 11 March 2007 03:53, Nicolas Mailhot wrote:
> Le dimanche 11 mars 2007 à 01:03 +1100, Con Kolivas a écrit :
> > On Saturday 10 March 2007 22:49, Nicolas Mailhot wrote:
> > > Oops
> > >
> > > ⇒ http://bugzilla.kernel.org/show_bug.cgi?id=8166
> >
> > Thanks very much. I can't get your
On Sat, 10 Mar 2007, Nicholas Miell wrote:
> I never complained about one timer per fd (although, now that you
> mention it, that would get a bit excessive if you have thousands of
> outstanding timers).
Right, of course.
> > The real-time and monotonic selection can be added.
>
> IOW, the
Hi1
> > It should explain why it is okay to proceed when we can't change to
> > text console.
> >
> See updated comment in attached patch. It's really up to the caller to
> decide what to do if we can't switch the console - currently all callers
> ignore the return code so I assume that it's
On 3/10/07, Willy Tarreau <[EMAIL PROTECTED]> wrote:
On Sat, Mar 10, 2007 at 04:56:57PM -0500, michael chang wrote:
> On 3/10/07, Willy Tarreau <[EMAIL PROTECTED]> wrote:
> >BTW, Con, I think that you should base your work on 2.6.20.[23] and not
> >2.6.20 next time, due to this conflict. It will
Delete apparently unused header file include/linux/elfnote.h.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
not sure who's responsible for this.
diff --git a/include/linux/elfnote.h b/include/linux/elfnote.h
deleted file mode 100644
index 67396db..000
---
Hi!
> > ...how does qpe know when to repaint the screen, anyway?
>
> QPE doesn't need to repaint the screen after wake-up - the framebuffer
> memory is retained so the PXA270 lcd controller simply displays what was
> last on the screen when it is re-enabled.
That probably means QPE is broken on
From: Dale Farnsworth <[EMAIL PROTECTED]>
Signed-off-by: Dale Farnsworth.org <[EMAIL PROTECTED]
---
drivers/rtc/Kconfig | 10 +
drivers/rtc/Makefile |1
drivers/rtc/rtc-max6900.c | 312
3 files changed, 323 insertions(+)
Index:
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
If swsusp is using the platform mode during the resume and the image cannot be
read, the platform mode should be switched off before software_resume() returns.
Make it happen.
Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]>
Acked-by: Pavel Machek
Delete apparently unused header file drivers/serial/crisv10.h.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
diff --git a/drivers/serial/crisv10.h b/drivers/serial/crisv10.h
deleted file mode 100644
index 4a23340..000
--- a/drivers/serial/crisv10.h
+++ /dev/null
@@ -1,136 +0,0
1 - 100 of 502 matches
Mail list logo
