Re: When to use threaded interrupts?

Kosta, Just a wild assumption: maybe the cost of incurring context switches ? (comparing to tasklets) Best Regards, Rami Rosen http://ramirose.wix.com/ramirosen On 10 September 2015 at 20:49, Kosta Zertsekel wrote: > Hi guys, > > I hope I'm on right mailing list. :-) > I think I get the pro o

When to use threaded interrupts?

Hi guys, I hope I'm on right mailing list. :-) I think I get the pro of using threaded interrupts - to decrease the maximum interrupt latency on RT workloads and/or RT machines (servers, embedded, etc.). Also, I see that in 4.2 there are only ~76 drivers that use threaded interrupt: ``` $ git gre

Re: Set the ACPI=on on the cmdline, and the OS can not boot.

On Thu, 10 Sep 2015 17:41:51 +0800, tianlilai said: > When I set the ACPI=on on the cmdline,and the OS can not boot(If set > ACPI=off, The system is OK). The attachmemt file is the booting log. Would > help me slove this ploblem? Thanks very much. > Note:kernel version v2.6.18,and the arch i

Set the ACPI=on on the cmdline, and the OS can not boot.

Hi,Everyone,I have a problem as follow: When I set the ACPI=on on the cmdline,and the OS can not boot(If set ACPI=off, The system is OK). The attachmemt file is the booting log. Would help me slove this ploblem? Thanks very much. Note:kernel version v2.6.18,and the arch is x86_64. Rega

Re: Use a variable before it's declaration

> Sure. That's a completely different issue. But this works: > > extern int b; > int *a = &b; > int b = 20; > > int main(void) > { > return 0; > } > > and that's what the code you refer do does. Yes, that make sense, thanks very much :-) -- Rock Lee ___

Re: Use a variable before it's declaration

On 2015/9/10 15:55, valdis.kletni...@vt.edu wrote: > On Thu, 10 Sep 2015 15:09:42 +0800, Rock Lee said: > >> union thread_union init_thread_union __init_task_data = >> >> { INIT_THREAD_INFO(init_task) }; > > 'gcc -E' to see what this expands to. All may not be as it seems. :) > Thanks, I us

Re: Use a variable before it's declaration

Rock Lee writes: >> Rock Lee writes: >> >>> Hi, all: >>> Here is a snippet of linux-v3.4 which drives me crazy. >>> Because init_task hasn't been declared yet when init_thread_union is >>> initializing. Why is there no compiling error? Any hint would be helpful. >>> >>> union thread_union in

Re: Use a variable before it's declaration

> Rock Lee writes: > >> Hi, all: >> Here is a snippet of linux-v3.4 which drives me crazy. >> Because init_task hasn't been declared yet when init_thread_union is >> initializing. Why is there no compiling error? Any hint would be helpful. >> >> union thread_union init_thread_union __init_tas

Re: Use a variable before it's declaration

Rock Lee writes: > Hi, all: > Here is a snippet of linux-v3.4 which drives me crazy. > Because init_task hasn't been declared yet when init_thread_union is > initializing. Why is there no compiling error? Any hint would be helpful. > > union thread_union init_thread_union __init_task_data

Re: Use a variable before it's declaration

On Thu, 10 Sep 2015 15:09:42 +0800, Rock Lee said: > union thread_union init_thread_union __init_task_data = > > { INIT_THREAD_INFO(init_task) }; 'gcc -E' to see what this expands to. All may not be as it seems. :) pgpbElrwkwUP7.pgp Description: PGP signature _

Use a variable before it's declaration

Hi, all: Here is a snippet of linux-v3.4 which drives me crazy. Because init_task hasn't been declared yet when init_thread_union is initializing. Why is there no compiling error? Any hint would be helpful. union thread_union init_thread_union __init_task_data = { INIT_THREAD_INFO(