On Thursday 15 February 2007 19:46, bert hubert wrote:
> Both 1 and 2 are currently limiting factors when I enter the 100kqps domain
> of name serving. This doesn't mean the rest of my code is as tight as it
> could be, but I spend a significant portion of time in the kernel even at
> moderate
move of_irq_to_resource to prom_parse.c (powerpc)
Here is the patch that follows Benjamin Herrenschmidt's comments to move
of_irq_to_resource from prom.h to prom_parse.c. It solves the following issue :
> include/asm/prom.h: In function `of_irq_to_resource':
> include/asm/prom.h:339: warning:
On Feb 15, 2007, at 11:11 AM, Ananiev, Leonid I wrote:
It returns -EIOCBRETRY without guaranteeing that kick_iocb() will be
called. This can lead to operations hanging
If EIOCBRETRY then generic_file_aio_write() will be recalled for the
same iocb.
Only if kick_iocb() is called. It won't
2) On the client facing side (port 53), I'd very much hope for a
way to
do 'recvv' on datagram sockets, so I can retrieve a whole bunch of
UDP datagrams with only one kernel transition.
I want to highlight this point that Bert is making.
Whenever we talk about AIO and kernel
On Thu, Feb 15, 2007 at 07:54:33PM +0100, Helge Deller wrote:
| Hi Cyrill,
|
| please include the "err1" label as well inside the #if / #endif clause.
| err1 is used only when CONFIG_HP300 is defined and in the parisc-case you
currently get an unused label warning...
|
| Helge
|
| On Thursday
I was wondering if there was some way to make a Kconfig menu either
be just a menu or a choice depending on another bool being set or not.
What I'm trying to accomplish is if CONFIG_ONLY_HAVE_ONE is set I
want it so you can only select on option, however if
CONFIG_ONLY_HAVE_ONE is not set
On Thu, Feb 15, 2007 at 08:44:19AM -0600, Eric Van Hensbergen wrote:
...
> diff --git a/fs/9p/vfs_addr.c b/fs/9p/vfs_addr.c
> index bed48fa..d43d6fb 100644
> --- a/fs/9p/vfs_addr.c
> +++ b/fs/9p/vfs_addr.c
> @@ -6,6 +6,9 @@
> * Copyright (C) 2005 by Eric Van Hensbergen <[EMAIL PROTECTED]>
> *
On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
> On Thu, Feb 15, 2007 at 05:52:32PM +0100, Ingo Molnar ([EMAIL PROTECTED])
> wrote:
> > +The syslet atom is a small, fixed-size (44 bytes on 32-bit) piece of
> > +user-space memory, which is the basic unit of execution within the syslet
> >
On Thu, 15 Feb 2007, Ingo Molnar wrote:
> +ENTRY(async_thread_helper)
> + CFI_STARTPROC
> + /*
> + * Allocate space on the stack for pt-regs.
> + * sizeof(struct pt_regs) == 64, and we've got 8 bytes on the
> + * kernel stack already:
> + */
> + subl $64-8, %esp
>
On Thu, Feb 15, 2007 at 07:46:56PM +0100, bert hubert ([EMAIL PROTECTED]) wrote:
> 1) batch, and wait for, with proper error reporting:
> socket();
> [ setsockopt(); ]
> bind();
> connect();
> gettimeofday(); // doesn't *always* happen
> send();
> recv();
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Sun, 11 Feb 2007 15:03:24 -0500 Mathieu Desnoyers <[EMAIL PROTECTED]>
> wrote:
>
> > Linux Kernel Markers, architecture independant code.
> >
> > Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
> >
> > ...
> >
> > +
> > +#ifndef MARK
> >
> It returns -EIOCBRETRY without guaranteeing that kick_iocb() will be
> called. This can lead to operations hanging
If EIOCBRETRY then generic_file_aio_write() will be recalled for the
same iocb.
> It overwrites -EIOCBQUEUED, leading to an aio_complete() while a
> retry is happening.
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Sun, 11 Feb 2007 15:03:27 -0500 Mathieu Desnoyers <[EMAIL PROTECTED]>
> wrote:
>
> > Linux Kernel Markers, non optimized architectures
> >
> > This patch also includes marker code for non optimized architectures.
>
> I think once we've done this
On Thu, 15 Feb 2007, Ingo Molnar wrote:
> /*
> + * Move user-space context from one kernel thread to another.
> + * This includes registers and FPU state. Callers must make
> + * sure that neither task is running user context at the moment:
> + */
> +void
> +move_user_context(struct task_struct
On Thu, Feb 15, 2007 at 10:25:37AM -0800, Linus Torvalds ([EMAIL PROTECTED])
wrote:
> > static void syslet_setup(struct syslet *s, int nr, void *arg1...)
> > {
> > s->flags = ...
> > s->arg[1] = arg1;
> >
> > }
> >
> > long glibc_async_stat(const char *path, struct stat *buf)
>
On Thu, 2007-02-15 at 19:52 +0100, Frank van Maarseveen wrote:
> FYI,
>
> Just captured this one, I'm not sure it's NFS at fault because I saw
> at least another AIO related mm/truncate.c:398 report with a totally
> different stack trace.
>
> The machine seems still running happily, as usual
Hi all,
On Wed, 14 Feb 2007, Jan Engelhardt wrote:
On Feb 14 2007 16:10, sfaibish wrote:
1. DualFS has only one copy of every meta-data block. This copy is
in the meta-data device,
Where does this differ from typical filesystems like xfs?
At least ext3 and xfs have an option to store the
On 2/15/07, v j <[EMAIL PROTECTED]> wrote:
So far I have heard nothing but, "if you don't contribute, screw you."
Well, so far I have heard from you is "let me use my closed-source
drivers in Linux or bye bye".
All this is fine. Just say so. Make it black and white. Make it
It is not black
On Thu, 15 Feb 2007, Sergei Organov wrote:
>
> I agree that if the warning has no true positives, it sucks. The problem
> is that somehow I doubt it has none. And the reasons for the doubt are:
Why do you harp on "no true positives"?
That's a pointless thing. You can make *any* warning have
Hi Cyrill,
please include the "err1" label as well inside the #if / #endif clause.
err1 is used only when CONFIG_HP300 is defined and in the parisc-case you
currently get an unused label warning...
Helge
On Thursday 15 February 2007, Cyrill V. Gorcunov wrote:
> Thist patch prevents from
On Thu, 15 Feb 2007, Mike Panetta wrote:
> I am not on the list (corperate email sucks) so please CC any replies to
> me. Thanks.
>
> I am working on a project that has run in to what seems to be an
> interrupt priority problem. We switched mainboards in our product and
> went from a system
Le jeudi 15 février 2007 à 10:20 -0800, v j a écrit :
> So far I have heard nothing but, "if you don't contribute, screw you."
> All this is fine. Just say so. Make it black and white. Make it
> perfectly clear what is and isn't legal. If we can't load proprietary
> modules, then so be it. It will
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Thu, 15 Feb 2007, Sergei Organov wrote:
[...Skip things I agree with...]
>> > But if you have
>> >
>> >unsigned char *mystring;
>> >
>> >len = strlen(mystring);
>> >
>> > then please tell me how to fix that warning without making the code
FYI,
Just captured this one, I'm not sure it's NFS at fault because I saw
at least another AIO related mm/truncate.c:398 report with a totally
different stack trace.
The machine seems still running happily, as usual with a considerable
load. kernel is tainted by fglrx.
kernel: BUG: warning at
On Thu, Feb 15, 2007 at 09:42:32AM -0800, Linus Torvalds wrote:
> We know one interface: the current aio_read() one. Nobody really _likes_
[...]
> Others? We don't know yet. And exposing complex interfaces that may not be
> the right ones is much *worse* than exposing simple interfaces (that
On 2/15/07, Brian D. McGrew <[EMAIL PROTECTED]> wrote:
Good morning all,
We're seeing a problem where an application is being killed from what
appears to be an out of memory issue. Can anyone offer any insight on
this for me?
See Documentation/vm/overcommit-accounting.
Lee
-
To unsubscribe
On 2/15/07, v j <[EMAIL PROTECTED]> wrote:
So far I have heard nothing but, "if you don't contribute, screw you."
All this is fine. Just say so. Make it black and white. Make it
perfectly clear what is and isn't legal. If we can't load proprietary
modules, then so be it. It will help everybody
Hi,
On Thu, 15 Feb 2007, David Howells wrote:
> > This is really the weak point - it offers no advantage over an equivalent
> > implementation in user space (e.g. in the module tools). So why has to be
> > done in the kernel?
>
> Because the init_module() system call is the common point of
On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
>
> So we just need to describe the way we want to see new interface -
> that's it.
Agreed. Absolutely.
But please keep the kernel interface as part of that. Not just a strange
and complex kernel interface and then _usable_ library interfaces that
On Thu, Feb 15, 2007 at 05:52:28PM +0100, Ingo Molnar wrote:
> From: Ingo Molnar <[EMAIL PROTECTED]>
> +static struct syslet_uatom __user *
> +exec_atom(struct async_head *ah, struct task_struct *t,
> + struct syslet_uatom __user *uatom)
> +{
> + struct syslet_uatom __user *last_uatom;
>
I am not on the list (corperate email sucks) so please CC any replies to
me. Thanks.
I am working on a project that has run in to what seems to be an
interrupt priority problem. We switched mainboards in our product and
went from a system where the EHCI controller IRQ was of a fairly high
On Thu, 2007-02-15 at 19:00 +0100, Marcin Juszkiewicz wrote:
> Dnia czwartek, 15 lutego 2007, [EMAIL PROTECTED] napisał:
> > On Thu, 15 Feb 2007 05:14:08 PST, Andrew Morton said:
>
> > git-backlight.patch contains this:
> >
> > +config BACKLIGHT_PROGEAR
> > + tristate "Frontpath ProGear
If invalidate_inode_pages2_range() will return EIOCBRETRY as the patch
"aio: fix kernel bug when page is temporally busy"
Sorry Leonid, this patch is not safe.
It returns -EIOCBRETRY without guaranteeing that kick_iocb() will be
called. This can lead to operations hanging, both AIO and
On Thursday 15 February 2007 16:37, Benny Amorsen wrote:
> > "JDL" == Jan De Luyck <[EMAIL PROTECTED]>
> > writes:
>
> JDL> I think a nice example of that might be the Linksys WRT54G
> JDL> routers.
>
> They don't ship with Linux anymore, except the WRT54GL. Apparently
> switching was
On Thu, Feb 15, 2007 at 05:52:59PM +0100, Ingo Molnar wrote:
> provide an optimized assembly version of sys_umem_add().
> --- linux.orig/arch/i386/lib/getuser.S
> +++ linux/arch/i386/lib/getuser.S
> +sys_umem_add:
> + movl 0x4(%esp), %ecx# uptr
> + movl 0x8(%esp),
So far I have heard nothing but, "if you don't contribute, screw you."
All this is fine. Just say so. Make it black and white. Make it
perfectly clear what is and isn't legal. If we can't load proprietary
modules, then so be it. It will help everybody if this is out in the
clear, instead of
Linus Torvalds wrote:
On Thu, 15 Feb 2007, Randy Dunlap wrote:
so, are we going to get a revert of 42da9cbd3eedde33a42acc2cb06f454814cf5de0 ?
Has that been requested? or are there other plans?
It should be fixed now (I had patches from Nick, but got sidetracked by
trying to fix metacity for
On Thursday 15 February 2007 17:15, Maynard Johnson wrote:
> >>+void spu_set_profile_private(struct spu_context * ctx, void * profile_info,
> >>+ struct kref * prof_info_kref,
> >>+ void (* prof_info_release) (struct kref * kref))
> >>+{
> >>+
On Thu, Feb 15, 2007 at 09:42:32AM -0800, Linus Torvalds ([EMAIL PROTECTED])
wrote:
>
>
> On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
> >
> > Userspace_API_is_the_ever_possible_last_thing_to_ever_think_about. Period
> > . // <- wrapped one
>
> No, I really think you're wrong.
>
> In many
On Thu, Feb 15, 2007 at 05:52:32PM +0100, Ingo Molnar ([EMAIL PROTECTED]) wrote:
> +The syslet atom is a small, fixed-size (44 bytes on 32-bit) piece of
> +user-space memory, which is the basic unit of execution within the syslet
> +framework. A syslet represents a single system-call and its
On Thu, 15 Feb 2007, Ingo Molnar wrote:
>
> this is the v2 release of the syslet subsystem. This is an interim
> release, not all known and pending items are fixed/changed yet - the
> tree is still work in progress:
I'm still not a huge fan of the user space interface, but at least the
core
On Thu, Feb 15, 2007 at 09:39:33AM -0800, Davide Libenzi
(davidel@xmailserver.org) wrote:
> On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
>
> > On Thu, Feb 15, 2007 at 09:05:13AM -0800, Davide Libenzi
> > (davidel@xmailserver.org) wrote:
> > >
> > > I actually think that building chains of
On Tue, Feb 13 2007, Tejun Heo wrote:
> >>So, actually, I was thinking about *always* using the non-NCQ FUA
> >>opcode. As currently implemented, FUA request is always issued by
> >>itself, so NCQ doesn't make any difference there. So, I think it
> >>would be better to turn on FUA on
On Thu, 15 Feb 2007, Randy Dunlap wrote:
>
> so, are we going to get a revert of 42da9cbd3eedde33a42acc2cb06f454814cf5de0 ?
> Has that been requested? or are there other plans?
It should be fixed now (I had patches from Nick, but got sidetracked by
trying to fix metacity for the gnome
Dnia czwartek, 15 lutego 2007, [EMAIL PROTECTED] napisał:
> On Thu, 15 Feb 2007 05:14:08 PST, Andrew Morton said:
> git-backlight.patch contains this:
>
> +config BACKLIGHT_PROGEAR
> + tristate "Frontpath ProGear Backlight Driver"
> + depends on BACKLIGHT_CLASS_DEVICE && PCI && X86
>
Looking at this one more time, I think it actually may be buggy:
> @@ -147,6 +147,7 @@ struct ib_cq *ehca_create_cq(struct ib_d
> spin_lock_init(_cq->spinlock);
> spin_lock_init(_cq->cb_lock);
> spin_lock_init(_cq->task_lock);
> +init_completion(_cq->zero_callbacks);
So
Thist patch prevents from improper call of release_region
if the code has been compiled without CONFIG_HP300 support.
Signed-off-by: Cyrill V. Gorcunov <[EMAIL PROTECTED]>
---
drivers/input/keyboard/hilkbd.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git
+static void
+__mark_async_thread_ready(struct async_thread *at, struct
async_head *ah)
+{
+ list_del(>entry);
+ list_add_tail(>entry, >ready_async_threads);
+__mark_async_thread_busy(struct async_thread *at, struct
async_head *ah)
+{
+ list_del(>entry);
+
Location:
ftp://ftp.kernel.org/pub/linux/kernel/people/bunk/linux-2.6.16.y/testing/
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
Changes since 2.6.16.40:
Adrian Bunk (3):
Revert "[Bluetooth] Fix compat ioctl for BNEP, CMTP and HIDP"
[ALSA]
On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
>
> Userspace_API_is_the_ever_possible_last_thing_to_ever_think_about. Period
> . // <- wrapped one
No, I really think you're wrong.
In many ways, the interfaces and especially data structures are *more*
important than the code.
The code we can
Thanks, queued 1, 2, 3 and 5 for 2.6.21.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
> On Thu, Feb 15, 2007 at 09:05:13AM -0800, Davide Libenzi
> (davidel@xmailserver.org) wrote:
> >
> > I actually think that building chains of syscalls bring you back to a
> > multithreaded solution. Why? Because suddendly the service thread become
On Thu, 15 Feb 2007 05:14:08 PST, Andrew Morton said:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-mm1/
>
> Will appear later at
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm1/
git-backlight.patch contains this:
+config
Roman Zippel <[EMAIL PROTECTED]> wrote:
> > Now, this is not a complete solution by any means: the core kernel is not
> > protected, and nor are /dev/mem or /dev/kmem, but it denies (or at least
> > controls) one relatively simple attack vector.
>
> This is really the weak point - it offers no
On Wed, Feb 14, 2007 at 04:10:50PM -0800, Jeremy Fitzhardinge wrote:
> Eric W. Biederman wrote:
> > Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> >
> >
> >> Add Xen interface header files. These are taken fairly directly from
> >> the Xen tree and hence the style is not entirely in
On Thu, Feb 15, 2007 at 09:05:13AM -0800, Davide Libenzi
(davidel@xmailserver.org) wrote:
> On Thu, 15 Feb 2007, Linus Torvalds wrote:
>
> > I don't think the "atom" approach is bad per se. I think it could be fine
> > to have some state information in user space. It's just that I think
> >
Linus Torvalds wrote:
> Here's a quick question: how many people have actually ever seen them used
> in "normal code"?
>
> Yeah. Nobody uses them. They're not all that portable (even within unixes
> they aren't always there, much less in other places), they are fairly
> obscure, and they are
Jan Beulich wrote:
> is there a particular reason for this?
>
Can't think of one.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
A previous cleanup misused need_poll, which had a fairly broken
interface. It implemented a growable array, changing the used
elements count itself, but leaving it up to the caller to fill in the
actual elements, including the entire array if the array had to be
reallocated. This worked because
Pierre Ossman wrote:
> Eugene Ilkov wrote:
>> PXAMCI: irq 0004 stat 2140
>
> Hang on. PXAMCI is a MMC controller, right? Perhaps the MMC timings
> aren't overlapping properly with the new stuff... I'm going to have to
> recheck my diagrams.
Hmm... depending on where you look, you get
On Wed, Feb 14, 2007 at 09:51:23PM -0800, Andrew Morton wrote:
> Whatever happens, please ensure that the final fix makes it into -stable
> as well. Jeff's version of this patch wasn't cc'ed to [EMAIL PROTECTED]
Paolo's patch was sent to -stable. His should be used everywhere, and mine
should
> Second, the probe and remove functions do not communicate whether an add
> or remove was successful. Combine this with the lack of port
> information in the adapter sysfs directory, and the userspace tool has
> no way of verifying a dynamic add/remove.
One way to communicate a return code is
On Thu, 15 Feb 2007, Linus Torvalds wrote:
> I don't think the "atom" approach is bad per se. I think it could be fine
> to have some state information in user space. It's just that I think
> complex interfaces that people largely won't even use is a big mistake. We
> should concentrate on
From: Ingo Molnar <[EMAIL PROTECTED]>
provide an optimized assembly version of the copy_uatom() method.
This is about 3 times faster than the C version.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/lib/getuser.S | 115
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> Index: linux/kernel/async.h
> ===
> --- /dev/null
> +++ linux/kernel/async.h
> @@ -0,0 +1,2 @@
> +
> +
this one sneaked in accidentally - i have removed it from my queue now.
Ingo
On Wed, 14 Feb 2007 00:19:06 + (GMT) Hugh Dickins wrote:
> On Tue, 13 Feb 2007, Randy Dunlap wrote:
> > From: Randy Dunlap <[EMAIL PROTECTED]>
> >
> > Don't check for pte swap entries when CONFIG_SWAP=n.
> > And save 'present' in the vec array.
> >
> > mm/built-in.o: In function
From: Ingo Molnar <[EMAIL PROTECTED]>
add include/linux/async.h which contains the kernel-side API
declarations.
it also provides NOP stubs for the !CONFIG_ASYNC_SUPPORT case.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
this is the v2 release of the syslet subsystem. This is an interim
release, not all known and pending items are fixed/changed yet - the
tree is still work in progress:
http://redhat.com/~mingo/syslet-patches/
The biggest conceptual change in v2 is the ability of cachemiss threads
to be
On Thu, 2007-02-15 at 10:37 -0600, Oscar Pearce wrote:
> On 10/28/06, Dave Jones <[EMAIL PROTECTED]> wrote:
> Ben,
> For the best part of a year since that N60 errata workaround
> went in, I've had floods of complaints from users of that
> driver
> about
From: Ingo Molnar <[EMAIL PROTECTED]>
add the kernel generic bits - these are present even if !CONFIG_ASYNC_SUPPORT.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
include/linux/sched.h | 23 ++-
kernel/exit.c
From: Ingo Molnar <[EMAIL PROTECTED]>
add the create_async_thread() way of creating kernel threads:
these threads first execute a kernel function and when they
return from it they execute user-space.
An architecture must implement this interface before it can turn
CONFIG_ASYNC_SUPPORT on.
From: Ingo Molnar <[EMAIL PROTECTED]>
mark clone() and fork() as not available for async execution.
Both need an intact user context beneath them to work.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/kernel/process.c |6
From: Arjan van de Ven <[EMAIL PROTECTED]>
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two (future) optimizations:
1) allocate the right size for the actual cpu rather than 512 bytes always
2)
From: Ingo Molnar <[EMAIL PROTECTED]>
provide an optimized assembly version of sys_umem_add().
It is about 2 times faster than the C version.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/lib/getuser.S | 27
From: Ingo Molnar <[EMAIL PROTECTED]>
this adds the data structures used by the syslet / async system calls
infrastructure.
This is used only if CONFIG_ASYNC_SUPPORT is enabled.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
From: Ingo Molnar <[EMAIL PROTECTED]>
wire up the new syslet / async system call syscalls and make it
thus available to user-space.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |6 ++
From: Ingo Molnar <[EMAIL PROTECTED]>
add the move_user_context() method to move the user-space
context of one kernel thread to another kernel thread.
User-space might notice the changed TID, but execution,
stack and register contents (general purpose and FPU) are
still the same.
An architecture
From: Ingo Molnar <[EMAIL PROTECTED]>
the core syslet / async system calls infrastructure code.
Is built only if CONFIG_ASYNC_SUPPORT is enabled.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
kernel/Makefile |1
kernel/async.c |
From: Ingo Molnar <[EMAIL PROTECTED]>
enable CONFIG_ASYNC_SUPPORT on x86.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
arch/i386/Kconfig |4
1 file changed, 4 insertions(+)
Index: linux/arch/i386/Kconfig
From: Ingo Molnar <[EMAIL PROTECTED]>
Add Documentation/syslet-design.txt with a high-level description
of the syslet concepts.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
Documentation/syslet-design.txt | 137
From: Ingo Molnar <[EMAIL PROTECTED]>
add include/linux/syslet.h which contains the user-space API/ABI
declarations. Add the new header to include/linux/Kbuild as well.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Arjan van de Ven <[EMAIL PROTECTED]>
---
include/linux/Kbuild
On Wed, Feb 14, 2007 at 10:27:10PM -0800, v j wrote:
> You are right. I have not contributed anything to Linux. Except one
> small patch to the MTD code. However, I don't think that is the point
> here. I am perfectly willing to live with the way Linux is today. I am
> telling you as a user that
Eugene Ilkov wrote:
> PXAMCI: irq 0004 stat 2140
Hang on. PXAMCI is a MMC controller, right? Perhaps the MMC timings
aren't overlapping properly with the new stuff... I'm going to have to
recheck my diagrams.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer
This patch will add two sysfs attributes to /sys/bus/ibmebus which can be used
to notify the ebus driver of added / removed ebus devices in the OF device
tree.
Echoing the device's location code (as found in the OFDT "ibm,loc-code"
property) into the "probe" attribute will notify ebus of addition
On Thu, 15 Feb 2007, Mockern wrote:
> I have a question about linux tty driver
>
> how to support cp, cat operations in tty driver (like tiny_tty)?
> (e.g. echo "hello tty" > /dev/ttyS3, cat < ttyS10 etc)
>
> There a lot of examples with char drivers, but I could not find it for tty
> Linux
This, I hope, is a final working version of this fix.
Jeff
--
Work email - jdike at linux dot intel dot com
a userspace fault or a kernelspace fault which will result in the
immediate death of the process. They should not be filled in as a
result of a kernelspace fault
On Thu, Feb 15, 2007 at 05:14:08AM -0800, Andrew Morton wrote:
>
> Temporarily at
>
> http://userweb.kernel.org/~akpm/2.6.20-mm1/
>
Hi,
It appears that the pcim_iomap_regions() function doesn't get the error
handling right. It BUGs early at boot with a backtrace along the lines of:
Eugene Ilkov wrote:
>
> I found another related patch
> http://mailman.laptop.org/pipermail/commits-kernel/2007-January/000554.html
>
> so i guess i'm not alone
>
You'd better pray that's not the problem you have because that revert
was because the hardware under development had problems.
>
>
On Thu, Feb 15, 2007 at 08:09:54AM -0800, Linus Torvalds ([EMAIL PROTECTED])
wrote:
> > > In other words, the "let user space sort out the complexity" is not a
> > > good
> > > answer. It just means that the interface is badly designed.
> >
> > Well, if we can setup iocb structure, why we can
Hi,
It is all I need ! no more 256 routing tables limitation !. But now it is time
for me to test it, but i am working on a kernel 2.6.9, do you think it will be
good ?
Why do I need so much routing tables? I need more than 500 routing tables
because my Linux have to work with 500 VLANs !. Do
On Thu, Feb 15, 2007 at 08:01:20AM +, Jan Beulich wrote:
> Ack.
Great, thanks for your help.
Jeff
--
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
v j wrote:
Not everybody has to be a contributor. The reason Linux is popular is
because of its openness. Take that away and see where it goes.
A few posts ago you said that your company had decided to take
away the openness by shipping closed source drivers to your
customers.
It is good to
VBE1.2 doesn't support function 15h (DDC) resulting in a 'hang' whilst
uncompressing kernel with some video cards. Make sure we check VBE version
before fiddling around with DDC.
http://bugzilla.kernel.org/show_bug.cgi?id=1458
Opened: 2003-10-30 09:12 Last update: 2007-02-13 22:03
:(
Much
David Chinner <[EMAIL PROTECTED]> wrote on 15 Feb 2007, 11:16 AM:
Subject: Re: xfs internal error on a new filesystem
>On Wed, Feb 14, 2007 at 10:24:27AM +, Ramy M. Hassan wrote:
>> Hello,
>> We got the following xfs internal error on one of our production servers:
>>
>> Feb 14 08:28:52
Andrew Morton wrote:
- The UBI tree got dropped due to probable lack of a git sync with
mainline (ie: it's a 13.5MB diff whcih doesn't apply very well)
Andrew, I apologize for this. Now it is fixed. It somehow got screwed
when I re-based it from mtd-2.6.git to linu-2.6.git. Please, do not
Jeremy,
is there a particular reason for this?
Thanks, Jan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: On Behalf Of v j
> On 2/14/07, Randy Dunlap <[EMAIL PROTECTED]> wrote:
> > We seem to have different definitions of open and closed.
>
> Open = 3rd party Linux drivers can be loaded. Closed = No third party
> Linux drivers can be loaded.
That is BSD-openness; the freedom to do anything
On 2/15/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Yeah and about the libsata/libata thingy, it is libata of course :)
libsata I will test later on, so be prepared allready for more ranting for me.
I even bought a cool sata controller with sata disk so I can mess around :D
Patrick
-
To
On 2/15/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
I appreciate the testing. One interesting but tedious test would be
suspend tests (both to disk and ram). Most libata drivers using new EH
should be ready for them. Oh, well, there's should and there's reality.
I will do these tests when I
On Thu, 15 Feb 2007, Evgeniy Polyakov wrote:
> >
> > In other words, the "let user space sort out the complexity" is not a good
> > answer. It just means that the interface is badly designed.
>
> Well, if we can setup iocb structure, why we can not setup syslet one?
(I'm cutting wildly, to
301 - 400 of 1060 matches
Mail list logo
