[ANNOUNCE][RFC] PlugSched-6.4 for 2.6.19

Peter Williams wrote: > > This version removes the hard/soft CPU rate caps from the SPA schedulers. > > A patch for 2.6.19 is available at: > > ownload> > > Very Brief Documentation: > > You can select a default scheduler

RE: CPUFREQ-CPUHOTPLUG: Possible circular locking dependency

>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >Gautham R Shenoy >Sent: Thursday, November 30, 2006 3:44 AM >To: Ingo Molnar >Cc: Gautham R Shenoy; [EMAIL PROTECTED]; >linux-kernel@vger.kernel.org; [EMAIL PROTECTED]; >[EMAIL PROTECTED]; [EMAIL

work_struct-induced breakage, part 1 of fsck-knows-how-many

Signed-off-by: Al Viro <[EMAIL PROTECTED]> --- diff --git a/drivers/char/istallion.c b/drivers/char/istallion.c index ffdf9df..bd9195e 100644 --- a/drivers/char/istallion.c +++ b/drivers/char/istallion.c @@ -663,7 +663,7 @@ static int stli_initopen(stlibrd_t *brdp static int

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006, Linus Torvalds wrote: > > and remove the "volatile" from all the bitop accessor functions. It might also be interesting to see if this would change code-size at all. There's a number of things that check different bits in the same word right now, and they just reload the

Re: [PATCH] Fix linux banner utsname information

On Tue, Dec 05, 2006 at 06:24:09PM +0100, Herbert Poetzl wrote: > On Mon, Dec 04, 2006 at 11:32:48PM +0100, Herbert Poetzl wrote: > > > > utsname information is shown in the linux banner, which > > also is used for /proc/version (which can have different > > utsname values inside a uts

[PATCH] powerpc: EEH recovery tweaks (resend)

Paul, Please apply and forward upstream. (Resend of patch from 27 October 2006.) --linas Subject: [PATCH] powerpc: EEH recovery tweaks If one attempts to create a device driver recovery sequence that does not depend on a hard reset of the device, but simply just attempts to resume

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006, Linus Torvalds wrote: > > Sadly, gcc doesn't do it in this case. Still, I'd rather keep the source > clean, and hope that the compiler improves eventually, than to make the > code uglier. Actually, it's our own damn fault. We've long had our arguments "const volatile" to

Re: Display class

> > That patch was rought draft for feedback. I applied your comments. This > > patch actually works. It includes my backlight fix as well. > > Glad to hear it. I had to make the following changes > in order for it to build. > However, I still have build errors for aty. Ug. I see another

Re: Display class

On Wed, 6 Dec 2006 15:10:44 + (GMT) James Simmons wrote: > > > > of Mr. Yu for acpi. Also this class could in time replace the lcd class > > > located in the backlight directory since a lcd is a type of display. > > > The final hope is that the purpose auxdisplay could fall under this > >

[PATCH]: typo in init/initramfs.c

Jean-Paul Saman wrote: > > In populate_rootfs() the printk on line 554. It says "Unpacking > initramfs..", which is confusing because if that line is reached the code > has already decided that the image is an initrd image. Are you sure? > The printk is thus > wrong in stating that it is

Re: Subtleties of __attribute__((packed))

From: Russell King <[EMAIL PROTECTED]> Date: Wed, 6 Dec 2006 17:54:23 + > It does not say "and as such the struct may be aligned to any alignment". Consider the implication for arrays and pointer arithmetic, it's just a logical consequence, that's all. It's why the alignment cannot be

2.6 tmpfs/swap performance oddity

I have this Ubuntu Edgy (HP Proliant DL380 intel x86-64 w/ 4 cores), kernel: 2.6.17-10-server) system with a raid controller (p600 + bbu, cciss) and 8gb memory. The raid disks are setup as one raid1+0 logical device, the swap and filesystem are partitions on this device. I've created a ext3

Re: [PATCH] make sata_promise PATA ports work

On Mon, 4 Dec 2006 12:47:37 -0700, Erik Andersen wrote: >This patch vs 2.6.19, based on the not-actually-working-for-me >code lurking in libata-dev.git#promise-sata-pata, makes the PATA >ports on my promise sata card actually work. Since the plan as >checked into git, is to drive the PATA ports

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006, Jeff Garzik wrote: > > Honestly I wonder if some of these situations really want > "kill_scheduled_work_unless_it_is_already_running_right_now_if_so_wait_for_it" We could do that, and the code to do it would be fairly close to what the "run it" code is. Just replace the

Re: Change x86 prefix order

On Wed, Dec 06, 2006 at 06:52:39PM +0100, Mikael Pettersson wrote: > > If hardware x86 decoders (i.e., Intel or AMD processors) > get measurably faster with the new order, that would be > a good reason to change it. I was told that AMD processors had no preferences and Intel processors preferred

Re: Change x86 prefix order

On Wed, 6 Dec 2006 09:00:30 -0800, H. J. Lu wrote: >On Wed, Dec 06, 2006 at 08:43:17AM -0800, Randy Dunlap wrote: >> On Tue, 5 Dec 2006 23:00:14 -0800 H. J. Lu wrote: >> >> > On x86, the order of prefix SEG_PREFIX, ADDR_PREFIX, DATA_PREFIX and >> > LOCKREP_PREFIX isn't fixed. Currently, gas

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006, Linus Torvalds wrote: > > Gcc should do it for us, afaik. I didn't check, but gcc is generally > pretty good at combining logical operations like this, because it's very > common. Sadly, gcc doesn't do it in this case. Still, I'd rather keep the source clean, and hope

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006, David Howells wrote: > > + if (get_wq_data(work) == cwq > + && test_bit(WORK_STRUCT_PENDING, >management) > > I wonder if those can be combined, perhaps: Gcc should do it for us, afaik. I didn't check, but gcc is generally pretty good at combining logical

[PATCH] WorkStruct: Implement generic UP cmpxchg() where an arch doesn't support it [try #2]

Implement generic UP cmpxchg() where an arch doesn't otherwise support it. This assuming that the arch doesn't have support SMP without providing its own cmpxchg() implementation. This is required because cmpxchg() is used by the reduced work queue patches to adjust the management data in a

Re: Subtleties of __attribute__((packed))

On Wed, Dec 06, 2006 at 04:54:39PM +0100, Jan Blunck wrote: > Maybe the arm backend is somehow broken. AFAIK (and I verfied it on S390 and > i386) the alignment shouldn't change. Please read the info pages: `packed' This attribute, attached to an `enum', `struct', or `union' type

Re: [PATCH] Export current_is_keventd() for libphy

Linus Torvalds <[EMAIL PROTECTED]> wrote: > test_bit() with a constant number is done very much in C, and very much on > purpose. _Exactly_ to allow the compiler to combine these kinds of things. Ah... I've read that several times, and each time I've assumed it's referring to *addr not nr as

Re: [PATCH] Export current_is_keventd() for libphy

Honestly I wonder if some of these situations really want "kill_scheduled_work_unless_it_is_already_running_right_now_if_so_wait_for_it" Since its during shutdown, usually the task just wants to know that the code in the workqueue won't be touching the hardware or data structures after

Re: PMTMR running too fast

> > > Is there a specific reason the check was removed (I couldn't see on in > > the archives) or was it simply overlooked? Without it I need to pass > > clocksource=tsc to have 2.6.18 work correctly on an older K6 system with > > an Aladdin chipset (will dig out the precise details if

Re: [PATCH] more sanity checks in Dwarf2 unwinder

On Monday 04 December 2006 17:20, Jan Beulich wrote: > >Would it be possible to add printks for the EIOs? We want to know > >when dwarf2 is corrupted. > > Here's a patch to do this and some more (applies on firstfloor tree, but > probably not on plain 2.6.19). Added thanks I added

Re: [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support.

On Tuesday 05 December 2006 12:01, Eric W. Biederman wrote: > > Ok due to popular demands here is the slightly fixed patch that works > on both i386 and x86_64. For the i386 version you must not have > HIGHMEM64G enabled. > > I just rolled it all into one patch as I'm to lazy to transmit all >

Re: [PATCH] Export current_is_keventd() for libphy

Linus Torvalds <[EMAIL PROTECTED]> wrote: > How about something like this? At first glance, this looks reasonable. It also looks like it should be used to replace a lot of the cancel_delayed_work() calls that attempt to cancel _undelayed_ work items. That would allow a number of work items to

Re: [PATCH 26/35] Unionfs: Privileged operations workqueue

On Tue, Dec 05, 2006 at 02:50:13PM -0500, Josef Sipek wrote: > On Tue, Dec 05, 2006 at 08:27:51PM +0100, Jan Engelhardt wrote: > > > > On Dec 4 2006 07:30, Josef 'Jeff' Sipek wrote: > > >+#include "union.h" > > >+ > > >+struct workqueue_struct *sioq; > > >+ > > >+int __init init_sioq(void) > > >

Re: [PATCH] Add __GFP_MOVABLE for callers to flag allocations that may be migrated

On Wed, 6 Dec 2006, Mel Gorman wrote: > Objective: Get contiguous block of free pages > Required: Pages that can move > Move means: Migrating them or reclaiming > How we do it for high-order allocations: Take a page from the LRU, move > the pages within that high-order block > How we do it

Re: Subtleties of __attribute__((packed))

Jan Blunck <[EMAIL PROTECTED]> writes: > Well, right ... and where do you see a structure of packed members? Read . Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg,

Re: [PATCH] WorkStruct: Implement generic UP cmpxchg() where an arch doesn't support it

On Wed, 6 Dec 2006, David Howells wrote: > > Implement generic UP cmpxchg() where an arch doesn't otherwise support it. > This assuming that the arch doesn't have support SMP without providing its own > cmpxchg() implementation. This is too ugly to live. At least the kernel/workqueue.c part.

Re: [PATCH] VIA and SiS AGP chipsets are x86-only

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Herrenschmidt wrote: > On Tue, 2006-12-05 at 20:40 -0700, Matthew Wilcox wrote: >> On Tue, Dec 05, 2006 at 02:56:41PM -0800, Ian Romanick wrote: >>> I don't know about SiS, but this is certainly *not* true for Via. There >>> are some PowerPC

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006, Andrew Morton wrote: > > I think so too. But it would be imprudent to hang around waiting for me > to write it :( How about something like this? This (a) depends on the just-merged "struct work" cleanup (b) is totally untested (c) probably kills you slowly and

[PATCH 4/4] lumpy take the other active inactive pages in the area

lumpy: take the other active/inactive pages in the area When we scan an order N aligned area around our tag page take any other pages with a matching active state to that of the tag page. This will tend to demote areas of the order we are interested from the active list to the inactive list and

[PATCH 1/4] lumpy reclaim v2

lumpy reclaim v2 When trying to reclaim pages for a higher order allocation, make reclaim try to move lumps of pages (fitting the requested order) about, instead of single pages. This should significantly reduce the number of reclaimed pages for higher order allocations. Signed-off-by: Peter

Re: -mm merge plans for 2.6.20

* Roman Zippel <[EMAIL PROTECTED]> wrote: > > It cannot be had both ways: either we stay simpler and less > > intrusive, or we go more generic but more intrusive. > > You miss the point, I don't care how intrusive this is, [...] we do care about how intrusive this is. I guess we'll have to

Re: -mm merge plans for 2.6.20

* Roman Zippel <[EMAIL PROTECTED]> wrote: > > > > > [...] one obvious user would be the scheduler, [...] > > > > but that is not a refutation of what Thomas said, at all. You say > > that the scheduler /could/ use such a facility. What Thomas said was > > that /there are no current users of

[PATCH 0/4] Lumpy Reclaim V3

This is a repost of the lumpy reclaim patch set. This is basically unchanged from the last post, other than being rebased to 2.6.19-rc2-mm2. This has passed basic stress testing on a range of machines here. [Sorry for the delay reposting, I had a test failure and needed to confirm it was not

Areca driver 2.6.19 on x86_64

We have a problem with the new areca driver included in kernel tree 2.6.19.   During the boot sequence we get this output:   Loading arcmsr.ko module ACPI: PCI Interrupt :05:0e.0[A] -> Link [LINKC] -> GSI 5 (level, low) -> IRQ 5 ARECA RAID ADAPTER0: FIRMWARE VERSION

Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64

Kasper Sandberg <[EMAIL PROTECTED]> wrote: > > What do you mean by "hardlock"? Do you mean the application has to be > > killed, > > or do you mean the kernel is stuck and the machine has to be rebooted? > i mean the kernel itself, two of the times it has happened to me, magic > sysrq havent

[PATCH 3/4] lumpy ensure we respect zone boundaries

lumpy: ensure we respect zone boundaries When scanning an aligned order N area ensure we only pull out pages in the same zone as our tag page, else we will manipulate those pages' LRU under the wrong zone lru_lock. Bad. Signed-off-by: Andy Whitcroft <[EMAIL PROTECTED]> Acked-by: Peter Zijlstra

[GIT] Please pull the NFS client update for 2.6.19

Hi Linus, Please pull from the repository at git pull git://git.linux-nfs.org/pub/linux/nfs-2.6.git This will update the following files through the appended changesets. The individual patches can also be viewed on the web at http://client.linux-nfs.org/Linux-2.6.x/2.6.19/ Cheers,

Re: Change x86 prefix order

On Wed, Dec 06, 2006 at 08:43:17AM -0800, Randy Dunlap wrote: > On Tue, 5 Dec 2006 23:00:14 -0800 H. J. Lu wrote: > > > On x86, the order of prefix SEG_PREFIX, ADDR_PREFIX, DATA_PREFIX and > > LOCKREP_PREFIX isn't fixed. Currently, gas generates > > > > LOCKREP_PREFIX ADDR_PREFIX DATA_PREFIX

[PATCH 2/4] lumpy cleanup a missplaced comment and simplify some code

lumpy: cleanup a missplaced comment and simplify some code Move the comment for isolate_lru_pages() back to its function and comment the new function. Add some running commentry on the area scan. Cleanup the indentation on switch to match the majority view in mm/*. Finally, clarify the

RFC [PATCH] 1/2 disable initramfs

The file init/initramfs.c is always compiled and linked in the kernel vmlinux even when BLK_DEV_RAM and BLK_DEV_INITRD are disabled and the system isn't using any form of an initramfs or initrd. In this situation the code is only used to unpack a (static) default initial rootfilesystem. The

Re: Change x86 prefix order

On Tue, 5 Dec 2006 23:00:14 -0800 H. J. Lu wrote: > On x86, the order of prefix SEG_PREFIX, ADDR_PREFIX, DATA_PREFIX and > LOCKREP_PREFIX isn't fixed. Currently, gas generates > > LOCKREP_PREFIX ADDR_PREFIX DATA_PREFIX SEG_PREFIX > > I will check in a patch: > >

Re: -mm merge plans for 2.6.20

Hi, On Wed, 6 Dec 2006, Ingo Molnar wrote: > > > > > If I understand it correctly, Roman wants clockevents to be usable > > > > > for other things aside hrtimer/dyntick, i.e. let other code request > > > > > unused timer event hardware for special purposes. I thought about > > > > > that in

[PATCH] WorkStruct: Implement generic UP cmpxchg() where an arch doesn't support it

From: David Howells <[EMAIL PROTECTED]> Implement generic UP cmpxchg() where an arch doesn't otherwise support it. This assuming that the arch doesn't have support SMP without providing its own cmpxchg() implementation. This is required because cmpxchg() is used by the reduced work queue patches

RFC [PATCH] 2/2 disable initramfs

Update all arch/*/kernel/vmlinux.lds.S to not include space for initramfs when CONFIG_BLK_DEV_INITRAMFS is not selected. This saves another 4 kbytes on most platfoms. Some platforms reserve PAGE_SIZE for initramfs. The patch is compiled and tested on mips (PNX8535) and arm

Re: Linux should define ENOTSUP

Samuel Thibault wrote: H. Peter Anvin, le Wed 06 Dec 2006 07:35:49 -0800, a écrit : Samuel Thibault wrote: The two can't be done at the same time. In fact, the two probably can't be done without a period of quite a few *years* between them. Not a reason for not doing it ;) No, but breakage

Re: Subtleties of __attribute__((packed))

On Wed, Dec 06, Andreas Schwab wrote: > Jan Blunck <[EMAIL PROTECTED]> writes: > > > Maybe the arm backend is somehow broken. > > A packed structure is something quite different than a structure of packed > members. > Well, right ... and where do you see a structure of packed members?

Re: [PATCH 0/3] New firewire stack

Geert Uytterhoeven wrote: > On Tue, 5 Dec 2006, Marcel Holtmann wrote: >> I personally would go with >> "ieee1394", because that is the official name for it. Otherwise go with >> "firewire" if you wanna separate yourself from the previous stack. > > Which still leaves the opportunity for having a

Re: Subtleties of __attribute__((packed))

On Wed, Dec 06, Phil Endecott wrote: > > To see a difference with your example structs you need to compare these two: > > struct wibble1 { > char c; > struct bar1 b1; > }; > > struct wibble2 { > char c; > struct bar2 b2; > }; > > struct wibble1 w1 = { 1, { 2, {3,4,5} } }; > struct

Re: [PATCH 0/3] New firewire stack

On Tue, 5 Dec 2006, Marcel Holtmann wrote: > the only problem are public and exported interfaces and function. For > static code you can use whatever you want. I personally would go with > "ieee1394", because that is the official name for it. Otherwise go with > "firewire" if you wanna separate

Re: sparse errors in srcu.h

On Wed, Dec 06, 2006 at 10:50:14AM +0100, Brice Goglin wrote: > Hi, > > When running sparse checks on a file that ends up including srcu.h, we > get the following warnings: > > include/linux/srcu.h:52:44: error: undefined identifier 'sp' > include/linux/srcu.h:52:44: error: bad constant

Re: Linux should define ENOTSUP

H. Peter Anvin, le Wed 06 Dec 2006 07:35:49 -0800, a écrit : > Samuel Thibault wrote: > >>The two can't be done at the same time. In fact, the two probably can't > >>be done without a period of quite a few *years* between them. > > > >Not a reason for not doing it ;) > > No, but breakage is.

Re: 2.6.16.32 stuck in generic_file_aio_write()

> > Done some more digging : isn't http://lkml.org/lkml/2006/10/13/139 somehow > > related ? I do see pagefaults, and inode locks and mmap_locks. > > > > I thought it was, but from my look through yout 8-billion-task backtrace, > no task was stuck in D-state with the appropriate call trace. >

Re: [PATCH]: cpu hotplug locking fix

On Wed, 6 Dec 2006 11:04:29 -0500 Prarit Bhargava <[EMAIL PROTECTED]> wrote: > --- linux-2.6.18.ia64/kernel/cpu.c.orig 2006-10-31 10:57:37.0 > -0500 > +++ linux-2.6.18.ia64/kernel/cpu.c2006-10-31 10:57:46.0 -0500 > @@ -58,8 +58,8 @@ void unlock_cpu_hotplug(void) >

Re: Subtleties of __attribute__((packed))

Jan Blunk wrote: Maybe the arm backend is somehow broken. AFAIK (and I verfied it on S390 and i386) the alignment shouldn't change. To see a difference with your example structs you need to compare these two: struct wibble1 { char c; struct bar1 b1; }; struct wibble2 { char c; struct

Re: BUG? atleast >=2.6.19-rc5, x86 chroot on x86_64

On Wed, 2006-12-06 at 13:08 +, David Howells wrote: > Kasper Sandberg <[EMAIL PROTECTED]> wrote: > > > and i am very very sure its because of this, i can run with the kernel > > (atleast with rc5 i had that long) for 10 days, and then chroot in, run > > the 32bit apps, and within hours of

Re: Subtleties of __attribute__((packed))

Jan Blunck <[EMAIL PROTECTED]> writes: > Maybe the arm backend is somehow broken. A packed structure is something quite different than a structure of packed members. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP

Re: Infinite retries reading the partition table

On Tue, 2006-12-05 at 21:08 -0800, Andrew Morton wrote: > case MEDIUM_ERROR: > + if (sshdr.asc == 0x11 || /* UNRECOVERED READ ERR */ > + sshdr.asc == 0x13 || /* AMNF DATA FIELD */ > + sshdr.asc == 0x14) { /* RECORD NOT FOUND */ > +

Re: [PATCH] Export current_is_keventd() for libphy

On Wed, 6 Dec 2006 15:25:22 + (GMT) "Maciej W. Rozycki" <[EMAIL PROTECTED]> wrote: > > Maybe the lesson here is that flush_scheduled_work() is a bad function. > > It should really be flush_this_work(struct work_struct *w). That is in > > fact what approximately 100% of the

Re: [PATCH -rt 0/3] Make trace_freerunning work; Take 2

* Karsten Wiese <[EMAIL PROTECTED]> wrote: > Following 3 patches try to implement the above. > > Tested on a UP only after this incantation: > echo 0 > /proc/sys/kernel/wakeup_timing > echo 1 > /proc/sys/kernel/trace_enabled > echo 1 > /proc/sys/kernel/trace_user_triggered >

Re: Subtleties of __attribute__((packed))

On Wed, Dec 06, Phil Endecott wrote: > I don't think so. Example: > > struct test { > int a __attribute__((packed)); > int b __attribute__((packed)); > }; > > char c = 1; > struct test t = { .a=2, .b=3 }; > > $ arm-linux-gnu-gcc -O2 -S -W -Wall test1.c > > .file "test2.c" >

Re: 2.6.16.32 stuck in generic_file_aio_write()

On Wed, 6 Dec 2006 16:17:10 +0100 (CET) Igmar Palsenberg <[EMAIL PROTECTED]> wrote: > > > > It's rather large, but for those who want to look at it : > > > http://www.jdi-ict.nl/plain/serial-28112006.txt > > > > The same problem, this time with 2.6.19. I've done a show tasks, a show > >

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On Wed, 6 Dec 2006, Dmitry Torokhov wrote: > If Greg is OK with that I would start with truly mechanical merge (no > now data structures, just move the files around) and merge this ASAP, > before we hit -rc1 or -rc2 at the latest. Then you can start puling up > your changesin the separate git

Re: [PATCH] acpi: add backlight support to the sony_acpi driver (v2)

Its nice to see acpi moving to the backlight api. Will acpi also move to hwmon and led class support ? On Sat, 2 Dec 2006, Pavel Machek wrote: > Hi! > > > > Looks okay to me. We really want unified interface for backlight. > > > > Then I request some help to get > >

Re: Linux should define ENOTSUP

Samuel Thibault wrote: H. Peter Anvin, le Wed 06 Dec 2006 07:16:39 -0800, a écrit : Arjan van de Ven wrote: Is there any way to fix this? Glibc people don't seem to want to fix it on their part, see http://sources.redhat.com/bugzilla/show_bug.cgi?id=2363 Hi, Ulrich asked you to go to us

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On 12/6/06, Jiri Kosina <[EMAIL PROTECTED]> wrote: On Wed, 6 Dec 2006, Dmitry Torokhov wrote: > Is there any reason why we can't mecanically move everything into > drivers/hid right now? Then Greg could simply forward all patches he > gets for HID your way and you won't have hard time merging

[PATCH -rt 3/3] Make trace_freerunning work; Take 2: change reset_trace_idx()

Move atomic_set(>underrun, 0) and atomic_set(>overrun, 0) occurrences into reset_trace_idx(). Note this leads to under/overrun being reset more often than before: - in the trace_all_cpus case. - from under check_critical_timing() Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]>

Re: Linux should define ENOTSUP

H. Peter Anvin, le Wed 06 Dec 2006 07:26:44 -0800, a écrit : > Samuel Thibault wrote: > >H. Peter Anvin, le Wed 06 Dec 2006 07:16:39 -0800, a écrit : > >>Arjan van de Ven wrote: > Is there any way to fix this? Glibc people don't seem to want to fix it > on their part, see >

Re: [LinuxBIOS] [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support.

What do you mean by + for (reps = 0; reps >= 0; reps++) { ? If you will not reps is negative. Roughly it is a loop that will timeout eventually if a usb debug cable is not present. So since I didn't know how many loop iterations made sense I allowed it to loop for 2^31 times or until

Re: Linux should define ENOTSUP

Samuel Thibault wrote: The two can't be done at the same time. In fact, the two probably can't be done without a period of quite a few *years* between them. Not a reason for not doing it ;) No, but breakage is. There has to be a major benefit to justify the cost, and you, at least, have

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

Hi Jiri, > This would be nice to merge, if noone has any major objections, and do > other development on top of that. > I am currently trying to set up an account and git tree for this at > kernel.org ... request sent, waiting for reply :) I can setup a tree for the merge. You simply have to

Re: [PATCH] Export current_is_keventd() for libphy

On Tue, 5 Dec 2006, Andrew Morton wrote: > But running flush_scheduled_work() from within dev_close() is a very > sensible thing to do, and dev_close is called under rtnl_lock(). > davem is -> thattaway ;) And when within dev_close() there is quite a chance there is linkwatch_event() somewhere

Re: Linux should define ENOTSUP

H. Peter Anvin, le Wed 06 Dec 2006 07:16:39 -0800, a écrit : > Arjan van de Ven wrote: > >>Is there any way to fix this? Glibc people don't seem to want to fix it > >>on their part, see > >>http://sources.redhat.com/bugzilla/show_bug.cgi?id=2363 > > > >Hi, > > > >Ulrich asked you to go to us once

Re: Linux should define ENOTSUP

Arjan van de Ven wrote: Is there any way to fix this? Glibc people don't seem to want to fix it on their part, see http://sources.redhat.com/bugzilla/show_bug.cgi?id=2363 Hi, Ulrich asked you to go to us once your time travel machine was finished.. is it finished yet ? ;=) this is part of

[PATCH -rt 2/3] Make trace_freerunning work; Take 2: Add atomic_t underrun

Add atomic_t underrun to struct cpu_trace. Increment it only when trace_freerunning is set and an older trace entry is overwritten. Modify copy_trace() to reorder entries, if underrun != 0. Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]> --- rt6-kw/kernel/latency_trace-tk2.1.c 2006-12-06

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On Wed, 6 Dec 2006, Dmitry Torokhov wrote: > > I guess that this paragraph wasn't for me, but rather for the author of > > the HID Simple Driver proposal, am I right? > Yes, mainly for him but also for you because we need to be able to do > what Li Yu is trying to do and be able to tweak HID

Re: Linux should define ENOTSUP

Samuel Thibault wrote: this is part of the ABI, so we can't change this in 2006... Ok, so Linux will never be fully posix compliant. That's largely already the case, mostly because there is unfortunately still a fair bit of rubber-stamping Solaris going on. -hpa - To

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

Hi Dmitry, > > > > I still have the same objection - the "simple'" code will have to be > > > > compiled into the driver instead of being a separate module and > > > > eventyally will lead to a monster-size HID module. We have this issue > > > > with psmouse to a degree but with HID the growth

Re: Subtleties of __attribute__((packed))

Jan Blunck wrote: On 12/6/06, Phil Endecott <[EMAIL PROTECTED]> wrote: I used to think that this: struct foo { int a __attribute__((packed)); char b __attribute__((packed)); ... more fields, all packed ... }; was exactly the same as this: struct foo { int a; char b; ...

Re: [RFC] rfkill - Add support for input key to control wireless radio

On 12/6/06, Dan Williams <[EMAIL PROTECTED]> wrote: On Wed, 2006-12-06 at 09:37 -0500, Dmitry Torokhov wrote: > > Fans of the 3rd method, speak up ;) I think I brought up the 3rd method initially in this thread. I'm not necessarily advocating it, but I wanted to be sure people realized that

Re: 2.6.16.32 stuck in generic_file_aio_write()

> > It's rather large, but for those who want to look at it : > > http://www.jdi-ict.nl/plain/serial-28112006.txt > > The same problem, this time with 2.6.19. I've done a show tasks, a show > locks, a show regs, and after that, a sync + reboot :) > > Log is at

Re: -mm merge plans for 2.6.20

* Roman Zippel <[EMAIL PROTECTED]> wrote: > > > > If I understand it correctly, Roman wants clockevents to be usable > > > > for other things aside hrtimer/dyntick, i.e. let other code request > > > > unused timer event hardware for special purposes. I thought about > > > > that in the

Re: [RFC] rfkill - Add support for input key to control wireless radio

On Wed, 2006-12-06 at 09:37 -0500, Dmitry Torokhov wrote: > On 12/4/06, Ivo van Doorn <[EMAIL PROTECTED]> wrote: > > > I am still not sure that tight coupling of input device with rfkill > > > structure is such a good idea. Quite often the button is separated > > > from the device itself and radio

Re: Display class

> > of Mr. Yu for acpi. Also this class could in time replace the lcd class > > located in the backlight directory since a lcd is a type of display. > > The final hope is that the purpose auxdisplay could fall under this > > catergory. > > > > P.S > >I know the edid parsing would have to

Re: [PATCH] let WARN_ON() output the condition

On Wed, 6 Dec 2006, Jaswinder Singh wrote: > I am playing with linux kernel but kernel dumps on WARN_ON , when I > commented WARN_ON in my code my kernel starts working but I get two > sideeffects :- Hi, please, submit a proper bugreport, including all the needed data (see REPORTING-BUGS

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On 12/6/06, Jiri Kosina <[EMAIL PROTECTED]> wrote: On Wed, 6 Dec 2006, Marcel Holtmann wrote: > > I still have the same objection - the "simple'" code will have to be > > compiled into the driver instead of being a separate module and > > eventyally will lead to a monster-size HID module. We

[PATCH -rt 0/3] Make trace_freerunning work; Take 2

Am Dienstag, 5. Dezember 2006 23:10 schrieb Ingo Molnar: > > freerunning should behave the same way with regard to latency > measurement. I.e. report_latency() is still needed, and the kernel will > thus do a maximum search over all traces triggered via start/stop. > > the difference is in the

[PATCH -rt 1/3] Make trace_freerunning work; Take 2: Off by 1 tweaks

Needed to make last trace entry appear when trace_freerunning is 1. Signed-off-by: Karsten Wiese <[EMAIL PROTECTED]> --- rt6/kernel/latency_trace.c 2006-12-06 00:36:49.0 +0100 +++ rt6-kw/kernel/latency_trace.c 2006-12-06 14:43:52.0 +0100 @@ -181,7 +181,7 @@ static int

Re: Subtleties of __attribute__((packed))

On 12/6/06, Phil Endecott <[EMAIL PROTECTED]> wrote: Dear All, I used to think that this: struct foo { int a __attribute__((packed)); char b __attribute__((packed)); ... more fields, all packed ... }; was exactly the same as this: struct foo { int a; char b; ... more

GIT pull on work_struct reduction tree

Hi Linus, I've brought the work_struct reduction patches up to date once again. David --- The following changes since commit ec0bf39a471bf6fcd01def2bd677128cea940b73: Linus Torvalds: Merge master.kernel.org:/.../jejb/scsi-misc-2.6 are found in the git repository at:

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

Hi Dmitry, > > > I still have the same objection - the "simple'" code will have to be > > > compiled into the driver instead of being a separate module and > > > eventyally will lead to a monster-size HID module. We have this issue > > > with psmouse to a degree but with HID the growth potential

Re: can't boot : Spurious ACK with kernel 2.6.19

On 12/6/06, Alan J. Wylie <[EMAIL PROTECTED]> wrote: On Wed, 06 Dec 2006 00:00:13 +0100, Bernd Prager <[EMAIL PROTECTED]> said: > I'm trying to upgrade to kernel 1.6.19. The boot process immediatly > locks in a loop with the message: "atkbd.c: Spurious ACK on > isa0060/serio0. Some program

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

Hi Marcel, On 12/6/06, Marcel Holtmann <[EMAIL PROTECTED]> wrote: Hi Dmitry, > > > 1. Make hidinput_disconnect_core() be more robust, it can not > > > break anything even failed to allocate device struct. > > > 2. Thanks new input device driver API, we need not the extra

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

On Wed, 6 Dec 2006, Marcel Holtmann wrote: > > I still have the same objection - the "simple'" code will have to be > > compiled into the driver instead of being a separate module and > > eventyally will lead to a monster-size HID module. We have this issue > > with psmouse to a degree but with

Re: [PATCH 0/3] New firewire stack

On Wed, 2006-12-06 at 09:56 +0100, Stefan Richter wrote: > (Adding Cc: linux1394-devel) > > Ben Collins wrote at linux-kernel: > > On Tue, 2006-12-05 at 18:21 -0500, Kristian Høgsberg wrote: > >> Alexey Dobriyan wrote: > >>> On Tue, Dec 05, 2006 at 12:22:29AM -0500, Kristian Høgsberg wrote: >

Re: -mm merge plans for 2.6.20

> > Right back from exams and with lots of spare time :) > > I got your patch, so I'm going to try your patch and exchange all the > "platform_device_*" stuff with your display class and move ks0108, > cfag12864b and cfag12864bfb to drivers/video/display/ Thanks. I will post a new patch soon.

Re: [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)

Hi Dmitry, > > > 1. Make hidinput_disconnect_core() be more robust, it can not > > > break anything even failed to allocate device struct. > > > 2. Thanks new input device driver API, we need not the extra code > > > for support force-feed device yet, so say bye to >

<    1   2   3   4   5   6   7   8   >