Andi Kleen wrote:
Stas Sergeev <[EMAIL PROTECTED]> writes:
Another way of saying the same thing: I absolutely hate seeing
patches that fix some theoretical issue that no Linux apps will ever
care about.
No, it is not theoretical, but it is mainly
about a DOS games and an MS linker, as
I choose the spec. If an implementation is not conformant to the
spec,
it doesn't "work".
Not to say that Linux doesn't have to work around bugs in actual
implementations, of course. And there's a lot of those. Too bad ;-)
Yah, well.. ok, let's say we have a spec... and an implementation that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Herrenschmidt wrote:
>>>Well, we have an unmaintained spec on one side that can't even be
>>>ordered from IEEE anymore and actual imlementations that work today,
>>>what do you chose ? ;)
>>
>>I choose the spec. If an implementation is not
Hi,
just tried the 2.6.11-mm3 and at boot-time my start scripts try to
enable DMA on my disk (hdparm -m16 -c1 -u1 -X69 /dev/hda).
But while running hdparm, the kernel waits many seconds and gives me
some DMA warnings/errors:
[dmesg output]
Uniform Multi-Platform E-IDE driver Revision:
> > Well, we have an unmaintained spec on one side that can't even be
> > ordered from IEEE anymore and actual imlementations that work today,
> > what do you chose ? ;)
>
> I choose the spec. If an implementation is not conformant to the spec,
> it doesn't "work".
>
> Not to say that Linux
OK - the first of them is merged in to the cifs bk tree.
The second one looks like an improvement on structuring of the cifs open
logic but needs review. I may have a chance to test it later in the
week.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Mon, 2005-03-14 at 15:51 +0100, Arjan van de Ven wrote:
> On Mon, 2005-03-14 at 17:48 +0300, Evgeniy wrote:
> > Here is a simple program.
> >
> > #include
> > #include
> > main(){
> > int err;
> > err=read(0,NULL,6);
> > printf("%d %d\n",err,errno);
> > }
> >
> > I think that it
On Mon, 2005-03-14 at 17:48 +0300, Evgeniy wrote:
> Here is a simple program.
>
> #include
> #include
> main(){
> int err;
> err=read(0,NULL,6);
> printf("%d %d\n",err,errno);
> }
>
> I think that it should be an error : Null pointer assignment, like in windows.
> But in practise it is
Here is a simple program.
#include
#include
main(){
int err;
err=read(0,NULL,6);
printf("%d %d\n",err,errno);
}
I think that it should be an error : Null pointer assignment, like in windows.
But in practise it is not so.
Mandrake Linux kernel 2.4.21-0.13mdk
I am a programmer too and i
On Monday 14 March 2005 09:00, Pavel Machek wrote:
> Hi!
>
> > * MySQL (hinders the actual suspension process and kicks the pc back to
> > where it was)
>
> Try this patch...
Works nicely. Thanks.
Jan
--
Most people don't need a great deal of love nearly so much as they need
a steady
On Mon, Mar 14, 2005 at 02:52:00PM +0300, Michael Tokarev wrote:
> After plugging in USB keyboard and loading uhci-hcd and
> usbhid, the keyboard un-freeze, but mouse still didn't
> work. So I tried re-loading psmouse module, and
> surprizingly, mouse started working again, but now dmesg
>
Is whitespace (in any form) allowed in the compatible value?
No. Only printable characters are allowed, that is, byte values
0x21..0x7e and 0xa1..0xfe; each text string is terminated by a
0x00; there can be several text strings concatenated in one
"compatible" property.
Yes, whitespace is used at
--- Andrew Morton <[EMAIL PROTECTED]> wrote:
> moreau francis <[EMAIL PROTECTED]> wrote:
>
> How does this look?
>
It works well though I haven't tested the second
correction. But it looks good...
By the way, is it safe in "n_tty_receive_overrun" to
call
"printk" ? because the former can be
On Thu, 10 Mar 2005, Dave Hansen wrote:
> On Thu, 2005-03-10 at 09:22 -0800, Paul Jackson wrote:
> > In particular, I am working on preparing a patch proposal for a policy
> > that would kill a task rather than invoke the swapper. In
> > mm/page_alloc.c __alloc_pages(), if one gets down to the
On Tue, Mar 15, Benjamin Herrenschmidt wrote:
> what do you chose ? ;)
I'm sure Rusty will prefer the non-whitespace version for depmod and
module.alias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Sun, 2005-03-13 at 16:17 +0100, Segher Boessenkool wrote:
> Sorry to follow up this late...
>
> >>> Is whitespace (in any form) allowed in the compatible value?
>
> No. Only printable characters are allowed, that is, byte values
> 0x21..0x7e and 0xa1..0xfe; each text string is terminated by
> > > See http://download.hennerich.de/kallsyms_20050312_1630.gz
> >
> > Great, just so that there is no confusion, I still need a new run
> > of /proc/page_owner, the shorter time before the lockup the better.
>
> The machine locked up this morning again. See
>
>
Sorry to follow up this late...
Is whitespace (in any form) allowed in the compatible value?
No. Only printable characters are allowed, that is, byte values
0x21..0x7e and 0xa1..0xfe; each text string is terminated by a
0x00; there can be several text strings concatenated in one
"compatible"
On Mon, 14 Mar 2005 13:19:56 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> How much does it interpret the stream in non-transparent mode? Are
> commands also passed through in soft transparent mode?
>
> I'm asking because we might want to implement a passthrough port
> similarly to what the
On Gwe, 2005-03-11 at 21:04, Albert Cahalan wrote:
> > Still insufficient because the device might be hotplugged on you. You
> > need a file handle that has the expected revocation effects on unplug
> > and refcounts
>
> I was under the impression that a file handle would be returned.
Then lets
On Llu, 2005-03-14 at 00:02, Peter Chubb wrote:
> I can see there'd be problems if the code allowed shared interrupts,
> but it doesn't.
If you don't allow shared IRQ's its useless, if you do allow shared
IRQ's it deadlocks. Take your pick 8)
As to your comment about needing to do a few more I/O
Sam Ravnborg wrote:
On Thu, Mar 10, 2005 at 12:12:22PM +, Paulo Marques wrote:
Paulo Marques wrote:
[...]
A simple and robust way is to do the sampling on a list of symbols
sorted by symbol name. This way, even if the symbol positions that are
given to scripts/kallsyms change, the symbols
In article <[EMAIL PROTECTED]> (at Mon, 14 Mar 2005 13:24:24 +), Alan Cox
<[EMAIL PROTECTED]> says:
> 1003.1g both agree with your expectations. The right list is probably
> netdev@oss.sgi.com however.
I've just forwarded this thread to netdev.
--yoshfuji
-
To unsubscribe from this list:
On Gwe, 2005-03-11 at 20:26, Felix Matathias wrote:
> Dear Alan,
>
> I am positive. I can setsockopt, and then, getsockopt returns the value
> that I requested.
Ok I misremembered - its SNDLOWAT that is locked to one in Linux.
> Stevens very clearly states that SO_RCVLOWAT has a direct impact
On Sat, 12 Mar 2005 10:01:43 -0700 (MST), Zwane Mwaikambo
<[EMAIL PROTECTED]> wrote:
> On Wed, 9 Mar 2005, Francesco Oppedisano wrote:
>
> > On Tue, 8 Mar 2005 12:09:58 -0700 (MST), Zwane Mwaikambo
> > <[EMAIL PROTECTED]> wrote:
> >
> > > At some cpu frequency point on i386 the main cause of your
Hello,
Should we hold some lock (like task_lock(tsk)) when test tsk->mm == _mm
or any things else like tsk->mm ==0 ? Suppose it's the final test.
Thanks
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Hi,
i have a pc with five ethernet devices onto and want to resend ethernet packets
coming in from one device to four direct neighbours (distance 1). Therefore i
have installed a packet handler receiving skbs.
Now i have the following questions:
1) is it enough to change the skb->dev to the
On Monday 14 March 2005 08:57, Eric Piel wrote:
> Jan De Luyck a écrit :
> > Hello lists,
> >
> > (please cc me from cpufreq list)
> >
> > I've since yesterday started using the ondemand governor. Seems to work
> > fine, tho I can't seem to find a reason why it keeps scaling my processor
> > speed
Hello,
my brother got ill this weekend, so I'll continue this task:
> > See http://download.hennerich.de/kallsyms_20050312_1630.gz
>
> Great, just so that there is no confusion, I still need a new run
> of /proc/page_owner, the shorter time before the lockup the better.
The machine locked up
On Mon, Mar 14, 2005 at 07:01:23AM -0500, Stephen Evanchik wrote:
> On Mon, 14 Mar 2005 09:19:49 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > > +/*
> > > + * Mode manipulation
> > > + */
> > > +#define TP_SET_SOFT_TRANS (0x4E) /* Set mode */
> > > +#define TP_CANCEL_SOFT_TRANS (0xB9) /*
On Mon, 14 Mar 2005 09:19:49 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote:
> > +/*
> > + * Mode manipulation
> > + */
> > +#define TP_SET_SOFT_TRANS (0x4E) /* Set mode */
> > +#define TP_CANCEL_SOFT_TRANS (0xB9) /* Cancel mode */
> > +#define TP_SET_HARD_TRANS (0x45) /* Mode can only be set */
> EXPORT_SYMBOL_PROTO(getuid);
> +EXPORT_SYMBOL_PROTO(getgid);
please don't. as mentioned in the discussion about ROOT_DEV the whole
code using it is bogus.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
Michael Tokarev wrote:
[]
2.6.10 almost works, but sometimes, the whole input
subsystem just "hungs", ie, both keyboard and mouse
just stops working. Plugging in USB keyboard and
loading usbhid module solves the problem - both
keyboards and the mouse works after that, and I
didn't yet notice the
Export this symbol which is now needed for a typo fix (getuid() -> getgid()).
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
---
linux-2.6.11-paolo/arch/um/os-Linux/user_syms.c |1 +
1 files changed, 1 insertion(+)
diff -puN
Hi,
Few more coding style comments.
On Fri, 11 Mar 2005 11:21:32 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> diff -puN /dev/null drivers/net/chelsio/cxgb2.c
> --- /dev/null 2003-09-15 06:40:47.0 -0700
> +++ 25-akpm/drivers/net/chelsio/cxgb2.c 2005-03-11 11:13:06.0
>
Pass the interface to close as an fd besides that by name... passing it by
name does not work with newer uml_net because that allows to ifconfig down
arbitrary interfaces, while if you have an open fd to the SLIP interface it
means you have full access to it (and thus can close it). Passing only
Export this symbol which is now needed for a typo fix (getuid() -> getgid()).
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
---
linux-2.6.11-paolo/arch/um/os-Linux/user_syms.c |1 +
1 files changed, 1 insertion(+)
diff -puN
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
---
linux-2.6.11-paolo/arch/um/drivers/slip_user.c |6 +-
1 files changed, 5 insertions(+), 1 deletion(-)
diff -puN arch/um/drivers/slip_user.c~uml-uml_net-security-fix
arch/um/drivers/slip_user.c
---
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
---
linux-2.6.11-paolo/arch/um/os-Linux/user_syms.c |1 +
1 files changed, 1 insertion(+)
diff -puN arch/um/os-Linux/user_syms.c~uml-export-getgid-for-hostfs
arch/um/os-Linux/user_syms.c
---
On Mon, Mar 14, 2005 at 08:57:52AM +0100, Eric Piel wrote:
> BTW, DaveJ, Dominik, I couldn't find them in the daily-snapshot
> available at codemonkey.org.uk. Should I worry, or is it just due to
> some latency between your private trees and the public one?
>
This happens those days only when
On Mon, 14 Mar 2005, Steven French wrote:
>
> > Here's the first of two patches with cleanups for fs/cifs/file.c
> The patch looks safe enough but I can not get the patch to apply (pattch
> always claims it is malformed) - whichever email clients I received it
> from probably because of wrap at
Some of my usual coding style comments...
On Fri, 11 Mar 2005 11:21:32 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> diff -puN /dev/null drivers/net/chelsio/osdep.h
> --- /dev/null 2003-09-15 06:40:47.0 -0700
> +++ 25-akpm/drivers/net/chelsio/osdep.h 2005-03-11
Stas Sergeev <[EMAIL PROTECTED]> writes:
Another way of saying the same thing: I absolutely hate seeing
patches that fix some theoretical issue that no Linux apps will ever
care about.
No, it is not theoretical, but it is mainly
about a DOS games and an MS linker, as for
me. The things I'd like
Ingo Molnar wrote:
* Arjan van de Ven <[EMAIL PROTECTED]> wrote:
as I said, since the cacheline just got dirtied, the write is just
half a cycle which is so much in the noise that it really doesn't
matter.
ok - the patch below is a small modification of Hugh's so that we clear
->break_lock
long wrote:
> This patch includes PCIEAER-HOWTO.txt, which describes how the PCI
> Express Advanced Error Reporting Root driver works.
> --- linux-2.6.11-rc5/Documentation/PCIEAER-HOWTO.txt
Could this be placed in a sub-system subdirectory (creating one if
necessary, e.g., pci/)? The root of
Removes some sparse warnings on one-bit bitfields.
Signed-off-by: Peter Hagervall <[EMAIL PROTECTED]>
--
dvb/dvb-core/dvb_ca_en50221.c |6 +++---
video/cx88/cx88.h |4 ++--
video/msp3400.c |4 ++--
video/videocodec.h| 16
4
* Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> as I said, since the cacheline just got dirtied, the write is just
> half a cycle which is so much in the noise that it really doesn't
> matter.
ok - the patch below is a small modification of Hugh's so that we clear
->break_lock unconditionally.
Hi Andi
I tried to read /dev/kmem on x86_64 (linux-2.6.11) and got no success.
read() or pread() returns EINVAL
I tried mmap() too : mmap() calls succeed, but as soon the user process
dereference memory, we get :
tinfo: Corrupted page table at address 2aabf800
PGD 8a983067 PUD c7e5a067 PMD
I noticied a weird problem with input subsystem (mostly
mouse) which happens on my boxes with 2.6.10 and 2.6.11+
kernels (up to current 2.6.11.3), which didn't happen with
earlier kernels.
First issue is that psmouse module takes about 10 sec to
load (to detect the mouse), which was done instantly
On Fri, Mar 11, 2005 at 07:16:45PM +0100, Adrian Bunk wrote:
> I haven't found any modular usage of kmap_{pte,port} on !ppc in the
> kernel.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
>
> ---
>
> This patch was already sent on:
> - 21 Jan 2005
>
> arch/i386/mm/init.c |3 ---
>
On Fri, Mar 11, 2005 at 09:58:39AM +0900, Yoichi Yuasa wrote:
> > > Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]>
> > > Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
> >
> > > @@ -307,7 +308,7 @@ asmlinkage void do_syscall_trace(struct
> > > {
> > > if (unlikely(current->audit_context))
> > Forget to mention, we are checking linux 2.6. It appears to us
> > that mmap doesnt' work for FUSE in linux 2.6.
>
> IIRC, the reason mmap doesn't work on FUSE is because when it
> dirties pages they cannot be flushed reliably, because writing them
> out involves calling a userspace process
Hi,
On Sun, 13 Mar 2005, Matt Mackall wrote:
> I've noticed a few problems with HFS+ support in recent kernels on
> another user's machine running Ubuntu (Warty) running
> 2.6.8.1-3-powerpc. I'm not in a position to extensively test or fix
> either of these problem because of the fs tools
Jake Moilanen writes:
> diff -puN fs/binfmt_elf.c~nx-user-ppc64 fs/binfmt_elf.c
> --- linux-2.6-bk/fs/binfmt_elf.c~nx-user-ppc642005-03-08 16:08:54
> -06:00
> +++ linux-2.6-bk-moilanen/fs/binfmt_elf.c 2005-03-08 16:08:54 -06:00
> @@ -99,6 +99,8 @@ static int set_brk(unsigned long
On Mon, 2005-03-14 at 17:55 +0800, Gordon Jin wrote:
> This patch fixes a corner case in sys_mprotect():
>
> Case: len is so large that will overflow to 0 after page alignment.
shouldn't we just fix the alignment code instead that the overflow case
doesn't align to 0???
that sounds really odd.
On Mon, 14 Mar 2005, Steven Rostedt wrote:
>
> I just downloaded -40 and applied my patch, compiled it with
> PREEMPT_DESKTOP and data=ordered, ran it and everything seems OK, except
> I'm getting the following...
>
> BUG: Unable to handle kernel NULL pointer dereference at virtual address
>
Thomas Richter <[EMAIL PROTECTED]> wrote:
>
>
> Hi Andrew,
>
> > I'm inclined to simply revert that change.
>
> In case the mentioned lines do cause problems, please do not hesitate
> to remove them. As the comments indicate, the patch was completely
> untested as I haven't had the cards
Hi all :)
I don't know if I've had this error previously, I noticed it this
morning when recompiling the kernel *I already use*. When doing 'make
dep' I had this:
make[1]: Leaving directory `/usr/kernel'
scripts/mkdep -- `find /usr/kernel/include/asm /usr/kernel/include/linux
This patch fixes a corner case in sys_mprotect():
Case: len is so large that will overflow to 0 after page alignment.
E.g. len=(size_t)(-1), i.e. 0xff...ff.
Expected result: POSIX spec says it should return -ENOMEM.
Current result: len is aligned to 0, then treated the same as len=0 and
return
Hello,
> Although "sync" doesnt seem to make any difference to fsck output,
> "blockdev --flushbufs" fixes the issue.
>
> Still wondering why the flushing of buffer behavior is different on a
> system with normal harddisk (Redhat 7.2 with 2.4.26 kernel ) as compared
> to a system
Greg Stark <[EMAIL PROTECTED]> wrote:
>
> > Greg Stark <[EMAIL PROTECTED]> writes:
> >
> > > Andrew Morton <[EMAIL PROTECTED]> writes:
> > >
> > > > Are you able to narrow it down to something more fine grained than
> "between
> > > > 2.6.6 and 2.6.9-rc1"?
> > >
> > > Er, I suppose I
moreau francis <[EMAIL PROTECTED]> wrote:
>
> I noticed that TTY is not able to notify overrun issue
> in "n_tty_receive_overrun". Actually it's because of
> "time_before" macro which tests "tty->overrun_time"
> (equals to 0) against "jiffies - HZ" (something very
> big
> after booting).
>
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED],
> > struct dvb_pll_desc {
[ ... ]
> > struct {
[ ... ]
> > } entries[];
> > };
> >
> > while 2.6.11-mm3 changed it into entries[0].
>
> The original code failed to compile with gcc-2.95.4, so I stuck the [0] in
> there, then was vaguely surprised when no warnings
Albert Cahalan wrote:
This is a bad idea. Users should not be allowed to
make this decision. This is rightly a decision for
the admin to make.
Why do you think users should not be allowed to chmod their processes'
/proc directories? Isn't it similar to being able to chmod their home
This patch is from Domen Puncer <[EMAIL PROTECTED]>.
Remove nowhere referenced file. (egrep "filename\." didn't find anything)
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
Acked-by: Stephen Rothwell <[EMAIL PROTECTED]>
Signed-off-by: Paul Mackerras <[EMAIL PROTECTED]>
diff -L
This patch is from Domen Puncer <[EMAIL PROTECTED]>.
Remove nowhere referenced file. (egrep "filename\." didn't find anything)
Signed-off-by: Domen Puncer <[EMAIL PROTECTED]>
Signed-off-by: Paul Mackerras <[EMAIL PROTECTED]>
diff -L arch/ppc64/boot/no_initrd.c -puN
On Mon, 14 Mar 2005, Steven Rostedt wrote:
>
> > > I'll test this with PREEMPT_DESKTOP and data=ordered also and see how it
> > > goes.
> >
> > Does not seem to work at all with the above settings. It seemed OK
> > until I started X. Then every time I launched an xterm it would
> > disappear
Stas Sergeev <[EMAIL PROTECTED]> writes:
>
>> Another way of saying the same thing: I absolutely hate seeing
>> patches that fix some theoretical issue that no Linux apps will ever
>> care about.
> No, it is not theoretical, but it is mainly
> about a DOS games and an MS linker, as for
> me. The
I noticed that TTY is not able to notify overrun issue
in "n_tty_receive_overrun". Actually it's because of
"time_before" macro which tests "tty->overrun_time"
(equals to 0) against "jiffies - HZ" (something very
big
after booting).
I guess a simple way to solve it, is to initialize
Hi,
This issue is quite interesting. We removed all specific VIA quirk
recently and apply a generic VIA quirk. But in this case, the MCH 00:0.0
is from AMD, and the ISA bridge and built-in devices are from VIA, this
means VIA quirk is useless, since it takes action only when the MCH is
from VIA.
Hi Andrew,
> I'm inclined to simply revert that change.
In case the mentioned lines do cause problems, please do not hesitate
to remove them. As the comments indicate, the patch was completely
untested as I haven't had the cards available. However, please ensure
that the parallel port remains
Trivial correction: the type of numbers for Kconfig is not integer but int (I
just verified because I followed the wrong docs and got a error, I looked
elsewhere and they are using int, and int works for me). Please apply.
Signed-off-by: Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
---
Hello,
in the long thread on "[request for inclusion] Realtime LSM" there
doesn't appear to be too many people who has actually tested the
nice-and-rt-prio-rlimits.patch. Well, it works for me...
However, the patch to pam_limits posted here:
http://lkml.org/lkml/2005/1/14/174
is a little bit
> Greg Stark <[EMAIL PROTECTED]> writes:
>
> > Andrew Morton <[EMAIL PROTECTED]> writes:
> >
> > > Are you able to narrow it down to something more fine grained than
> > > "between
> > > 2.6.6 and 2.6.9-rc1"?
> >
> > Er, I suppose I would have to build some more kernels. Ugh. Is there a good
This patch is from Arnd Bergmann <[EMAIL PROTECTED]>.
RTAS is not actually pSeries specific, but some PPC64 code that relies
on RTAS is currently protected by CONFIG_PPC_PSERIES.
This introduces a generic configuration option PPC_RTAS that can be used
by other subarchitectures as well. The
Arjan van de Ven wrote:
Yes that's the tradeoff. I just feel that the former may be better,
especially because the latter can be timing dependant (so you may get
things randomly "happening"), and the former is apparently very low
overhead compared with the cost of taking the lock. Any numbers,
Hi!
> >>I'm fascinated that not a single person picked up on this problem
> >>whilst the agp code sat in -mm. Even if DRI isn't enabled,
> >>every box out there with AGP that uses the generic routines
> >>(which is a majority), should have barfed loudly when it hit
> >>this check during boot.
>
> Yes that's the tradeoff. I just feel that the former may be better,
> especially because the latter can be timing dependant (so you may get
> things randomly "happening"), and the former is apparently very low
> overhead compared with the cost of taking the lock. Any numbers,
> anyone?
as I
On Mon, 14 Mar 2005, Pavel Machek wrote:
I'm fascinated that not a single person picked up on this problem
whilst the agp code sat in -mm. Even if DRI isn't enabled,
every box out there with AGP that uses the generic routines
(which is a majority), should have barfed loudly when it hit
this check
Ingo Molnar wrote:
* Nick Piggin <[EMAIL PROTECTED]> wrote:
while writing the ->break_lock feature i intentionally avoided
overhead in the spinlock fastpath. A better solution for the bug you
noticed is to clear the break_lock flag in places that use
need_lock_break() explicitly.
What happens if
On Mon, Mar 14, 2005 at 12:02:13AM -0500, Stephen Evanchik wrote:
> Here's the latest patch for TracKPoint devices. I have changed the
> sysfs filenames to be more descriptive for commonly used attributes. I
> also implemented the set_properties flag for initialization.
>
> It patches against
On Pá 11-03-05 17:26:14, Dave Jones wrote:
> On Sat, Mar 12, 2005 at 07:18:19AM +0900, OGAWA Hirofumi wrote:
> > Linus Torvalds <[EMAIL PROTECTED]> writes:
> >
> > > Hmm.. We seem to not have any tests for the counts becoming negative, and
> > > this would seem to be an easy mistake to make
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> > while writing the ->break_lock feature i intentionally avoided
> > overhead in the spinlock fastpath. A better solution for the bug you
> > noticed is to clear the break_lock flag in places that use
> > need_lock_break() explicitly.
>
> What happens
This patch is from Arnd Bergmann and Olof Johansson.
This implements the __copy_{to,from}_user_inatomic() functions on ppc64.
The only difference between the inatomic and regular version is that
inatomic does not call might_sleep() to detect possible faults while
holding locks/elevated preempt
Ingo Molnar wrote:
* Hugh Dickins <[EMAIL PROTECTED]> wrote:
@@ -187,6 +187,8 @@ void __lockfunc _##op##_lock(locktype##_
cpu_relax();\
preempt_disable(); \
}
Hi!
> * MySQL (hinders the actual suspension process and kicks the pc back to
> where it was)
Try this patch...
Pavel
--- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100
+++ linux/kernel/signal.c
Jan De Luyck a écrit :
Hello lists,
(please cc me from cpufreq list)
I've since yesterday started using the ondemand governor. Seems to work fine,
tho I can't seem to find a reason why it keeps scaling my processor speed
upwards tho the processor use never exceeds 30% (been watching top -d 1).
Jan De Luyck a écrit :
Hello lists,
(please cc me from cpufreq list)
I've since yesterday started using the ondemand governor. Seems to work fine,
tho I can't seem to find a reason why it keeps scaling my processor speed
upwards tho the processor use never exceeds 30% (been watching top -d 1).
Hi!
* MySQL (hinders the actual suspension process and kicks the pc back to
where it was)
Try this patch...
Pavel
--- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100
+++ linux/kernel/signal.c
Ingo Molnar wrote:
* Hugh Dickins [EMAIL PROTECTED] wrote:
@@ -187,6 +187,8 @@ void __lockfunc _##op##_lock(locktype##_
cpu_relax();\
preempt_disable(); \
}
This patch is from Arnd Bergmann and Olof Johansson.
This implements the __copy_{to,from}_user_inatomic() functions on ppc64.
The only difference between the inatomic and regular version is that
inatomic does not call might_sleep() to detect possible faults while
holding locks/elevated preempt
* Nick Piggin [EMAIL PROTECTED] wrote:
while writing the -break_lock feature i intentionally avoided
overhead in the spinlock fastpath. A better solution for the bug you
noticed is to clear the break_lock flag in places that use
need_lock_break() explicitly.
What happens if break_lock
On Pá 11-03-05 17:26:14, Dave Jones wrote:
On Sat, Mar 12, 2005 at 07:18:19AM +0900, OGAWA Hirofumi wrote:
Linus Torvalds [EMAIL PROTECTED] writes:
Hmm.. We seem to not have any tests for the counts becoming negative, and
this would seem to be an easy mistake to make considering
On Mon, Mar 14, 2005 at 12:02:13AM -0500, Stephen Evanchik wrote:
Here's the latest patch for TracKPoint devices. I have changed the
sysfs filenames to be more descriptive for commonly used attributes. I
also implemented the set_properties flag for initialization.
It patches against 2.6.11
Ingo Molnar wrote:
* Nick Piggin [EMAIL PROTECTED] wrote:
while writing the -break_lock feature i intentionally avoided
overhead in the spinlock fastpath. A better solution for the bug you
noticed is to clear the break_lock flag in places that use
need_lock_break() explicitly.
What happens if
On Mon, 14 Mar 2005, Pavel Machek wrote:
I'm fascinated that not a single person picked up on this problem
whilst the agp code sat in -mm. Even if DRI isn't enabled,
every box out there with AGP that uses the generic routines
(which is a majority), should have barfed loudly when it hit
this check
Yes that's the tradeoff. I just feel that the former may be better,
especially because the latter can be timing dependant (so you may get
things randomly happening), and the former is apparently very low
overhead compared with the cost of taking the lock. Any numbers,
anyone?
as I said,
Hi!
I'm fascinated that not a single person picked up on this problem
whilst the agp code sat in -mm. Even if DRI isn't enabled,
every box out there with AGP that uses the generic routines
(which is a majority), should have barfed loudly when it hit
this check during boot. Does no-one read
Arjan van de Ven wrote:
Yes that's the tradeoff. I just feel that the former may be better,
especially because the latter can be timing dependant (so you may get
things randomly happening), and the former is apparently very low
overhead compared with the cost of taking the lock. Any numbers,
301 - 400 of 771 matches
Mail list logo
