* [ANNOUNCE] 2.6.33-rc8-rt2 @ 2010-02-24 16:52 Thomas Gleixner 2010-02-24 22:38 ` Peter Zijlstra ` (2 more replies) 0 siblings, 3 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-02-24 16:52 UTC (permalink / raw) To: LKML Cc: rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde We are pleased to announce the next update to our new preempt-rt series. - Update to linus latest - Fixes all over the place for the merge fallout - KVM fix from Jan - perf fix from Peter - tracer fixes from Carsten Known issues: - the highmem problem which Fernando reported with i915 on 32bit i386 is not yet solved. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33-rc8-rt2 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.tar.bz2 http://www.kernel.org/pub/linux/kernel/v2.6/testing/patch-2.6.33-rc8.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rc8-rt2.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rc8-rt2 2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner @ 2010-02-24 22:38 ` Peter Zijlstra 2010-02-25 22:56 ` Peter Zijlstra 2010-02-26 19:44 ` Dan Carpenter 2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner 2 siblings, 1 reply; 54+ messages in thread From: Peter Zijlstra @ 2010-02-24 22:38 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Steven Rostedt, Clark Williams, nando, Carsten Emde On Wed, 2010-02-24 at 17:52 +0100, Thomas Gleixner wrote: > > - the highmem problem which Fernando reported with i915 on 32bit > i386 is not yet solved. The below compiles and boots a i386 defconfig kernel in kvm, I don't have a system with 32bit userspace and i915 handy further test this. --- arch/x86/include/asm/highmem.h | 9 ++- arch/x86/mm/highmem_32.c | 27 +++++--- arch/x86/mm/iomap_32.c | 17 ----- mm/highmem.c | 151 +++++++++++++++++++++++++++------------ 4 files changed, 128 insertions(+), 76 deletions(-) diff --git a/arch/x86/include/asm/highmem.h b/arch/x86/include/asm/highmem.h index 433ae1f..8279657 100644 --- a/arch/x86/include/asm/highmem.h +++ b/arch/x86/include/asm/highmem.h @@ -55,14 +55,17 @@ extern unsigned long highstart_pfn, highend_pfn; #define PKMAP_ADDR(nr) (PKMAP_BASE + ((nr) << PAGE_SHIFT)) extern void *kmap_high(struct page *page); +extern void *kmap_pfn_prot(unsigned long pfn, pgprot_t prot); extern void kunmap_high(struct page *page); void *kmap(struct page *page); +void *kmap_page_prot(struct page *page, pgprot_t prot); extern void kunmap_virt(void *ptr); extern struct page *kmap_to_page(void *ptr); void kunmap(struct page *page); void *__kmap_atomic_prot(struct page *page, enum km_type type, pgprot_t prot); +void *__kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type, pgprot_t prot); void *__kmap_atomic(struct page *page, enum km_type type); void *__kmap_atomic_direct(struct page *page, enum km_type type); void __kunmap_atomic(void *kvaddr, enum km_type type); @@ -85,15 +88,17 @@ extern void add_highpages_with_active_regions(int nid, unsigned long start_pfn, * on PREEMPT_RT kmap_atomic() is a wrapper that uses kmap(): */ #ifdef CONFIG_PREEMPT_RT -# define kmap_atomic_prot(page, type, prot) ({ pagefault_disable(); kmap(page); }) +# define kmap_atomic_prot(page, type, prot) ({ pagefault_disable(); kmap_pfn_prot(page_to_pfn(page), prot); }) +# define kmap_atomic_prot_pfn(pfn, type, prot) ({ pagefault_disable(); kmap_pfn_prot(pfn, prot); }) # define kmap_atomic(page, type) ({ pagefault_disable(); kmap(page); }) # define kmap_atomic_pfn(pfn, type) kmap(pfn_to_page(pfn)) -# define kunmap_atomic(kvaddr, type) do { pagefault_enable(); kunmap_virt(kvaddr); } while(0) +# define kunmap_atomic(kvaddr, type) do { kunmap_virt(kvaddr); pagefault_enable(); } while(0) # define kmap_atomic_to_page(kvaddr) kmap_to_page(kvaddr) # define kmap_atomic_direct(page, type) __kmap_atomic_direct(page, type) # define kunmap_atomic_direct(kvaddr, type) __kunmap_atomic(kvaddr, type) #else # define kmap_atomic_prot(page, type, prot) __kmap_atomic_prot(page, type, prot) +# define kmap_atomic_prot_pfn(pfn, type, prot) __kmap_atomic_prot_pfn(pfn, type, prot) # define kmap_atomic(page, type) __kmap_atomic(page, type) # define kmap_atomic_pfn(pfn, type) __kmap_atomic_pfn(pfn, type) # define kunmap_atomic(kvaddr, type) __kunmap_atomic(kvaddr, type) diff --git a/arch/x86/mm/highmem_32.c b/arch/x86/mm/highmem_32.c index dcb1899..b4eb59a 100644 --- a/arch/x86/mm/highmem_32.c +++ b/arch/x86/mm/highmem_32.c @@ -19,16 +19,6 @@ void kunmap(struct page *page) kunmap_high(page); } -void kunmap_virt(void *ptr) -{ - struct page *page; - - if ((unsigned long)ptr < PKMAP_ADDR(0)) - return; - page = pte_page(pkmap_page_table[PKMAP_NR((unsigned long)ptr)]); - kunmap(page); -} - struct page *kmap_to_page(void *ptr) { struct page *page; @@ -70,6 +60,23 @@ void *__kmap_atomic_prot(struct page *page, enum km_type type, pgprot_t prot) return (void *)vaddr; } +void *__kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type, pgprot_t prot) +{ + enum fixed_addresses idx; + unsigned long vaddr; + + preempt_disable(); + pagefault_disable(); + + debug_kmap_atomic(type); + idx = type + KM_TYPE_NR * smp_processor_id(); + vaddr = __fix_to_virt(FIX_KMAP_BEGIN + idx); + set_pte(kmap_pte - idx, pfn_pte(pfn, prot)); + arch_flush_lazy_mmu_mode(); + + return (void *)vaddr; +} + void *__kmap_atomic_direct(struct page *page, enum km_type type) { return __kmap_atomic_prot(page, type, kmap_prot); diff --git a/arch/x86/mm/iomap_32.c b/arch/x86/mm/iomap_32.c index 715d822..8b784dd 100644 --- a/arch/x86/mm/iomap_32.c +++ b/arch/x86/mm/iomap_32.c @@ -55,23 +55,6 @@ iomap_free(resource_size_t base, unsigned long size) } EXPORT_SYMBOL_GPL(iomap_free); -void *kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type, pgprot_t prot) -{ - enum fixed_addresses idx; - unsigned long vaddr; - - preempt_disable(); - pagefault_disable(); - - debug_kmap_atomic(type); - idx = type + KM_TYPE_NR * smp_processor_id(); - vaddr = __fix_to_virt(FIX_KMAP_BEGIN + idx); - set_pte(kmap_pte - idx, pfn_pte(pfn, prot)); - arch_flush_lazy_mmu_mode(); - - return (void *)vaddr; -} - /* * Map 'pfn' using fixed map 'type' and protections 'prot' */ diff --git a/mm/highmem.c b/mm/highmem.c index 446b75c..43447d4 100644 --- a/mm/highmem.c +++ b/mm/highmem.c @@ -66,7 +66,13 @@ unsigned int nr_free_highpages (void) * 1 means its free for use - either mapped or not. * n means that there are (n-1) current users of it. */ -static atomic_t pkmap_count[LAST_PKMAP]; + +struct pkmap_state { + atomic_t count; + int pfn; +}; + +static struct pkmap_state pkmap[LAST_PKMAP]; static atomic_t pkmap_hand; static atomic_t pkmap_free; static atomic_t pkmap_users; @@ -105,25 +111,26 @@ static DECLARE_WAIT_QUEUE_HEAD(pkmap_wait); */ static int pkmap_try_free(int pos) { - if (atomic_cmpxchg(&pkmap_count[pos], 1, 0) != 1) + if (atomic_cmpxchg(&pkmap[pos].count, 1, 0) != 1) return -1; atomic_dec(&pkmap_free); /* * TODO: add a young bit to make it CLOCK */ if (!pte_none(pkmap_page_table[pos])) { - struct page *page = pte_page(pkmap_page_table[pos]); unsigned long addr = PKMAP_ADDR(pos); pte_t *ptep = &pkmap_page_table[pos]; - VM_BUG_ON(addr != (unsigned long)page_address(page)); + if (!pkmap[pos].pfn) { + struct page *page = pte_page(pkmap_page_table[pos]); + VM_BUG_ON(addr != (unsigned long)page_address(page)); + if (!__set_page_address(page, NULL, pos)) + BUG(); + flush_kernel_dcache_page(page); + } - if (!__set_page_address(page, NULL, pos)) - BUG(); - flush_kernel_dcache_page(page); pte_clear(&init_mm, addr, ptep); - return 1; } @@ -187,7 +194,7 @@ got_one: continue; if (!flush) { - atomic_t *counter = &pkmap_count[pos2]; + atomic_t *counter = &pkmap[pos2].count; VM_BUG_ON(atomic_read(counter) != 0); atomic_set(counter, 2); pkmap_put(counter); @@ -197,7 +204,7 @@ got_one: flush_tlb_kernel_range(PKMAP_ADDR(0), PKMAP_ADDR(LAST_PKMAP)); for (i = 0; i < nr; i++) { - atomic_t *counter = &pkmap_count[entries[i]]; + atomic_t *counter = &pkmap[entries[i]].count; VM_BUG_ON(atomic_read(counter) != 0); atomic_set(counter, 2); pkmap_put(counter); @@ -207,32 +214,51 @@ got_one: return pos; } -static unsigned long pkmap_insert(struct page *page) +static unsigned long pkmap_insert(unsigned long pfn, pgprot_t prot) { int pos = pkmap_get_free(); unsigned long vaddr = PKMAP_ADDR(pos); pte_t *ptep = &pkmap_page_table[pos]; - pte_t entry = mk_pte(page, kmap_prot); - atomic_t *counter = &pkmap_count[pos]; + pte_t entry = pfn_pte(pfn, prot); + atomic_t *counter = &pkmap[pos].count; VM_BUG_ON(atomic_read(counter) != 0); - set_pte_at(&init_mm, vaddr, ptep, entry); - if (unlikely(!__set_page_address(page, (void *)vaddr, pos))) { + + pkmap[pos].pfn = + !(pgprot_val(prot) == pgprot_val(kmap_prot) && pfn_valid(pfn)); + + if (!pkmap[pos].pfn) { + struct page *page = pfn_to_page(pfn); + + if (unlikely(!__set_page_address(page, (void *)vaddr, pos))) { + /* + * concurrent pkmap_inserts for this page - + * the other won the race, release this entry. + * + * we can still clear the pte without a tlb flush since + * it couldn't have been used yet. + */ + pte_clear(&init_mm, vaddr, ptep); + VM_BUG_ON(atomic_read(counter) != 0); + atomic_set(counter, 2); + pkmap_put(counter); + return 0; + } + } else { +#ifdef ARCH_NEEDS_KMAP_HIGH_GET /* - * concurrent pkmap_inserts for this page - - * the other won the race, release this entry. + * non-default prot and pure pfn memory doesn't + * get map deduplication, nor a working page_address * - * we can still clear the pte without a tlb flush since - * it couldn't have been used yet. + * this also makes it incompatible with + * ARCH_NEEDS_KMAP_HIGH_GET */ - pte_clear(&init_mm, vaddr, ptep); - VM_BUG_ON(atomic_read(counter) != 0); - atomic_set(counter, 2); - pkmap_put(counter); - vaddr = 0; - } else - atomic_set(counter, 2); + BUG(); +#endif + } + + atomic_set(counter, 2); return vaddr; } @@ -313,20 +339,17 @@ static void kunmap_account(void) wake_up(&pkmap_wait); } -void *kmap_high(struct page *page) +void *kmap_get(struct page *page) { unsigned long vaddr; - - - kmap_account(); again: vaddr = (unsigned long)page_address(page); if (vaddr) { - atomic_t *counter = &pkmap_count[PKMAP_NR(vaddr)]; + atomic_t *counter = &pkmap[PKMAP_NR(vaddr)].count; if (atomic_inc_not_zero(counter)) { /* - * atomic_inc_not_zero implies a (memory) barrier on success - * so page address will be reloaded. + * atomic_inc_not_zero implies a (memory) barrier on + * success so page address will be reloaded. */ unsigned long vaddr2 = (unsigned long)page_address(page); if (likely(vaddr == vaddr2)) @@ -341,13 +364,42 @@ again: * reused. */ pkmap_put(counter); - goto again; } + goto again; } + return (void *)vaddr; +} - vaddr = pkmap_insert(page); - if (!vaddr) - goto again; +void *kmap_high(struct page *page) +{ + unsigned long vaddr; + + kmap_account(); + +again: + vaddr = (unsigned long)kmap_get(page); + if (!vaddr) { + vaddr = pkmap_insert(page_to_pfn(page), kmap_prot); + if (!vaddr) + goto again; + } + + return (void *)vaddr; +} + + +void *kmap_pfn_prot(unsigned long pfn, pgprot_t prot) +{ + unsigned long vaddr; + + if (pgprot_val(prot) == pgprot_val(kmap_prot) && + pfn_valid(pfn) && PageHighMem(pfn_to_page(pfn))) + return kmap_high(pfn_to_page(pfn)); + + kmap_account(); + + vaddr = pkmap_insert(pfn, prot); + BUG_ON(!vaddr); return (void *)vaddr; } @@ -370,21 +422,26 @@ void *kmap_high_get(struct page *page) unsigned long vaddr, flags; lock_kmap_any(flags); - vaddr = (unsigned long)page_address(page); - if (vaddr) { - BUG_ON(pkmap_count[PKMAP_NR(vaddr)] < 1); - pkmap_count[PKMAP_NR(vaddr)]++; - } + vaddr = (unsigned long)kmap_get(page); unlock_kmap_any(flags); - return (void*) vaddr; + return (void *)vaddr; } #endif - void kunmap_high(struct page *page) +void kunmap_virt(void *ptr) +{ + unsigned long vaddr = (unsigned long)ptr; + if (vaddr < PKMAP_ADDR(0) || vaddr >= PKMAP_ADDR(LAST_PKMAP)) + return; + pkmap_put(&pkmap[PKMAP_NR(vaddr)].count); + kunmap_account(); +} + +void kunmap_high(struct page *page) { unsigned long vaddr = (unsigned long)page_address(page); BUG_ON(!vaddr); - pkmap_put(&pkmap_count[PKMAP_NR(vaddr)]); + pkmap_put(&pkmap[PKMAP_NR(vaddr)].count); kunmap_account(); } @@ -539,8 +596,8 @@ void __init page_address_init(void) #ifdef CONFIG_HIGHMEM int i; - for (i = 0; i < ARRAY_SIZE(pkmap_count); i++) - atomic_set(&pkmap_count[i], 1); + for (i = 0; i < ARRAY_SIZE(pkmap); i++) + atomic_set(&pkmap[i].count, 1); atomic_set(&pkmap_hand, 0); atomic_set(&pkmap_free, LAST_PKMAP); atomic_set(&pkmap_users, 0); ^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rc8-rt2 2010-02-24 22:38 ` Peter Zijlstra @ 2010-02-25 22:56 ` Peter Zijlstra 0 siblings, 0 replies; 54+ messages in thread From: Peter Zijlstra @ 2010-02-25 22:56 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Steven Rostedt, Clark Williams, nando, Carsten Emde On Wed, 2010-02-24 at 23:38 +0100, Peter Zijlstra wrote: > On Wed, 2010-02-24 at 17:52 +0100, Thomas Gleixner wrote: > > > > - the highmem problem which Fernando reported with i915 on 32bit > > i386 is not yet solved. > > The below compiles and boots a i386 defconfig kernel in kvm, I don't > have a system with 32bit userspace and i915 handy further test this. > The below seems to boot on 32bit with i915, but since the box was headless not much was thrown at it. --- arch/x86/include/asm/highmem.h | 9 ++- arch/x86/mm/highmem_32.c | 27 +++++--- arch/x86/mm/iomap_32.c | 32 +-------- mm/highmem.c | 152 +++++++++++++++++++++++++++------------ 4 files changed, 130 insertions(+), 90 deletions(-) diff --git a/arch/x86/include/asm/highmem.h b/arch/x86/include/asm/highmem.h index 433ae1f..8279657 100644 --- a/arch/x86/include/asm/highmem.h +++ b/arch/x86/include/asm/highmem.h @@ -55,14 +55,17 @@ extern unsigned long highstart_pfn, highend_pfn; #define PKMAP_ADDR(nr) (PKMAP_BASE + ((nr) << PAGE_SHIFT)) extern void *kmap_high(struct page *page); +extern void *kmap_pfn_prot(unsigned long pfn, pgprot_t prot); extern void kunmap_high(struct page *page); void *kmap(struct page *page); +void *kmap_page_prot(struct page *page, pgprot_t prot); extern void kunmap_virt(void *ptr); extern struct page *kmap_to_page(void *ptr); void kunmap(struct page *page); void *__kmap_atomic_prot(struct page *page, enum km_type type, pgprot_t prot); +void *__kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type, pgprot_t prot); void *__kmap_atomic(struct page *page, enum km_type type); void *__kmap_atomic_direct(struct page *page, enum km_type type); void __kunmap_atomic(void *kvaddr, enum km_type type); @@ -85,15 +88,17 @@ extern void add_highpages_with_active_regions(int nid, unsigned long start_pfn, * on PREEMPT_RT kmap_atomic() is a wrapper that uses kmap(): */ #ifdef CONFIG_PREEMPT_RT -# define kmap_atomic_prot(page, type, prot) ({ pagefault_disable(); kmap(page); }) +# define kmap_atomic_prot(page, type, prot) ({ pagefault_disable(); kmap_pfn_prot(page_to_pfn(page), prot); }) +# define kmap_atomic_prot_pfn(pfn, type, prot) ({ pagefault_disable(); kmap_pfn_prot(pfn, prot); }) # define kmap_atomic(page, type) ({ pagefault_disable(); kmap(page); }) # define kmap_atomic_pfn(pfn, type) kmap(pfn_to_page(pfn)) -# define kunmap_atomic(kvaddr, type) do { pagefault_enable(); kunmap_virt(kvaddr); } while(0) +# define kunmap_atomic(kvaddr, type) do { kunmap_virt(kvaddr); pagefault_enable(); } while(0) # define kmap_atomic_to_page(kvaddr) kmap_to_page(kvaddr) # define kmap_atomic_direct(page, type) __kmap_atomic_direct(page, type) # define kunmap_atomic_direct(kvaddr, type) __kunmap_atomic(kvaddr, type) #else # define kmap_atomic_prot(page, type, prot) __kmap_atomic_prot(page, type, prot) +# define kmap_atomic_prot_pfn(pfn, type, prot) __kmap_atomic_prot_pfn(pfn, type, prot) # define kmap_atomic(page, type) __kmap_atomic(page, type) # define kmap_atomic_pfn(pfn, type) __kmap_atomic_pfn(pfn, type) # define kunmap_atomic(kvaddr, type) __kunmap_atomic(kvaddr, type) diff --git a/arch/x86/mm/highmem_32.c b/arch/x86/mm/highmem_32.c index dcb1899..b4eb59a 100644 --- a/arch/x86/mm/highmem_32.c +++ b/arch/x86/mm/highmem_32.c @@ -19,16 +19,6 @@ void kunmap(struct page *page) kunmap_high(page); } -void kunmap_virt(void *ptr) -{ - struct page *page; - - if ((unsigned long)ptr < PKMAP_ADDR(0)) - return; - page = pte_page(pkmap_page_table[PKMAP_NR((unsigned long)ptr)]); - kunmap(page); -} - struct page *kmap_to_page(void *ptr) { struct page *page; @@ -70,6 +60,23 @@ void *__kmap_atomic_prot(struct page *page, enum km_type type, pgprot_t prot) return (void *)vaddr; } +void *__kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type, pgprot_t prot) +{ + enum fixed_addresses idx; + unsigned long vaddr; + + preempt_disable(); + pagefault_disable(); + + debug_kmap_atomic(type); + idx = type + KM_TYPE_NR * smp_processor_id(); + vaddr = __fix_to_virt(FIX_KMAP_BEGIN + idx); + set_pte(kmap_pte - idx, pfn_pte(pfn, prot)); + arch_flush_lazy_mmu_mode(); + + return (void *)vaddr; +} + void *__kmap_atomic_direct(struct page *page, enum km_type type) { return __kmap_atomic_prot(page, type, kmap_prot); diff --git a/arch/x86/mm/iomap_32.c b/arch/x86/mm/iomap_32.c index 715d822..38a1a68 100644 --- a/arch/x86/mm/iomap_32.c +++ b/arch/x86/mm/iomap_32.c @@ -55,23 +55,6 @@ iomap_free(resource_size_t base, unsigned long size) } EXPORT_SYMBOL_GPL(iomap_free); -void *kmap_atomic_prot_pfn(unsigned long pfn, enum km_type type, pgprot_t prot) -{ - enum fixed_addresses idx; - unsigned long vaddr; - - preempt_disable(); - pagefault_disable(); - - debug_kmap_atomic(type); - idx = type + KM_TYPE_NR * smp_processor_id(); - vaddr = __fix_to_virt(FIX_KMAP_BEGIN + idx); - set_pte(kmap_pte - idx, pfn_pte(pfn, prot)); - arch_flush_lazy_mmu_mode(); - - return (void *)vaddr; -} - /* * Map 'pfn' using fixed map 'type' and protections 'prot' */ @@ -94,19 +77,6 @@ EXPORT_SYMBOL_GPL(iomap_atomic_prot_pfn); void iounmap_atomic(void *kvaddr, enum km_type type) { - unsigned long vaddr = (unsigned long) kvaddr & PAGE_MASK; - enum fixed_addresses idx = type + KM_TYPE_NR*smp_processor_id(); - - /* - * Force other mappings to Oops if they'll try to access this pte - * without first remap it. Keeping stale mappings around is a bad idea - * also, in case the page changes cacheability attributes or becomes - * a protected page in a hypervisor. - */ - if (vaddr == __fix_to_virt(FIX_KMAP_BEGIN+idx)) - kpte_clear_flush(kmap_pte-idx, vaddr); - - pagefault_enable(); - preempt_enable(); + kunmap_atomic(kvaddr, type); } EXPORT_SYMBOL_GPL(iounmap_atomic); diff --git a/mm/highmem.c b/mm/highmem.c index 446b75c..1b534a8 100644 --- a/mm/highmem.c +++ b/mm/highmem.c @@ -66,7 +66,13 @@ unsigned int nr_free_highpages (void) * 1 means its free for use - either mapped or not. * n means that there are (n-1) current users of it. */ -static atomic_t pkmap_count[LAST_PKMAP]; + +struct pkmap_state { + atomic_t count; + int pfn; +}; + +static struct pkmap_state pkmap[LAST_PKMAP]; static atomic_t pkmap_hand; static atomic_t pkmap_free; static atomic_t pkmap_users; @@ -105,25 +111,26 @@ static DECLARE_WAIT_QUEUE_HEAD(pkmap_wait); */ static int pkmap_try_free(int pos) { - if (atomic_cmpxchg(&pkmap_count[pos], 1, 0) != 1) + if (atomic_cmpxchg(&pkmap[pos].count, 1, 0) != 1) return -1; atomic_dec(&pkmap_free); /* * TODO: add a young bit to make it CLOCK */ if (!pte_none(pkmap_page_table[pos])) { - struct page *page = pte_page(pkmap_page_table[pos]); unsigned long addr = PKMAP_ADDR(pos); pte_t *ptep = &pkmap_page_table[pos]; - VM_BUG_ON(addr != (unsigned long)page_address(page)); + if (!pkmap[pos].pfn) { + struct page *page = pte_page(pkmap_page_table[pos]); + VM_BUG_ON(addr != (unsigned long)page_address(page)); + if (!__set_page_address(page, NULL, pos)) + BUG(); + flush_kernel_dcache_page(page); + } - if (!__set_page_address(page, NULL, pos)) - BUG(); - flush_kernel_dcache_page(page); pte_clear(&init_mm, addr, ptep); - return 1; } @@ -187,7 +194,7 @@ got_one: continue; if (!flush) { - atomic_t *counter = &pkmap_count[pos2]; + atomic_t *counter = &pkmap[pos2].count; VM_BUG_ON(atomic_read(counter) != 0); atomic_set(counter, 2); pkmap_put(counter); @@ -197,7 +204,7 @@ got_one: flush_tlb_kernel_range(PKMAP_ADDR(0), PKMAP_ADDR(LAST_PKMAP)); for (i = 0; i < nr; i++) { - atomic_t *counter = &pkmap_count[entries[i]]; + atomic_t *counter = &pkmap[entries[i]].count; VM_BUG_ON(atomic_read(counter) != 0); atomic_set(counter, 2); pkmap_put(counter); @@ -207,32 +214,51 @@ got_one: return pos; } -static unsigned long pkmap_insert(struct page *page) +static unsigned long pkmap_insert(unsigned long pfn, pgprot_t prot) { int pos = pkmap_get_free(); unsigned long vaddr = PKMAP_ADDR(pos); pte_t *ptep = &pkmap_page_table[pos]; - pte_t entry = mk_pte(page, kmap_prot); - atomic_t *counter = &pkmap_count[pos]; + pte_t entry = pfn_pte(pfn, prot); + atomic_t *counter = &pkmap[pos].count; VM_BUG_ON(atomic_read(counter) != 0); - set_pte_at(&init_mm, vaddr, ptep, entry); - if (unlikely(!__set_page_address(page, (void *)vaddr, pos))) { + + pkmap[pos].pfn = + !(pgprot_val(prot) == pgprot_val(kmap_prot) && pfn_valid(pfn)); + + if (!pkmap[pos].pfn) { + struct page *page = pfn_to_page(pfn); + + if (unlikely(!__set_page_address(page, (void *)vaddr, pos))) { + /* + * concurrent pkmap_inserts for this page - + * the other won the race, release this entry. + * + * we can still clear the pte without a tlb flush since + * it couldn't have been used yet. + */ + pte_clear(&init_mm, vaddr, ptep); + VM_BUG_ON(atomic_read(counter) != 0); + atomic_set(counter, 2); + pkmap_put(counter); + return 0; + } + } else { +#ifdef ARCH_NEEDS_KMAP_HIGH_GET /* - * concurrent pkmap_inserts for this page - - * the other won the race, release this entry. + * non-default prot and pure pfn memory doesn't + * get map deduplication, nor a working page_address * - * we can still clear the pte without a tlb flush since - * it couldn't have been used yet. + * this also makes it incompatible with + * ARCH_NEEDS_KMAP_HIGH_GET */ - pte_clear(&init_mm, vaddr, ptep); - VM_BUG_ON(atomic_read(counter) != 0); - atomic_set(counter, 2); - pkmap_put(counter); - vaddr = 0; - } else - atomic_set(counter, 2); + BUG(); +#endif + } + + atomic_set(counter, 2); return vaddr; } @@ -313,20 +339,17 @@ static void kunmap_account(void) wake_up(&pkmap_wait); } -void *kmap_high(struct page *page) +void *kmap_get(struct page *page) { unsigned long vaddr; - - - kmap_account(); again: vaddr = (unsigned long)page_address(page); if (vaddr) { - atomic_t *counter = &pkmap_count[PKMAP_NR(vaddr)]; + atomic_t *counter = &pkmap[PKMAP_NR(vaddr)].count; if (atomic_inc_not_zero(counter)) { /* - * atomic_inc_not_zero implies a (memory) barrier on success - * so page address will be reloaded. + * atomic_inc_not_zero implies a (memory) barrier on + * success so page address will be reloaded. */ unsigned long vaddr2 = (unsigned long)page_address(page); if (likely(vaddr == vaddr2)) @@ -341,19 +364,49 @@ again: * reused. */ pkmap_put(counter); - goto again; } + goto again; } + return (void *)vaddr; +} - vaddr = pkmap_insert(page); - if (!vaddr) - goto again; +void *kmap_high(struct page *page) +{ + unsigned long vaddr; + + kmap_account(); + +again: + vaddr = (unsigned long)kmap_get(page); + if (!vaddr) { + vaddr = pkmap_insert(page_to_pfn(page), kmap_prot); + if (!vaddr) + goto again; + } return (void *)vaddr; } EXPORT_SYMBOL(kmap_high); +void *kmap_pfn_prot(unsigned long pfn, pgprot_t prot) +{ + unsigned long vaddr; + + if (pgprot_val(prot) == pgprot_val(kmap_prot) && + pfn_valid(pfn) && PageHighMem(pfn_to_page(pfn))) + return kmap_high(pfn_to_page(pfn)); + + kmap_account(); + + vaddr = pkmap_insert(pfn, prot); + BUG_ON(!vaddr); + + return (void *)vaddr; +} + +EXPORT_SYMBOL(kmap_pfn_prot); + #ifdef ARCH_NEEDS_KMAP_HIGH_GET /** * kmap_high_get - pin a highmem page into memory @@ -370,21 +423,26 @@ void *kmap_high_get(struct page *page) unsigned long vaddr, flags; lock_kmap_any(flags); - vaddr = (unsigned long)page_address(page); - if (vaddr) { - BUG_ON(pkmap_count[PKMAP_NR(vaddr)] < 1); - pkmap_count[PKMAP_NR(vaddr)]++; - } + vaddr = (unsigned long)kmap_get(page); unlock_kmap_any(flags); - return (void*) vaddr; + return (void *)vaddr; } #endif - void kunmap_high(struct page *page) +void kunmap_virt(void *ptr) +{ + unsigned long vaddr = (unsigned long)ptr; + if (vaddr < PKMAP_ADDR(0) || vaddr >= PKMAP_ADDR(LAST_PKMAP)) + return; + pkmap_put(&pkmap[PKMAP_NR(vaddr)].count); + kunmap_account(); +} + +void kunmap_high(struct page *page) { unsigned long vaddr = (unsigned long)page_address(page); BUG_ON(!vaddr); - pkmap_put(&pkmap_count[PKMAP_NR(vaddr)]); + pkmap_put(&pkmap[PKMAP_NR(vaddr)].count); kunmap_account(); } @@ -539,8 +597,8 @@ void __init page_address_init(void) #ifdef CONFIG_HIGHMEM int i; - for (i = 0; i < ARRAY_SIZE(pkmap_count); i++) - atomic_set(&pkmap_count[i], 1); + for (i = 0; i < ARRAY_SIZE(pkmap); i++) + atomic_set(&pkmap[i].count, 1); atomic_set(&pkmap_hand, 0); atomic_set(&pkmap_free, LAST_PKMAP); atomic_set(&pkmap_users, 0); ^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rc8-rt2 2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner 2010-02-24 22:38 ` Peter Zijlstra @ 2010-02-26 19:44 ` Dan Carpenter 2010-02-27 8:10 ` Thomas Gleixner 2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner 2 siblings, 1 reply; 54+ messages in thread From: Dan Carpenter @ 2010-02-26 19:44 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde kernel/trace/latency_hist.c 341 static ssize_t 342 latency_hist_reset(struct file *file, const char __user *a, 343 size_t size, loff_t *off) 344 { 345 int cpu; 346 struct hist_data *hist = NULL; 347 #if defined(CONFIG_WAKEUP_LATENCY_HIST) || \ 348 defined(CONFIG_MISSED_TIMER_OFFSETS_HIST) 349 struct maxlatproc_data *mp = NULL; 350 #endif 351 off_t latency_type = (off_t) file->private_data; 352 353 for_each_online_cpu(cpu) { 354 355 switch (latency_type) { It seems like this switch statement should have a default case. I haven't looked into it very closely but it seems like if you had all those config options turned off then "hist" would be still be NULL. regards, dan carpenter ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rc8-rt2 2010-02-26 19:44 ` Dan Carpenter @ 2010-02-27 8:10 ` Thomas Gleixner 0 siblings, 0 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-02-27 8:10 UTC (permalink / raw) To: Dan Carpenter Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde On Fri, 26 Feb 2010, Dan Carpenter wrote: > kernel/trace/latency_hist.c > 341 static ssize_t > 342 latency_hist_reset(struct file *file, const char __user *a, > 343 size_t size, loff_t *off) > 344 { > 345 int cpu; > 346 struct hist_data *hist = NULL; > 347 #if defined(CONFIG_WAKEUP_LATENCY_HIST) || \ > 348 defined(CONFIG_MISSED_TIMER_OFFSETS_HIST) > 349 struct maxlatproc_data *mp = NULL; > 350 #endif > 351 off_t latency_type = (off_t) file->private_data; > 352 > 353 for_each_online_cpu(cpu) { > 354 > 355 switch (latency_type) { > > It seems like this switch statement should have a default case. > > I haven't looked into it very closely but it seems like if you had all > those config options turned off then "hist" would be still be NULL. When all config options are turned off then the file is not compiled at all. Thanks, tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33-rt3 2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner 2010-02-24 22:38 ` Peter Zijlstra 2010-02-26 19:44 ` Dan Carpenter @ 2010-02-26 19:54 ` Thomas Gleixner 2010-02-27 9:25 ` Xavier Miller ` (2 more replies) 2 siblings, 3 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-02-26 19:54 UTC (permalink / raw) To: LKML Cc: rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde We are pleased to announce the next update to our new preempt-rt series. - Update to 2.6.33 - rt fixes: Peter Zijlstra (1): highmem, -rt: Implement pfn and prot kmaps Thomas Gleixner (2): x86: pci: Prevent mmconfig memory corruption mmc: omap_hsmmc: Fix the locking mess A note on the development process: The rt/2.6.33 branch is now stabilization only. The rt/head branch will follow linus tree from now on, so it will inherit all (mis)features which come in the merge window. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33-rt3 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner @ 2010-02-27 9:25 ` Xavier Miller 2010-02-27 9:50 ` GeunSik Lim 2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner 2 siblings, 0 replies; 54+ messages in thread From: Xavier Miller @ 2010-02-27 9:25 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde Hello, The name is -rt4, not -rt3 Xavier Miller. Le 26/02/10 20:54, Thomas Gleixner a écrit : > We are pleased to announce the next update to our new preempt-rt > series. > > - Update to 2.6.33 > > - rt fixes: > > Peter Zijlstra (1): > highmem, -rt: Implement pfn and prot kmaps > > Thomas Gleixner (2): > x86: pci: Prevent mmconfig memory corruption > mmc: omap_hsmmc: Fix the locking mess > > A note on the development process: > > The rt/2.6.33 branch is now stabilization only. The rt/head branch > will follow linus tree from now on, so it will inherit all > (mis)features which come in the merge window. > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git development branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33-rt3 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2 > > Enjoy ! > > tglx > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 @ 2010-02-27 9:25 ` Xavier Miller 0 siblings, 0 replies; 54+ messages in thread From: Xavier Miller @ 2010-02-27 9:25 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde Hello, The name is -rt4, not -rt3 Xavier Miller. Le 26/02/10 20:54, Thomas Gleixner a écrit : > We are pleased to announce the next update to our new preempt-rt > series. > > - Update to 2.6.33 > > - rt fixes: > > Peter Zijlstra (1): > highmem, -rt: Implement pfn and prot kmaps > > Thomas Gleixner (2): > x86: pci: Prevent mmconfig memory corruption > mmc: omap_hsmmc: Fix the locking mess > > A note on the development process: > > The rt/2.6.33 branch is now stabilization only. The rt/head branch > will follow linus tree from now on, so it will inherit all > (mis)features which come in the merge window. > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git development branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33-rt3 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2 > > Enjoy ! > > tglx > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 2010-02-27 9:25 ` Xavier Miller (?) @ 2010-02-27 10:10 ` GeunSik Lim -1 siblings, 0 replies; 54+ messages in thread From: GeunSik Lim @ 2010-02-27 10:10 UTC (permalink / raw) To: Xavier Miller Cc: Thomas Gleixner, LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde > The name is -rt4, not -rt3 > Xavier Miller. Hi Xavier. When I checked -rt tag currently, tag name is -rt4 based 2.6.33. So, I changed -rt tag name to -rt4. Test result is normal with 2.6.33-rt4 on my desktop(Q6600, SSD64G, DDR2 2GRAM) at least. :) Thanks, On Sat, Feb 27, 2010 at 6:25 PM, Xavier Miller <xavier.miller@cauwe.org> wrote: > Hello, > > The name is -rt4, not -rt3 > > Xavier Miller. > > Le 26/02/10 20:54, Thomas Gleixner a écrit : >> We are pleased to announce the next update to our new preempt-rt >> series. >> >> - Update to 2.6.33 >> >> - rt fixes: >> >> Peter Zijlstra (1): >> highmem, -rt: Implement pfn and prot kmaps >> >> Thomas Gleixner (2): >> x86: pci: Prevent mmconfig memory corruption >> mmc: omap_hsmmc: Fix the locking mess >> >> A note on the development process: >> >> The rt/2.6.33 branch is now stabilization only. The rt/head branch >> will follow linus tree from now on, so it will inherit all >> (mis)features which come in the merge window. >> >> Download locations: >> >> http://www.kernel.org/pub/linux/kernel/projects/rt/ >> >> Git development branch: >> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head >> >> Git release branch: >> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 >> >> Gitweb: >> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 >> >> Information on the RT patch can be found at: >> >> http://rt.wiki.kernel.org/index.php/Main_Page >> >> To build the 2.6.33-rt3 tree, the following patches should be >> applied: >> >> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 >> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2 >> >> Enjoy ! >> >> tglx >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Regards, GeunSik Lim ( Samsung Electronics ) Blog : http://blog.naver.com/invain/ e-Mail: geunsik.lim@samsung.com leemgs@gmail.com , leemgs1@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 2010-02-27 9:25 ` Xavier Miller (?) (?) @ 2010-02-27 11:53 ` Thomas Gleixner 2010-03-02 21:25 ` Fernando Lopez-Lezcano -1 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-02-27 11:53 UTC (permalink / raw) To: Xavier Miller Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde On Sat, 27 Feb 2010, Xavier Miller wrote: > Hello, > > The name is -rt4, not -rt3 I pushed out an -rt4 w/o notice in the morning because I forgot to pick up a few trivial fixes for -rt3. Thanks tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 2010-02-27 11:53 ` Thomas Gleixner @ 2010-03-02 21:25 ` Fernando Lopez-Lezcano 2010-03-02 21:53 ` Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Fernando Lopez-Lezcano @ 2010-03-02 21:25 UTC (permalink / raw) To: Thomas Gleixner Cc: nando, Xavier Miller, LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, Carsten Emde On Sat, 2010-02-27 at 12:53 +0100, Thomas Gleixner wrote: > On Sat, 27 Feb 2010, Xavier Miller wrote: > > > Hello, > > > > The name is -rt4, not -rt3 > > I pushed out an -rt4 w/o notice in the morning because I forgot to > pick up a few trivial fixes for -rt3. Hmm, I had to comment out a VM_BUG_ON for pkmap_count in mm/highmem.c, looks like pkmap_count is not defined anywhere else? -- Fernando ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 2010-03-02 21:25 ` Fernando Lopez-Lezcano @ 2010-03-02 21:53 ` Thomas Gleixner 0 siblings, 0 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-03-02 21:53 UTC (permalink / raw) To: Fernando Lopez-Lezcano Cc: Xavier Miller, LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, Carsten Emde Fernando, On Tue, 2 Mar 2010, Fernando Lopez-Lezcano wrote: > On Sat, 2010-02-27 at 12:53 +0100, Thomas Gleixner wrote: > > On Sat, 27 Feb 2010, Xavier Miller wrote: > > > > > Hello, > > > > > > The name is -rt4, not -rt3 > > > > I pushed out an -rt4 w/o notice in the morning because I forgot to > > pick up a few trivial fixes for -rt3. > > Hmm, I had to comment out a VM_BUG_ON for pkmap_count in mm/highmem.c, > looks like pkmap_count is not defined anywhere else? yuck, did not notice due to CONFIG_VM_DEBUG=n. Will fix. Thanks, tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner @ 2010-02-27 9:50 ` GeunSik Lim 2010-02-27 9:50 ` GeunSik Lim 2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner 2 siblings, 0 replies; 54+ messages in thread From: GeunSik Lim @ 2010-02-27 9:50 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde Dear Thomas, Thank you for notice about 2.6.33 based -rt3. I tested system booting with linux-2.6.33-rt3 on my Q6600 based Desktop. For reference, I am using Centos 5.4 rootFS. As a result, I booted this version on my desktop successfully. * Booting result of linux-2.6.33-rt3 on Q6600 PC. --> Passed. http://picasaweb.google.com/leemgs/LinuxRelatedScreenshot#5442856195052253634 Regards, Geunsik Lim. On Sat, Feb 27, 2010 at 4:54 AM, Thomas Gleixner <tglx@linutronix.de> wrote: > We are pleased to announce the next update to our new preempt-rt > series. > > - Update to 2.6.33 > > - rt fixes: > > Peter Zijlstra (1): > highmem, -rt: Implement pfn and prot kmaps > > Thomas Gleixner (2): > x86: pci: Prevent mmconfig memory corruption > mmc: omap_hsmmc: Fix the locking mess > > A note on the development process: > > The rt/2.6.33 branch is now stabilization only. The rt/head branch > will follow linus tree from now on, so it will inherit all > (mis)features which come in the merge window. > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git development branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33-rt3 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2 > > Enjoy ! > > tglx > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Regards, GeunSik Lim ( Samsung Electronics ) Blog : http://blog.naver.com/invain/ e-Mail: geunsik.lim@samsung.com leemgs@gmail.com , leemgs1@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33-rt3 @ 2010-02-27 9:50 ` GeunSik Lim 0 siblings, 0 replies; 54+ messages in thread From: GeunSik Lim @ 2010-02-27 9:50 UTC (permalink / raw) To: Thomas Gleixner Cc: LKML, rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde Dear Thomas, Thank you for notice about 2.6.33 based -rt3. I tested system booting with linux-2.6.33-rt3 on my Q6600 based Desktop. For reference, I am using Centos 5.4 rootFS. As a result, I booted this version on my desktop successfully. * Booting result of linux-2.6.33-rt3 on Q6600 PC. --> Passed. http://picasaweb.google.com/leemgs/LinuxRelatedScreenshot#5442856195052253634 Regards, Geunsik Lim. On Sat, Feb 27, 2010 at 4:54 AM, Thomas Gleixner <tglx@linutronix.de> wrote: > We are pleased to announce the next update to our new preempt-rt > series. > > - Update to 2.6.33 > > - rt fixes: > > Peter Zijlstra (1): > highmem, -rt: Implement pfn and prot kmaps > > Thomas Gleixner (2): > x86: pci: Prevent mmconfig memory corruption > mmc: omap_hsmmc: Fix the locking mess > > A note on the development process: > > The rt/2.6.33 branch is now stabilization only. The rt/head branch > will follow linus tree from now on, so it will inherit all > (mis)features which come in the merge window. > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git development branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33-rt3 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2 > > Enjoy ! > > tglx > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Regards, GeunSik Lim ( Samsung Electronics ) Blog : http://blog.naver.com/invain/ e-Mail: geunsik.lim@samsung.com leemgs@gmail.com , leemgs1@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33-rt6 2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner 2010-02-27 9:25 ` Xavier Miller 2010-02-27 9:50 ` GeunSik Lim @ 2010-03-12 10:44 ` Thomas Gleixner 2010-03-12 12:17 ` 2.6.33-rt6 on Beagle Chatterjee, Amit 2010-03-21 11:06 ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner 2 siblings, 2 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-03-12 10:44 UTC (permalink / raw) To: LKML Cc: rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde, Wu Zhangjin, Nicholas Mc Guire We are pleased to announce the next update to our new preempt-rt series. For those who wonder about -rt5. It's there as well, but the tag is more or less a separation point. Changes from -rt4 to -rt5: 8fafaf5: v2.6.33-rt5 f6e20d0: tracing: Define pid functions for all config combinations 4216e30: vga console: Remove the CON_ATOMIC flag 7033151: x86: Fix 32bit HIGHMEM=n compile c28c2c8: x86: highmem: Remove stale function prototype fb301a4: mm: highmem: Fix stale BUG_ON condition Changes from -rt5 to -rt6: af5d4b6: v2.6.33-rt6 1054085: Merge branch 'rt-2.6.33-queue' of git://dev.lemote.com/rt4ls into rt/2.6.33 This brings MIPS back into the -RT world! Thanks to Wu Zhangjin !! Note that the MIPS support is only tested on Loongson hardware so your milage with other MIPS incarnations may vary. Known issues for -rt6: - load balancer induced latencies. Can be observed in extreme system overload situations (load avg > 1000), so probably not a real world issue, but still it shows a weak point. - rcu stalls on overload situations caused by exit_io_context() RCU read locked section which heavily contends on sleeping locks. Still under investigation. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33-rt6 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt6.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* 2.6.33-rt6 on Beagle 2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner @ 2010-03-12 12:17 ` Chatterjee, Amit 2010-03-15 9:20 ` Uwe Kleine-König 2010-03-21 11:06 ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner 1 sibling, 1 reply; 54+ messages in thread From: Chatterjee, Amit @ 2010-03-12 12:17 UTC (permalink / raw) To: linux-rt-users-owner; +Cc: rt-users Hi, I am unable to boot the kernel (as available in this link - http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=refs/heads/rt/2.6.33) on Beagle board. Kernel is unable to uncompress itself & crashing. Tool chain used is - gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67). I will check with older toolchain & keep it posted. Regards, Amit -----Original Message----- From: linux-rt-users-owner@vger.kernel.org [mailto:linux-rt-users-owner@vger.kernel.org] On Behalf Of Thomas Gleixner Sent: Friday, March 12, 2010 4:14 PM To: LKML Cc: rt-users; Ingo Molnar; Peter Zijlstra; Steven Rostedt; Clark Williams; nando@ccrma.Stanford.EDU; Carsten Emde; Wu Zhangjin; Nicholas Mc Guire Subject: [ANNOUNCE] 2.6.33-rt6 We are pleased to announce the next update to our new preempt-rt series. For those who wonder about -rt5. It's there as well, but the tag is more or less a separation point. Changes from -rt4 to -rt5: 8fafaf5: v2.6.33-rt5 f6e20d0: tracing: Define pid functions for all config combinations 4216e30: vga console: Remove the CON_ATOMIC flag 7033151: x86: Fix 32bit HIGHMEM=n compile c28c2c8: x86: highmem: Remove stale function prototype fb301a4: mm: highmem: Fix stale BUG_ON condition Changes from -rt5 to -rt6: af5d4b6: v2.6.33-rt6 1054085: Merge branch 'rt-2.6.33-queue' of git://dev.lemote.com/rt4ls into rt/2.6.33 This brings MIPS back into the -RT world! Thanks to Wu Zhangjin !! Note that the MIPS support is only tested on Loongson hardware so your milage with other MIPS incarnations may vary. Known issues for -rt6: - load balancer induced latencies. Can be observed in extreme system overload situations (load avg > 1000), so probably not a real world issue, but still it shows a weak point. - rcu stalls on overload situations caused by exit_io_context() RCU read locked section which heavily contends on sleeping locks. Still under investigation. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33-rt6 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt6.bz2 Enjoy ! tglx -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: 2.6.33-rt6 on Beagle 2010-03-12 12:17 ` 2.6.33-rt6 on Beagle Chatterjee, Amit @ 2010-03-15 9:20 ` Uwe Kleine-König 2010-03-15 11:23 ` What's the best way to create an embedded version of PREEMPT_RT Linux ? Armin Steinhoff 0 siblings, 1 reply; 54+ messages in thread From: Uwe Kleine-König @ 2010-03-15 9:20 UTC (permalink / raw) To: Chatterjee, Amit; +Cc: rt-users Hello Amit, On Fri, Mar 12, 2010 at 05:47:56PM +0530, Chatterjee, Amit wrote: > Hi, > I am unable to boot the kernel (as available in this link - http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=refs/heads/rt/2.6.33) on Beagle board. Kernel is unable to uncompress itself & crashing. Tool chain used is - gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67). I will check with older toolchain & keep it posted. Can you try to cherry-pick 5de813b6cd06460b337f9da9afe316823cf3ef45 currently sitting in Russell Kings devel branch[1]? The decompressor has a known bug in .33 on ARM. Best regards Uwe [1] http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm.git/ -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* What's the best way to create an embedded version of PREEMPT_RT Linux ? 2010-03-15 9:20 ` Uwe Kleine-König @ 2010-03-15 11:23 ` Armin Steinhoff 0 siblings, 0 replies; 54+ messages in thread From: Armin Steinhoff @ 2010-03-15 11:23 UTC (permalink / raw) To: rt-users Hi, is there a way to use KIWI for it ? --Armin ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.1-rt11 2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner 2010-03-12 12:17 ` 2.6.33-rt6 on Beagle Chatterjee, Amit @ 2010-03-21 11:06 ` Thomas Gleixner 2010-04-07 14:24 ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner 1 sibling, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-03-21 11:06 UTC (permalink / raw) To: LKML Cc: rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde, Wu Zhangjin, Nicholas Mc Guire We are pleased to announce the next update to our new preempt-rt series. I pushed out a bunch of updates while traveling w/o a release mail, so here is the change log from rt6 to rt11 Changes from rt10 to rt11 318e45e: sched: Fix pick_next_highest_task_rt() for cgroups 6d79084: ARM: Eliminate decompressor -Dstatic= PIC hack Changes from rt9 to rt10 e89fab2: x86: Fix the highmem fallout really Changes from rt8 to rt9 Update to 2.6.33.1, see http://lwn.net/Articles/378613/ Changes from rt7 to rt8 5d2740b: sched: Break out from load_balancing on rq_lock contention cd4ac9b: x86: Fix iomap_atomic with highmem=y again Changes from rt6 to rt7 2c5f66a: Revert "Loongson: add a new option FUJITSU_QUIRKS" Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33-rt11 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.1.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.1-rt11.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.2-rt13 2010-03-21 11:06 ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner @ 2010-04-07 14:24 ` Thomas Gleixner 2010-04-27 15:52 ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-04-07 14:24 UTC (permalink / raw) To: LKML Cc: rt-users, Ingo Molnar, Peter Zijlstra, Steven Rostedt, Clark Williams, nando, Carsten Emde, Wu Zhangjin, Nicholas Mc Guire B1;2005;0cWe are pleased to announce the next update to our new preempt-rt series. I pushed out rt12 w/o a release mail, so here is the change log from rt11 to rt13 Changes from rt11 to rt12 35b5256: x86: Fix irq off tracing for 32 bit 6e331ac: net: gianfar: Make RT aware ac4d7f0: Merge 2.6.33.2 into -RT Changes from rt12 to rt13 b2c877a: mqueue: Convert message queue timeout to use hrtimers 3c3016f: hrtimers: Provide schedule_hrtimeout for CLOCK_REALTIME d980cb7: raid5: Make raid5_percpu handling RT aware e86d615: powerpc: Convert uic->lock to raw_spinlock Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.2-rt13 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.2.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.2-rt13.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.3-rt16 2010-04-07 14:24 ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner @ 2010-04-27 15:52 ` Thomas Gleixner 2010-04-30 10:00 ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-04-27 15:52 UTC (permalink / raw) To: LKML; +Cc: rt-users, Nick Piggin, John Stultz We are pleased to announce the next update to our new preempt-rt series. I pushed out rt14 and rt15 w/o a release mail, so here are the change logs from rt13 to rt16 Changes from rt13 to rt14 846bcf3: Merge 2.6.33.3 863c3ad: net: Fix iptables get_counters() Changes from rt14 to rt15 510cc22: net: gianfar: More RT fixups 923499c: rtmutex: Preserve TASK_STOPPED state when blocking on a "spin_lock" 1268870: powerpc: Replace kmap_atomic with kmap in pte_offset_map Changes from rt15 to rt16 That's the long awaited merge of Nick's VFS scalability patches. Thanks to Nick and John for keeping it up to date and fixing the problems which we observed with earlier versions. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.3-rt16 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.3.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.3-rt16.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.3-rt17 2010-04-27 15:52 ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner @ 2010-04-30 10:00 ` Thomas Gleixner 2010-05-02 19:18 ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-04-30 10:00 UTC (permalink / raw) To: LKML; +Cc: rt-users, John Stultz, Nick Piggin We are pleased to announce the next update to our new preempt-rt series. Mostly fixups for the VFS scalability fallout. 4c8acb4: rt: Fix the reminder block accounting for CONFIG_FUNCTION_TRACER 4eba98c: fs: Use s_inodes not s_files for inode lists 4329d1a: fs: Fix namespace related hangs a0a5961: xfs: Make i_count access non-atomic d3d17b8: fs: Fix d_count fallout 5e022ed: fs: namespace: Fix MNT_MOUNTED handling for cloned rootfs 4b44047: fs: namespace: Make put_mnt_ns rt aware f008b2b: fs: namespace: Fix potential deadlock f4c3013: rt: Remove irrelevant CONFIGS from reminder block. 6994daf: hugetlb: fix infinite loop in get_futex_key() when backed by huge pages Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.3-rt17 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.3.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.3-rt17.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.3-rt19 2010-04-30 10:00 ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner @ 2010-05-02 19:18 ` Thomas Gleixner 2010-06-09 16:44 ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-05-02 19:18 UTC (permalink / raw) To: LKML; +Cc: rt-users, John Stultz, Nick Piggin We are pleased to announce the next update to our new preempt-rt series. Changes from 2.6.33.3-rt17 to 2.6.33.3-rt18: edf9d4b5: tclib: Default to tclib timer for RT 917c377: Atmel TCLIB: Allow higher clock rates for clock events b16bd4f: AT91: PIT: Remove irq handler when clock event is unused 360c3e7: fs: Prevent dput race Changes from 2.6.33.3-rt18 to 2.6.33.3-rt19: 4b40e94: sched: Warn on rt throttling dc15be1: init: Fix config items in debug reminder finally Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git development branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.3-rt19 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.3.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.3-rt19.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.5-rt23 2010-05-02 19:18 ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner @ 2010-06-09 16:44 ` Thomas Gleixner 2010-06-09 21:31 ` Will Schmidt 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner 0 siblings, 2 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-06-09 16:44 UTC (permalink / raw) To: LKML; +Cc: rt-users, John Stultz, Nick Piggin We are pleased to announce the next update to our new preempt-rt series. Changes from 2.6.33.3-rt19 to 2.6.33.4-rt20: 5b6c7b0: net: Make [dis/en]able_irq_*_lockdep() RT safe d6434af: fs: Resolve mntput_no_expire issues. 56e4c7f: fs: Fix mnt_count typo 1540c84: Merge branch '2.6.33.4' into rt/2.6.33 1a3a403: autofs4: Remove another autofs4_lock deadlock 6b568a0: autofs: Remove deadlock c54c071: fs: Add missing parantheses Changes from 2.6.33.4-rt20 to 2.6.33.4-rt21: cc4a826: sched: Fix wake_affine() vs RT tasks ea17fed: printk: Fix missing klogd wakeup 9846da2: fix undefined references to kernel_sem e868252: fs: namespace: Fix fuse mount fallout 44b341a: net: ehea: make rx irq handler non-threaded (IRQF_NODELAY) Changes from 2.6.33.4-rt21 to 2.6.33.5-rt22: ef4afcc: Merge stable/linux-2.6.33.y into rt/2.6.33 Changes from 2.6.33.5-rt22 to 2.6.33.5-rt23: ab774e8: drivers/hwmon/coretemp.c: get TjMax value from MSR e8bfcca: drivers/hwmon/coretemp.c: detect the thermal sensors by CPUID a06a867: dcache: Prevent d_genocide() from decrementing d_count more than once bdeadaf: nfs: Avoid igrab deadlock. 6976846: dcache: Fix select_parent dentry traversal locking 1f0f6ec: powerpc: chrp/time.c fix preprocessor conditional Bulk of changes comes from stable tree. The -rt related changes are mostly fixes for the vfs fallout the rest are fixlets all over the place and hardware enablement. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.5-rt23 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.5.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.5-rt23.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-09 16:44 ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner @ 2010-06-09 21:31 ` Will Schmidt 2010-06-10 6:07 ` Thomas Gleixner 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner 1 sibling, 1 reply; 54+ messages in thread From: Will Schmidt @ 2010-06-09 21:31 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users, John Stultz, Nick Piggin On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > We are pleased to announce the next update to our new preempt-rt > series. > <snip> > Changes from 2.6.33.4-rt21 to 2.6.33.5-rt22: > > ef4afcc: Merge stable/linux-2.6.33.y into rt/2.6.33 > > Changes from 2.6.33.5-rt22 to 2.6.33.5-rt23: > > ab774e8: drivers/hwmon/coretemp.c: get TjMax value from MSR > e8bfcca: drivers/hwmon/coretemp.c: detect the thermal sensors by CPUID > a06a867: dcache: Prevent d_genocide() from decrementing d_count more than once > bdeadaf: nfs: Avoid igrab deadlock. > 6976846: dcache: Fix select_parent dentry traversal locking > 1f0f6ec: powerpc: chrp/time.c fix preprocessor conditional I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple "sleeping function called from invalid context..." BUGs. The first was during system boot, second during a 'make'. relevant code paths don't seem to have changed between -rt22 and -rt23, so I think still valid.. :-) This is on a POWER7 system, which may have opened up some timing windows, wrt previous runs on POWER6 systems. BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 pcnt: 1 0 in_atomic(): 1, irqs_disabled(): 1, pid: 3209, name: ip Call Trace: [c000000078cf28e0] [c000000000015550] .show_stack+0xd8/0x218 (unreliable) [c000000078cf29c0] [c0000000006a99c8] .dump_stack+0x28/0x3c [c000000078cf2a40] [c00000000006cea8] .__might_sleep+0x134/0x15c [c000000078cf2ae0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c [c000000078cf2b70] [c0000000001799e8] ._slab_irq_disable+0x70/0xd8 [c000000078cf2c20] [c00000000017d1b4] .kmem_cache_alloc_node_notrace +0x78/0x234 [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node+0xdc/0x2b8 [c000000078cf2db0] [c00000000000f238] .irq_setup_virq+0x44/0xe4 [c000000078cf2e50] [c00000000000f3f8] .irq_create_mapping+0x120/0x188 [c000000078cf2ef0] [c00000000002edfc] .ibmebus_request_irq+0x50/0xac [c000000078cf2fa0] [c0000000004f3bd0] .ehea_up+0x314/0x69c [c000000078cf30b0] [c0000000004f3fc8] .ehea_open+0x70/0x128 [c000000078cf3150] [c0000000005e504c] .dev_open+0x120/0x198 [c000000078cf31f0] [c0000000005e3ee8] .dev_change_flags+0x11c/0x21c [c000000078cf32a0] [c0000000005f10ec] .do_setlink+0x2e0/0x400 [c000000078cf3380] [c0000000005f23a0] .rtnl_newlink+0x380/0x5b8 [c000000078cf3580] [c0000000005f1fd4] .rtnetlink_rcv_msg+0x258/0x2a4 [c000000078cf3630] [c000000000604094] .netlink_rcv_skb+0x84/0x120 [c000000078cf36d0] [c0000000005f1d58] .rtnetlink_rcv+0x38/0x5c [c000000078cf3760] [c000000000603ba0] .netlink_unicast+0x31c/0x3fc [c000000078cf3840] [c000000000604838] .netlink_sendmsg+0x2c8/0x30c [c000000078cf3930] [c0000000005c8bdc] .sock_sendmsg+0xbc/0xfc [c000000078cf3b10] [c0000000005c92fc] .SyS_sendmsg+0x20c/0x2a4 [c000000078cf3d50] [c0000000005c7f6c] .SyS_socketcall+0x238/0x2b0 [c000000078cf3e30] [c00000000000852c] syscall_exit+0x0/0x40 BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 4760, name: make Call Trace: [c0000000792978b0] [c000000000015550] .show_stack+0xd8/0x218 (unreliable) [c000000079297990] [c0000000006a99c8] .dump_stack+0x28/0x3c [c000000079297a10] [c00000000006cea8] .__might_sleep+0x134/0x15c [c000000079297ab0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c [c000000079297b40] [c0000000000a1ff0] .get_signal_to_deliver+0xcc/0x4ec [c000000079297c50] [c000000000018604] .do_signal_pending.clone.0+0x6c/0x2e0 [c000000079297d90] [c0000000000188b0] .do_signal+0x38/0x74 [c000000079297e30] [c000000000008b40] user_work+0x24/0x28 > > Bulk of changes comes from stable tree. The -rt related changes are > mostly fixes for the vfs fallout the rest are fixlets all over the > place and hardware enablement. > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.5-rt23 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.5.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.5-rt23.bz2 > > Enjoy ! > > tglx > > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-09 21:31 ` Will Schmidt @ 2010-06-10 6:07 ` Thomas Gleixner 2010-06-10 15:56 ` Will Schmidt 0 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-06-10 6:07 UTC (permalink / raw) To: Will Schmidt; +Cc: LKML, rt-users, John Stultz, Nick Piggin On Wed, 9 Jun 2010, Will Schmidt wrote: > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > "sleeping function called from invalid context..." BUGs. The first was > during system boot, second during a 'make'. > > relevant code paths don't seem to have changed between -rt22 and -rt23, > so I think still valid.. :-) > > This is on a POWER7 system, which may have opened up some timing > windows, wrt previous runs on POWER6 systems. > > > BUG: sleeping function called from invalid context at > kernel/rtmutex.c:684 > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node+0xdc/0x2b8 Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems it came back somehow. Can you disable that, or does you machine depend on it ? > BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 > pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 4760, name: make > Call Trace: > [c0000000792978b0] [c000000000015550] .show_stack+0xd8/0x218 (unreliable) > [c000000079297990] [c0000000006a99c8] .dump_stack+0x28/0x3c > [c000000079297a10] [c00000000006cea8] .__might_sleep+0x134/0x15c > [c000000079297ab0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c > [c000000079297b40] [c0000000000a1ff0] .get_signal_to_deliver+0xcc/0x4ec > [c000000079297c50] [c000000000018604] .do_signal_pending.clone.0+0x6c/0x2e0 > [c000000079297d90] [c0000000000188b0] .do_signal+0x38/0x74 > [c000000079297e30] [c000000000008b40] user_work+0x24/0x28 Does the patch below fix it ? Thanks, tglx ----- diff --git a/arch/powerpc/kernel/signal.c b/arch/powerpc/kernel/signal.c index 00b5078..fa580f9 100644 --- a/arch/powerpc/kernel/signal.c +++ b/arch/powerpc/kernel/signal.c @@ -120,6 +120,14 @@ static int do_signal_pending(sigset_t *oldset, struct pt_regs *regs) int ret; int is32 = is_32bit_task(); +#ifdef CONFIG_PREEMPT_RT + /* + * Fully-preemptible kernel does not need interrupts disabled: + */ + local_irq_enable(); + preempt_check_resched(); +#endif + if (current_thread_info()->local_flags & _TLF_RESTORE_SIGMASK) oldset = ¤t->saved_sigmask; else if (!oldset) ^ permalink raw reply related [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-10 6:07 ` Thomas Gleixner @ 2010-06-10 15:56 ` Will Schmidt 2010-06-10 16:05 ` Darcy L. Watkins 2010-06-14 13:34 ` Thomas Gleixner 0 siblings, 2 replies; 54+ messages in thread From: Will Schmidt @ 2010-06-10 15:56 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users, John Stultz, Nick Piggin On Thu, 2010-06-10 at 08:07 +0200, Thomas Gleixner wrote: > On Wed, 9 Jun 2010, Will Schmidt wrote: > > > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > > "sleeping function called from invalid context..." BUGs. The first was > > during system boot, second during a 'make'. > > > > relevant code paths don't seem to have changed between -rt22 and -rt23, > > so I think still valid.. :-) > > > > This is on a POWER7 system, which may have opened up some timing > > windows, wrt previous runs on POWER6 systems. > > > > > > BUG: sleeping function called from invalid context at > > kernel/rtmutex.c:684 > > > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node+0xdc/0x2b8 > > Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems > it came back somehow. Can you disable that, or does you machine depend > on it ? I'm not sure whether it is required by the architecture. I do see that SPARSE_IRQ is disabled in arch/x86/Kconfig with a !PREEMPT_RT, but I don't see an equivalent 'disable' in arch/powerpc/Kconfig. > > BUG: sleeping function called from invalid context at kernel/rtmutex.c:684 > > pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 4760, name: make > > Call Trace: > > [c0000000792978b0] [c000000000015550] .show_stack+0xd8/0x218 (unreliable) > > [c000000079297990] [c0000000006a99c8] .dump_stack+0x28/0x3c > > [c000000079297a10] [c00000000006cea8] .__might_sleep+0x134/0x15c > > [c000000079297ab0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c > > [c000000079297b40] [c0000000000a1ff0] .get_signal_to_deliver+0xcc/0x4ec > > [c000000079297c50] [c000000000018604] .do_signal_pending.clone.0+0x6c/0x2e0 > > [c000000079297d90] [c0000000000188b0] .do_signal+0x38/0x74 > > [c000000079297e30] [c000000000008b40] user_work+0x24/0x28 > > Does the patch below fix it ? Probably.. :-) I'm running with the patch now, and no repeats of that BUG yet. Thanks, -Will > > Thanks, > > tglx > ----- > diff --git a/arch/powerpc/kernel/signal.c b/arch/powerpc/kernel/signal.c > index 00b5078..fa580f9 100644 > --- a/arch/powerpc/kernel/signal.c > +++ b/arch/powerpc/kernel/signal.c > @@ -120,6 +120,14 @@ static int do_signal_pending(sigset_t *oldset, struct pt_regs *regs) > int ret; > int is32 = is_32bit_task(); > > +#ifdef CONFIG_PREEMPT_RT > + /* > + * Fully-preemptible kernel does not need interrupts disabled: > + */ > + local_irq_enable(); > + preempt_check_resched(); > +#endif > + > if (current_thread_info()->local_flags & _TLF_RESTORE_SIGMASK) > oldset = ¤t->saved_sigmask; > else if (!oldset) ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-10 15:56 ` Will Schmidt @ 2010-06-10 16:05 ` Darcy L. Watkins 2010-06-14 13:33 ` Thomas Gleixner 2010-06-14 13:34 ` Thomas Gleixner 1 sibling, 1 reply; 54+ messages in thread From: Darcy L. Watkins @ 2010-06-10 16:05 UTC (permalink / raw) To: will_schmidt; +Cc: Thomas Gleixner, LKML, rt-users, John Stultz, Nick Piggin On Thu, 2010-06-10 at 08:56 -0700, Will Schmidt wrote: > On Thu, 2010-06-10 at 08:07 +0200, Thomas Gleixner wrote: > > On Wed, 9 Jun 2010, Will Schmidt wrote: > > > > > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > > > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > > > "sleeping function called from invalid context..." BUGs. The > first was > > > during system boot, second during a 'make'. > > > > > > relevant code paths don't seem to have changed between -rt22 and > -rt23, > > > so I think still valid.. :-) > > > > > > This is on a POWER7 system, which may have opened up some timing > > > windows, wrt previous runs on POWER6 systems. > > > > > > > > > BUG: sleeping function called from invalid context at > > > kernel/rtmutex.c:684 > > > > > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node > +0xdc/0x2b8 > > > > Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems > > it came back somehow. Can you disable that, or does you machine > depend > > on it ? > > I'm not sure whether it is required by the architecture. I do see > that > SPARSE_IRQ is disabled in arch/x86/Kconfig with a !PREEMPT_RT, but I > don't see an equivalent 'disable' in arch/powerpc/Kconfig. > I see it as "y" in my .config for a powerpc 405 build. This appears to run on my system (although I haven't loaded up the rt23 build on the target yet - last one loaded up was rt22). What should I expect to see different if SPARSE_IRQ is turned off? > > > > BUG: sleeping function called from invalid context at > kernel/rtmutex.c:684 > > > pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 4760, name: > make > > > Call Trace: > > > [c0000000792978b0] [c000000000015550] .show_stack+0xd8/0x218 > (unreliable) > > > [c000000079297990] [c0000000006a99c8] .dump_stack+0x28/0x3c > > > [c000000079297a10] [c00000000006cea8] .__might_sleep+0x134/0x15c > > > [c000000079297ab0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c > > > [c000000079297b40] [c0000000000a1ff0] .get_signal_to_deliver > +0xcc/0x4ec > > > [c000000079297c50] [c000000000018604] .do_signal_pending.clone.0 > +0x6c/0x2e0 > > > [c000000079297d90] [c0000000000188b0] .do_signal+0x38/0x74 > > > [c000000079297e30] [c000000000008b40] user_work+0x24/0x28 > > > > Does the patch below fix it ? > > Probably.. :-) I'm running with the patch now, and no repeats of > that > BUG yet. > > Thanks, > -Will > > > > > > Thanks, > > > > tglx > > ----- > > diff --git a/arch/powerpc/kernel/signal.c > b/arch/powerpc/kernel/signal.c > > index 00b5078..fa580f9 100644 > > --- a/arch/powerpc/kernel/signal.c > > +++ b/arch/powerpc/kernel/signal.c > > @@ -120,6 +120,14 @@ static int do_signal_pending(sigset_t *oldset, > struct pt_regs *regs) > > int ret; > > int is32 = is_32bit_task(); > > > > +#ifdef CONFIG_PREEMPT_RT > > + /* > > + * Fully-preemptible kernel does not need interrupts disabled: > > + */ > > + local_irq_enable(); > > + preempt_check_resched(); > > +#endif > > + > > if (current_thread_info()->local_flags & _TLF_RESTORE_SIGMASK) > > oldset = ¤t->saved_sigmask; > > else if (!oldset) > > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-10 16:05 ` Darcy L. Watkins @ 2010-06-14 13:33 ` Thomas Gleixner 0 siblings, 0 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-06-14 13:33 UTC (permalink / raw) To: Darcy L. Watkins; +Cc: will_schmidt, LKML, rt-users, John Stultz, Nick Piggin On Thu, 10 Jun 2010, Darcy L. Watkins wrote: > > > On Thu, 2010-06-10 at 08:56 -0700, Will Schmidt wrote: > > On Thu, 2010-06-10 at 08:07 +0200, Thomas Gleixner wrote: > > > On Wed, 9 Jun 2010, Will Schmidt wrote: > > > > > > > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > > > > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > > > > "sleeping function called from invalid context..." BUGs. The > > first was > > > > during system boot, second during a 'make'. > > > > > > > > relevant code paths don't seem to have changed between -rt22 and > > -rt23, > > > > so I think still valid.. :-) > > > > > > > > This is on a POWER7 system, which may have opened up some timing > > > > windows, wrt previous runs on POWER6 systems. > > > > > > > > > > > > BUG: sleeping function called from invalid context at > > > > kernel/rtmutex.c:684 > > > > > > > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node > > +0xdc/0x2b8 > > > > > > Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems > > > it came back somehow. Can you disable that, or does you machine > > depend > > > on it ? > > > > I'm not sure whether it is required by the architecture. I do see > > that > > SPARSE_IRQ is disabled in arch/x86/Kconfig with a !PREEMPT_RT, but I > > don't see an equivalent 'disable' in arch/powerpc/Kconfig. > > > > I see it as "y" in my .config for a powerpc 405 build. This appears to > run on my system (although I haven't loaded up the rt23 build on the > target yet - last one loaded up was rt22). > > What should I expect to see different if SPARSE_IRQ is turned off? The difference is that you can trigger "scheduling while atomic". The warning Will has seen depends on debug options. Thanks, tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-10 15:56 ` Will Schmidt 2010-06-10 16:05 ` Darcy L. Watkins @ 2010-06-14 13:34 ` Thomas Gleixner 2010-06-14 15:35 ` Will Schmidt 1 sibling, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-06-14 13:34 UTC (permalink / raw) To: Will Schmidt; +Cc: LKML, rt-users, John Stultz, Nick Piggin On Thu, 10 Jun 2010, Will Schmidt wrote: > On Thu, 2010-06-10 at 08:07 +0200, Thomas Gleixner wrote: > > On Wed, 9 Jun 2010, Will Schmidt wrote: > > > > > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > > > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > > > "sleeping function called from invalid context..." BUGs. The first was > > > during system boot, second during a 'make'. > > > > > > relevant code paths don't seem to have changed between -rt22 and -rt23, > > > so I think still valid.. :-) > > > > > > This is on a POWER7 system, which may have opened up some timing > > > windows, wrt previous runs on POWER6 systems. > > > > > > > > > BUG: sleeping function called from invalid context at > > > kernel/rtmutex.c:684 > > > > > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node+0xdc/0x2b8 > > > > Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems > > it came back somehow. Can you disable that, or does you machine depend > > on it ? > > I'm not sure whether it is required by the architecture. I do see that > SPARSE_IRQ is disabled in arch/x86/Kconfig with a !PREEMPT_RT, but I > don't see an equivalent 'disable' in arch/powerpc/Kconfig. Can you disable it ? Thanks, tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.5-rt23 2010-06-14 13:34 ` Thomas Gleixner @ 2010-06-14 15:35 ` Will Schmidt 0 siblings, 0 replies; 54+ messages in thread From: Will Schmidt @ 2010-06-14 15:35 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users, John Stultz, Nick Piggin On Mon, 2010-06-14 at 15:34 +0200, Thomas Gleixner wrote: > On Thu, 10 Jun 2010, Will Schmidt wrote: > > > On Thu, 2010-06-10 at 08:07 +0200, Thomas Gleixner wrote: > > > On Wed, 9 Jun 2010, Will Schmidt wrote: > > > > > > > On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote: > > > > I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple > > > > "sleeping function called from invalid context..." BUGs. The first was > > > > during system boot, second during a 'make'. > > > > > > > > relevant code paths don't seem to have changed between -rt22 and -rt23, > > > > so I think still valid.. :-) > > > > > > > > This is on a POWER7 system, which may have opened up some timing > > > > windows, wrt previous runs on POWER6 systems. > > > > > > > > > > > > BUG: sleeping function called from invalid context at > > > > kernel/rtmutex.c:684 > > > > > > > [c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node+0xdc/0x2b8 > > > > > > Grr. I thought I had the SPARSE_IRQ stuff disabled on -rt, but seems > > > it came back somehow. Can you disable that, or does you machine depend > > > on it ? > > > > I'm not sure whether it is required by the architecture. I do see that > > SPARSE_IRQ is disabled in arch/x86/Kconfig with a !PREEMPT_RT, but I > > don't see an equivalent 'disable' in arch/powerpc/Kconfig. > > Can you disable it ? Yeah. [root@foo ~]# zcat /proc/config.gz | grep SPARSE # CONFIG_SPARSE_IRQ is not set ... Thats a sample size of one (POWER7) system, but seems to have worked. Thanks, -Will > > Thanks, > > tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.6-rt26 2010-06-09 16:44 ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner 2010-06-09 21:31 ` Will Schmidt @ 2010-07-13 15:54 ` Thomas Gleixner 2010-07-13 16:52 ` Dhaval Giani ` (3 more replies) 1 sibling, 4 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-07-13 15:54 UTC (permalink / raw) To: LKML; +Cc: rt-users, John Stultz, Nick Piggin We are pleased to announce the next update to our new preempt-rt series. Changes from 2.6.33.5-rt23 to 2.6.33.5-rt24: 42edbcb: gianfar: Fix TX ring processing on SMP machines faf3581: timer_stats: Convert table_lock to raw_spin_lock 654e404: hvc_console: Fix race between hvc_close and hvc_remove 09fd768: hvc_console: Fix race between hvc_close and hvc_remove ea2d2a0: perf: Fix errors path in perf_output_begin() 60bd946: KEYS: find_keyring_by_name() can gain access to a freed keyring b5ac516: tracing: Update the comm field in the right variable in update_max_tr 77cb7c1: lockdep: Reduce stack_trace usage cee9ee0: powerpc: Disable sparse irq for RT c7dec16: powerpc: Enable interrupts in do_signal() Changes from 2.6.33.5-rt24 to 2.6.33.5-rt25: ec646ea: vfs: Revert the scalability patches Changes from 2.6.33.5-rt26 to 2.6.33.6-rt26: 7e1af11: Merge git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.33.y Bulk of changes comes from the stable tree and from the big revert of the VFS scalability patches. They looked promising, but the nasty details bit us hard. We'll revisit them later. There are some pending issues: - rtc_lock suspend/resume (working on a patch) - futex requeue_pi (patch available, needs testing/confirmation) - powerpc64 oddities (patch available, needs rework) Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.6-rt26 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt26.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner @ 2010-07-13 16:52 ` Dhaval Giani 2010-07-13 18:04 ` Philipp Überbacher ` (2 subsequent siblings) 3 siblings, 0 replies; 54+ messages in thread From: Dhaval Giani @ 2010-07-13 16:52 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users, John Stultz, Nick Piggin Hi, > Enjoy ! > I hit this with rt26. (Quite possible is on vanilla as well, will build a kernel soemtime soon and try) ======================================================= [ INFO: possible circular locking dependency detected ] 2.6.33.6-rt26 #36 ------------------------------------------------------- iperf/1629 is trying to acquire lock: (slock-AF_INET){+.+...}, at: [<ffffffff8135a4fa>] release_sock+0x30/0x108 but task is already holding lock: (&lock->lock){+.+...}, at: [<ffffffff813cd6cc>] ipt_do_table+0x118/0x650 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&lock->lock){+.+...}: [<ffffffff810697e7>] lock_acquire+0xd6/0xfa [<ffffffff813fcfaa>] rt_spin_lock+0x31/0x38 [<ffffffffa00ba8ef>] nf_nat_get_offset+0x42/0x6b [nf_nat] [<ffffffff8138b2ba>] tcp_packet+0x659/0xd5b [<ffffffff81387eb9>] nf_conntrack_in+0x445/0x4fc [<ffffffff813ca933>] ipv4_conntrack_local+0x3b/0x44 [<ffffffff81384c22>] nf_iterate+0x41/0x84 [<ffffffff81384cd8>] nf_hook_slow+0x73/0xdb [<ffffffff813970b4>] nf_hook_thresh.clone.0+0x3c/0x45 [<ffffffff81397136>] __ip_local_out+0x79/0x7b [<ffffffff81397149>] ip_local_out+0x11/0x22 [<ffffffff81397407>] ip_push_pending_frames+0x2ad/0x30b [<ffffffff81398a41>] ip_send_reply+0x21a/0x259 [<ffffffff813acdf1>] tcp_v4_send_reset+0x1c8/0x1eb [<ffffffff813b0367>] tcp_v4_rcv+0x500/0x661 [<ffffffff8139400a>] ip_local_deliver_finish+0x14d/0x1c3 [<ffffffff813940f2>] ip_local_deliver+0x72/0x7c [<ffffffff81393ac3>] ip_rcv_finish+0x31a/0x346 [<ffffffff81393d29>] ip_rcv+0x23a/0x268 [<ffffffff81366862>] netif_receive_skb+0x3fa/0x424 [<ffffffffa023fb41>] br_handle_frame_finish+0x105/0x13d [bridge] [<ffffffffa023fd08>] br_handle_frame+0x18f/0x1a7 [bridge] [<ffffffff81366792>] netif_receive_skb+0x32a/0x424 [<ffffffff813669d4>] napi_skb_finish+0x24/0x3b [<ffffffff81366e83>] napi_gro_receive+0x2a/0x2f [<ffffffff812d03b9>] sky2_poll+0x86e/0xaef [<ffffffff81366fcc>] net_rx_action+0xa3/0x1f1 [<ffffffff81044a02>] run_ksoftirqd+0x14e/0x254 [<ffffffff8105975f>] kthread+0x88/0x90 [<ffffffff81009844>] kernel_thread_helper+0x4/0x10 -> #0 (slock-AF_INET){+.+...}: [<ffffffff8106941a>] __lock_acquire+0x9f1/0xce8 [<ffffffff810697e7>] lock_acquire+0xd6/0xfa [<ffffffff813fcfaa>] rt_spin_lock+0x31/0x38 [<ffffffff8135a4fa>] release_sock+0x30/0x108 [<ffffffff813a012a>] tcp_recvmsg+0x8b8/0x9a3 [<ffffffff81359864>] sock_common_recvmsg+0x37/0x48 [<ffffffff81357178>] __sock_recvmsg+0x6d/0x78 (Just run iperf as server and test it from another system) thanks, Dhaval ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner 2010-07-13 16:52 ` Dhaval Giani @ 2010-07-13 18:04 ` Philipp Überbacher 2010-07-13 19:13 ` Darcy L. Watkins 2010-07-19 6:37 ` Barry Song 2010-07-31 13:33 ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner 3 siblings, 1 reply; 54+ messages in thread From: Philipp Überbacher @ 2010-07-13 18:04 UTC (permalink / raw) To: linux-rt-users Excerpts from Thomas Gleixner's message of 2010-07-13 17:54:35 +0200: > We are pleased to announce the next update to our new preempt-rt > series. > > Changes from 2.6.33.5-rt23 to 2.6.33.5-rt24: > > 42edbcb: gianfar: Fix TX ring processing on SMP machines > faf3581: timer_stats: Convert table_lock to raw_spin_lock > 654e404: hvc_console: Fix race between hvc_close and hvc_remove > 09fd768: hvc_console: Fix race between hvc_close and hvc_remove > ea2d2a0: perf: Fix errors path in perf_output_begin() > 60bd946: KEYS: find_keyring_by_name() can gain access to a freed keyring > b5ac516: tracing: Update the comm field in the right variable in update_max_tr > 77cb7c1: lockdep: Reduce stack_trace usage > cee9ee0: powerpc: Disable sparse irq for RT > c7dec16: powerpc: Enable interrupts in do_signal() > > Changes from 2.6.33.5-rt24 to 2.6.33.5-rt25: > > ec646ea: vfs: Revert the scalability patches > > Changes from 2.6.33.5-rt26 to 2.6.33.6-rt26: > > 7e1af11: Merge git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.33.y > > Bulk of changes comes from the stable tree and from the big revert of > the VFS scalability patches. They looked promising, but the nasty > details bit us hard. We'll revisit them later. > > There are some pending issues: > - rtc_lock suspend/resume (working on a patch) > - futex requeue_pi (patch available, needs testing/confirmation) > - powerpc64 oddities (patch available, needs rework) > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.6-rt26 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt26.bz2 > > Enjoy ! > > tglx Thanks Thomas, but I have a problem applying the patch. I get lots of ignored hunks and it ends and fails with: 2 out of 2 hunks ignored -- saving rejects to file sound/soc/codecs/wm8990.c.rej patching file virt/kvm/kvm_main.c I tried to build with my usual script, which just does: patch -Np1 -i ../patch-2.6.33.6-rt26 Before that it applies the .6 patch, with the same command, without any hickup. I don't know whether something is wrong with the patch or whether I did something wrong. -- Regards, Philipp -- "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-13 18:04 ` Philipp Überbacher @ 2010-07-13 19:13 ` Darcy L. Watkins 2010-07-13 19:23 ` Philipp Überbacher 0 siblings, 1 reply; 54+ messages in thread From: Darcy L. Watkins @ 2010-07-13 19:13 UTC (permalink / raw) To: Philipp Überbacher; +Cc: linux-rt-users On Tue, 2010-07-13 at 11:04 -0700, Philipp Überbacher wrote: > Excerpts from Thomas Gleixner's message of 2010-07-13 17:54:35 +0200: > > We are pleased to announce the next update to our new preempt-rt > > series. > > --snip!-- > > > > To build the 2.6.33.6-rt26 tree, the following patches should be > > applied: > > > > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 > > > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt26.bz2 > > > > Enjoy ! > > > > tglx > Hi, The patch applies OK to the kernel 2.6.33.5 tarball. Either the patch is just a misnamed RT patch update to 2.6.33.5 or it includes both this and the 2.6.33.5-->2.6.33.6 incremental patch changes together and was just generated against the wrong baseline. So try it against 2.6.33.5 if you want to try something before the next patch is released. Darcy > Thanks Thomas, > but I have a problem applying the patch. > I get lots of ignored hunks and it ends and fails with: > > 2 out of 2 hunks ignored -- saving rejects to file > sound/soc/codecs/wm8990.c.rej > patching file virt/kvm/kvm_main.c > > I tried to build with my usual script, which just does: > patch -Np1 -i ../patch-2.6.33.6-rt26 > > Before that it applies the .6 patch, with the same command, without > any hickup. > I don't know whether something is wrong with the patch or whether I > did > something wrong. > -- > Regards, > Philipp > > -- > "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und > alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-13 19:13 ` Darcy L. Watkins @ 2010-07-13 19:23 ` Philipp Überbacher 2010-07-14 13:47 ` Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Philipp Überbacher @ 2010-07-13 19:23 UTC (permalink / raw) To: linux-rt-users Excerpts from Darcy L. Watkins's message of 2010-07-13 21:13:14 +0200: > > On Tue, 2010-07-13 at 11:04 -0700, Philipp Ãberbacher wrote: > > Excerpts from Thomas Gleixner's message of 2010-07-13 17:54:35 +0200: > > > We are pleased to announce the next update to our new preempt-rt > > > series. > > > > > --snip!-- > > > > > > > To build the 2.6.33.6-rt26 tree, the following patches should be > > > applied: > > > > > > > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 > > > > > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt26.bz2 > > > > > > Enjoy ! > > > > > > tglx > > > Hi, > > The patch applies OK to the kernel 2.6.33.5 tarball. Either the patch > is just a misnamed RT patch update to 2.6.33.5 or it includes both this > and the 2.6.33.5-->2.6.33.6 incremental patch changes together and was > just generated against the wrong baseline. So try it against 2.6.33.5 > if you want to try something before the next patch is released. > > Darcy Ah, thanks Darcy. It's don't urgently need it, so I'll just wait for Thomas' response, whether he'll upload a version against .6 or not. Either way is fine for me. -- Regards, Philipp -- "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-13 19:23 ` Philipp Überbacher @ 2010-07-14 13:47 ` Thomas Gleixner 2010-07-14 13:57 ` Ng Oon-Ee 2010-07-15 11:45 ` Philipp Überbacher 0 siblings, 2 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-07-14 13:47 UTC (permalink / raw) To: Philipp Überbacher; +Cc: linux-rt-users [-- Attachment #1: Type: TEXT/PLAIN, Size: 393 bytes --] On Tue, 13 Jul 2010, Philipp Überbacher wrote: > Ah, thanks Darcy. > It's don't urgently need it, so I'll just wait for Thomas' response, > whether he'll upload a version against .6 or not. Either way is fine for > me. Duh, I fat fingered my release script params. New version is uploaded, will take a bit until it mirrors out to the public servers. Sorry for the inconveniance, tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-14 13:47 ` Thomas Gleixner @ 2010-07-14 13:57 ` Ng Oon-Ee 2010-07-14 14:27 ` John Kacur 2010-07-15 11:45 ` Philipp Überbacher 1 sibling, 1 reply; 54+ messages in thread From: Ng Oon-Ee @ 2010-07-14 13:57 UTC (permalink / raw) To: Thomas Gleixner; +Cc: Philipp Überbacher, linux-rt-users On Wed, 2010-07-14 at 15:47 +0200, Thomas Gleixner wrote: > On Tue, 13 Jul 2010, Philipp Überbacher wrote: > > Ah, thanks Darcy. > > It's don't urgently need it, so I'll just wait for Thomas' response, > > whether he'll upload a version against .6 or not. Either way is fine for > > me. > > Duh, I fat fingered my release script params. New version is uploaded, > will take a bit until it mirrors out to the public servers. > > Sorry for the inconveniance, > > tglx Sorry for the dumb question, but its not clear whether 'new version' means 2.6.33.6-rt26 has been changed or 2.6.33.6-rt27 has been uploaded. Which is it? -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-14 13:57 ` Ng Oon-Ee @ 2010-07-14 14:27 ` John Kacur [not found] ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com> 0 siblings, 1 reply; 54+ messages in thread From: John Kacur @ 2010-07-14 14:27 UTC (permalink / raw) To: Ng Oon-Ee; +Cc: Thomas Gleixner, Philipp Überbacher, linux-rt-users 2010/7/14 Ng Oon-Ee <ngoonee@gmail.com>: > On Wed, 2010-07-14 at 15:47 +0200, Thomas Gleixner wrote: >> On Tue, 13 Jul 2010, Philipp Überbacher wrote: >> > Ah, thanks Darcy. >> > It's don't urgently need it, so I'll just wait for Thomas' response, >> > whether he'll upload a version against .6 or not. Either way is fine for >> > me. >> >> Duh, I fat fingered my release script params. New version is uploaded, >> will take a bit until it mirrors out to the public servers. >> >> Sorry for the inconveniance, >> >> tglx > > Sorry for the dumb question, but its not clear whether 'new version' > means 2.6.33.6-rt26 has been changed or 2.6.33.6-rt27 has been uploaded. > Which is it? > If you look in the directory, you can tell. :) He regenerated patch-2.6.33.6-rt26 John -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
[parent not found: <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com>]
* Re: [ANNOUNCE] 2.6.33.6-rt26 [not found] ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com> @ 2010-07-15 5:25 ` Yang Jian 0 siblings, 0 replies; 54+ messages in thread From: Yang Jian @ 2010-07-15 5:25 UTC (permalink / raw) To: linux-rt-users Hi, guys does 2.6.33.6-rt26 version support ARM EP9315 and powerpc mpc5121E series. I need the 2 boards in my real-time projects. On Thu, Jul 15, 2010 at 10:41 AM, Yang Jian <flyinwindy@gmail.com> wrote: > > > thanks. > 2010/7/14 John Kacur <jkacur@redhat.com> >> >> 2010/7/14 Ng Oon-Ee <ngoonee@gmail.com>: >> > On Wed, 2010-07-14 at 15:47 +0200, Thomas Gleixner wrote: >> >> On Tue, 13 Jul 2010, Philipp Überbacher wrote: >> >> > Ah, thanks Darcy. >> >> > It's don't urgently need it, so I'll just wait for Thomas' response, >> >> > whether he'll upload a version against .6 or not. Either way is fine for >> >> > me. >> >> >> >> Duh, I fat fingered my release script params. New version is uploaded, >> >> will take a bit until it mirrors out to the public servers. >> >> >> >> Sorry for the inconveniance, >> >> >> >> tglx >> > >> > Sorry for the dumb question, but its not clear whether 'new version' >> > means 2.6.33.6-rt26 has been changed or 2.6.33.6-rt27 has been uploaded. >> > Which is it? >> > >> >> If you look in the directory, you can tell. :) >> He regenerated patch-2.6.33.6-rt26 >> >> John >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > Best Regards > > Yang.Jian > +86 138 1100 5774 > flyinwindy@gmail.com -- Best Regards Yang.Jian +86 138 1100 5774 flyinwindy@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-14 13:47 ` Thomas Gleixner 2010-07-14 13:57 ` Ng Oon-Ee @ 2010-07-15 11:45 ` Philipp Überbacher 1 sibling, 0 replies; 54+ messages in thread From: Philipp Überbacher @ 2010-07-15 11:45 UTC (permalink / raw) To: linux-rt-users Excerpts from Thomas Gleixner's message of 2010-07-14 15:47:11 +0200: > On Tue, 13 Jul 2010, Philipp Ãberbacher wrote: > > Ah, thanks Darcy. > > It's don't urgently need it, so I'll just wait for Thomas' response, > > whether he'll upload a version against .6 or not. Either way is fine for > > me. > > Duh, I fat fingered my release script params. New version is uploaded, > will take a bit until it mirrors out to the public servers. > > Sorry for the inconveniance, > > tglx Thanks Thomas, the new patch applied fine. -- Regards, Philipp -- "Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner @ 2010-07-19 6:37 ` Barry Song 2010-07-13 18:04 ` Philipp Überbacher ` (2 subsequent siblings) 3 siblings, 0 replies; 54+ messages in thread From: Barry Song @ 2010-07-19 6:37 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users, John Stultz, Nick Piggin Hi Thomas, Just want to know when there will be released RT patch for 2.6.34? We have some tasks to patch RT to our local 2.6.34 tree. Thanks Barry On Tue, Jul 13, 2010 at 11:54 PM, Thomas Gleixner <tglx@linutronix.de> wrote: > We are pleased to announce the next update to our new preempt-rt > series. > > Changes from 2.6.33.5-rt23 to 2.6.33.5-rt24: > > 42edbcb: gianfar: Fix TX ring processing on SMP machines > faf3581: timer_stats: Convert table_lock to raw_spin_lock > 654e404: hvc_console: Fix race between hvc_close and hvc_remove > 09fd768: hvc_console: Fix race between hvc_close and hvc_remove > ea2d2a0: perf: Fix errors path in perf_output_begin() > 60bd946: KEYS: find_keyring_by_name() can gain access to a freed keyring > b5ac516: tracing: Update the comm field in the right variable in update_max_tr > 77cb7c1: lockdep: Reduce stack_trace usage > cee9ee0: powerpc: Disable sparse irq for RT > c7dec16: powerpc: Enable interrupts in do_signal() > > Changes from 2.6.33.5-rt24 to 2.6.33.5-rt25: > > ec646ea: vfs: Revert the scalability patches > > Changes from 2.6.33.5-rt26 to 2.6.33.6-rt26: > > 7e1af11: Merge git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.33.y > > Bulk of changes comes from the stable tree and from the big revert of > the VFS scalability patches. They looked promising, but the nasty > details bit us hard. We'll revisit them later. > > There are some pending issues: > - rtc_lock suspend/resume (working on a patch) > - futex requeue_pi (patch available, needs testing/confirmation) > - powerpc64 oddities (patch available, needs rework) > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.6-rt26 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt26.bz2 > > Enjoy ! > > tglx > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.6-rt26 @ 2010-07-19 6:37 ` Barry Song 0 siblings, 0 replies; 54+ messages in thread From: Barry Song @ 2010-07-19 6:37 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users, John Stultz, Nick Piggin Hi Thomas, Just want to know when there will be released RT patch for 2.6.34? We have some tasks to patch RT to our local 2.6.34 tree. Thanks Barry On Tue, Jul 13, 2010 at 11:54 PM, Thomas Gleixner <tglx@linutronix.de> wrote: > We are pleased to announce the next update to our new preempt-rt > series. > > Changes from 2.6.33.5-rt23 to 2.6.33.5-rt24: > > 42edbcb: gianfar: Fix TX ring processing on SMP machines > faf3581: timer_stats: Convert table_lock to raw_spin_lock > 654e404: hvc_console: Fix race between hvc_close and hvc_remove > 09fd768: hvc_console: Fix race between hvc_close and hvc_remove > ea2d2a0: perf: Fix errors path in perf_output_begin() > 60bd946: KEYS: find_keyring_by_name() can gain access to a freed keyring > b5ac516: tracing: Update the comm field in the right variable in update_max_tr > 77cb7c1: lockdep: Reduce stack_trace usage > cee9ee0: powerpc: Disable sparse irq for RT > c7dec16: powerpc: Enable interrupts in do_signal() > > Changes from 2.6.33.5-rt24 to 2.6.33.5-rt25: > > ec646ea: vfs: Revert the scalability patches > > Changes from 2.6.33.5-rt26 to 2.6.33.6-rt26: > > 7e1af11: Merge git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.33.y > > Bulk of changes comes from the stable tree and from the big revert of > the VFS scalability patches. They looked promising, but the nasty > details bit us hard. We'll revisit them later. > > There are some pending issues: > - rtc_lock suspend/resume (working on a patch) > - futex requeue_pi (patch available, needs testing/confirmation) > - powerpc64 oddities (patch available, needs rework) > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.6-rt26 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt26.bz2 > > Enjoy ! > > tglx > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.6-rt27 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner ` (2 preceding siblings ...) 2010-07-19 6:37 ` Barry Song @ 2010-07-31 13:33 ` Thomas Gleixner 2010-08-03 9:23 ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner 3 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-07-31 13:33 UTC (permalink / raw) To: LKML; +Cc: rt-users We are pleased to announce the next update to our new preempt-rt series. Changes from 2.6.33.6-rt26 to 2.6.33.6-rt27: d2decbf: v2.6.33.6-rt27 d972e60: UIO: Add a driver for Hilscher netX-based fieldbus cards 911d28c: dca: Fix fallout from raw_spinlock conversion 59fdcc0: powerpc: cpu-hotplug: Prevent softirq wakeup on wrong CPU 5805f5a: drivers/dca: Convert dca_lock to a raw spinlock 96c5397: cpu-hotplug: Prevent softirq wakeup on wrong CPU 8e7dbdf: cpu-hotplug: Don't wake up the desched thread from idle_task_exit() 5706af4: x86: mce: Convert cmci_discover_lock to raw_spinlock 5bbbedc: net: iptables: Fix xt_info locking 60f778f: suspend: Prevent might sleep splats 19491de: futex: Protect against pi_blocked_on corruption during requeue PI d69f558: sched: Fix TASK_WAKING vs fork deadlock 111abc8: sched: Make select_fallback_rq() cpuset friendly bb8eef7: sched: _cpu_down(): Don't play with current->cpus_allowed a325588: sched: sched_exec(): Remove the select_fallback_rq() logic 2d5a7c7: sched: move_task_off_dead_cpu(): Remove retry logic ae35e6f: sched: move_task_off_dead_cpu(): Take rq->lock around select_fallback_rq() a1e0f4a: sched: Kill the broken and deadlockable cpuset_lock/cpuset_cpus_allowed_locked code dd56c23: sched: set_cpus_allowed_ptr(): Don't use rq->migration_thread after unlock Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.6-rt27 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.6.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.6-rt27.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* [ANNOUNCE] 2.6.33.7-rt29 2010-07-31 13:33 ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner @ 2010-08-03 9:23 ` Thomas Gleixner 2010-12-21 13:52 ` Thomas Gleixner 0 siblings, 1 reply; 54+ messages in thread From: Thomas Gleixner @ 2010-08-03 9:23 UTC (permalink / raw) To: LKML; +Cc: rt-users We are pleased to announce the next update to our new preempt-rt series. Changes from 2.6.33.6-rt28 to 2.6.33.7-rt29: c88417f: Merge stable update Changes from 2.6.33.6-rt27 to 2.6.33.6-rt28: 8a990ab: printk: Restore irqs before calling release_console_mutex() Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.7-rt29 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7-rt29.bz2 Enjoy ! tglx ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-08-03 9:23 ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner @ 2010-12-21 13:52 ` Thomas Gleixner 2010-12-21 15:01 ` Mark Knecht ` (5 more replies) 0 siblings, 6 replies; 54+ messages in thread From: Thomas Gleixner @ 2010-12-21 13:52 UTC (permalink / raw) To: LKML; +Cc: rt-users We are pleased to announce the next update to our new preempt-rt series. Changes from 2.6.33.7-rt29 to 2.6.33.7.2-rt30: 5fed714: x86: stackprotector: Avoid random pool on rt 76bdf0c: x86: Convert mce timer to hrtimer a1026af: net: ebtables: Work around per cpu assumptions cfaca74: tracing: Add combined timer and wakeup latency histogram e94445b: rt: mm: fix kthreadd livelock in drain_local_pages_work a09b02c: powerpc/fsl-booke: Move loadcam_entry back to asm code to fix SMP ftrace a8b8812: AT91: SAM9G45 - add a separate clock entry for every single TC block 3cf7bf5: mm: make stack guard page logic use vm_prev pointer 901f364: mm: make the mlock() stack guard page checks stricter 498f700: mm: make the vma list be doubly linked e276f93c: mm: fix up some user-visible effects of the stack guard page a487cf3: mm: fix page table unmap for stack guard page properly 27ed5f7: mm: fix missing page table unmap for stack guard page failure case ed313b5: mm: keep a guard page below a grow-down stack segment bf18be0: drm: block userspace under allocating buffer and having drivers overwrite it (v2) 3609ee7: x86-64, compat: Retruncate rax after ia32 syscall entry tracing b2104d5: x86-64, compat: Test %rax for the syscall number, not %eax c2841fe: compat: Make compat_alloc_user_space() incorporate the access_ok() 85b5abf: ALSA: seq/oss - Fix double-free at error path of snd_seq_oss_open() 5741fe4: wireless extensions: fix kernel heap content leak 49aa1d9: net sched: fix some kernel memory leaks cd92f99: act_nat: use stack variable dc7dde7: tracing: Do not allow llseek to set_ftrace_filter 2da92b6: x86: Limit 32bit PAE memory to 16G 1389ed5: niu: Fix kernel buffer overflow for ETHTOOL_GRXCLSRLALL 4d4ea8b: KEYS: Fix bug in keyctl_session_to_parent() if parent has no session keyring 300f0c0: KEYS: Fix RCU no-lock warning in keyctl_session_to_parent() 300bc74: can: add limit for nframes and clean up signed/unsigned variables 88df886: NFS: Fix an Oops in the NFSv4 atomic open code 00b073d: staging/comedi: Fix type in semaphore conversion 327735e: perf: Provide kmap_atomic_direct for !CONFIG_HIGHMEM ddeca62: perf: Use kmap_atomic_direct d07d5cf: v2.6.33.7.1-rt29 e6c0211: ssb: Handle alternate SSPROM location 0bc60c2: ssb: fix NULL ptr deref when pcihost_wrapper is used 9ab4cde: ssb: Look for SPROM at different offset on higher rev CC 314beea: ssb: do not read SPROM if it does not exist 4ed85ce: Revert "ssb: Handle Netbook devices where the SPROM address is changed" d4202e4: drm/i915: Check overlay stride errata for i830 and i845 60853cb: KVM: MMU: flush remote tlbs when overwriting spte with different pfn fbbddb2: mac80211: avoid scheduling while atomic in mesh_rx_plink_frame 8d5c466: xen: drop xen_sched_clock in favour of using plain wallclock time e4de451: CIFS: Fix compile error with __init in cifs_init_dns_resolver() definition a9229e0: CIFS: Remove __exit mark from cifs_exit_dns_resolver() ab006e3: slow-work: use get_ref wrapper instead of directly calling get_ref 7485c1e: GFS2: rename causes kernel Oops 432cfce: SCSI: enclosure: fix error path - actually return ERR_PTR() on error 127524e: xfs: prevent swapext from operating on write-only files ab1b2be: cfg80211: don't get expired BSSes d377614: cfg80211: ignore spurious deauth efce9f4: iwlwifi: fix scan abort 8dc20bd: ath9k: fix yet another buffer leak in the tx aggregation code 9fd8aa6: ath9k: fix TSF after reset on AR913x 2089c7f: ath9k_hw: fix an off-by-one error in the PDADC boundaries calculation e10e4ec: ath9k: enable serialize_regmode for non-PCIE AR9160 cad9c43: 9p: strlen() doesn't count the terminator d2f1f93: e1000e: 82577/82578 PHY register access issues 8ed2a49: e1000e: don't inadvertently re-set INTX_DISABLE 257a4e8: amd64_edac: Correct scrub rate setting 3f5500c: amd64_edac: Fix DCT base address selector 8c0b0d6: parisc: pass through '\t' to early (iodc) console d7e94ae: arm/imx/gpio: add spinlock protection 42aa826: PARISC: led.c - fix potential stack overflow in led_proc_write() 49337d1: NFS: kswapd must not block in nfs_release_page 7486bb3: comedi: Uncripple 8255-based DIO subdevices 6388252: mm: fix ia64 crash when gcore reads gate area This is a rather large update with cherry-picks from the stable tree and quite a few fixes for long standing problems in the rt patch. Download locations: http://www.kernel.org/pub/linux/kernel/projects/rt/ Git release branch: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 Gitweb: http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 Information on the RT patch can be found at: http://rt.wiki.kernel.org/index.php/Main_Page To build the 2.6.33.7.2-rt30 tree, the following patches should be applied: http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 Enjoy ! This is probably the last update to the 33-rt series. The next release will be based on 2.6.37, but I'm still in the middle of a major overhaul of key compononents of the patch. This overhaul is necessary to make progress in mainlining the missing bits and pieces. I hope to have it ready not too long after the 2.6.37 mainline release, but no promise. At this point I want to say thanks to everyone who supported the development of the -rt patches with testing, bugfixes, stable backports etc. in the last years. I hope that I can rely on your help for the upcoming 37 release and the ongoing effort to merge the patch fully into the mainline. I wish you all a Merry Christmas and a Happy New Year! Thomas ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-21 13:52 ` Thomas Gleixner @ 2010-12-21 15:01 ` Mark Knecht 2010-12-21 15:48 ` Madovsky ` (4 subsequent siblings) 5 siblings, 0 replies; 54+ messages in thread From: Mark Knecht @ 2010-12-21 15:01 UTC (permalink / raw) To: Thomas Gleixner; +Cc: rt-users On Tue, Dec 21, 2010 at 5:52 AM, Thomas Gleixner <tglx@linutronix.de> wrote: > We are pleased to announce the next update to our new preempt-rt > series. <SNIP> > This is probably the last update to the 33-rt series. > > The next release will be based on 2.6.37, but I'm still in the middle > of a major overhaul of key compononents of the patch. This overhaul is > necessary to make progress in mainlining the missing bits and > pieces. I hope to have it ready not too long after the 2.6.37 mainline > release, but no promise. <SNIP> Thanks for both the update as well as info on the next kernel. I've been unable to use rt-sources for quite awhile as my new machine requires at least 2.6.36 for disk controller reasons. I'll look forward to getting back on the RT treadmill one day soon. Cheers, Mark ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-21 13:52 ` Thomas Gleixner 2010-12-21 15:01 ` Mark Knecht @ 2010-12-21 15:48 ` Madovsky 2010-12-21 16:39 ` Dennis Borgmann ` (3 subsequent siblings) 5 siblings, 0 replies; 54+ messages in thread From: Madovsky @ 2010-12-21 15:48 UTC (permalink / raw) To: linux-rt-users > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git > rt/2.6.33 > > Gitweb: > > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.7.2-rt30 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 > > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 > > Enjoy ! > > This is probably the last update to the 33-rt series. > > The next release will be based on 2.6.37, but I'm still in the middle > of a major overhaul of key compononents of the patch. This overhaul is > necessary to make progress in mainlining the missing bits and > pieces. I hope to have it ready not too long after the 2.6.37 mainline > release, but no promise. > > At this point I want to say thanks to everyone who supported the > development of the -rt patches with testing, bugfixes, stable > backports etc. in the last years. I hope that I can rely on your help > for the upcoming 37 release and the ongoing effort to merge the patch > fully into the mainline. > > I wish you all a Merry Christmas and a Happy New Year! > > Thomas > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" > in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Great job Thomas, my frustration is to not know enough C to help this amazing project. but I can try the last patch on Fedora10 64bits. MC and HNY Franck ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-21 13:52 ` Thomas Gleixner 2010-12-21 15:01 ` Mark Knecht 2010-12-21 15:48 ` Madovsky @ 2010-12-21 16:39 ` Dennis Borgmann 2010-12-22 16:38 ` Madovsky ` (2 subsequent siblings) 5 siblings, 0 replies; 54+ messages in thread From: Dennis Borgmann @ 2010-12-21 16:39 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users @Thomas et al.: Thank you so much for your work! It's really a amazing. Merry Christmas! Dennis Thomas Gleixner schrieb: > We are pleased to announce the next update to our new preempt-rt > series. > > Changes from 2.6.33.7-rt29 to 2.6.33.7.2-rt30: > > 5fed714: x86: stackprotector: Avoid random pool on rt > 76bdf0c: x86: Convert mce timer to hrtimer > a1026af: net: ebtables: Work around per cpu assumptions > cfaca74: tracing: Add combined timer and wakeup latency histogram > e94445b: rt: mm: fix kthreadd livelock in drain_local_pages_work > a09b02c: powerpc/fsl-booke: Move loadcam_entry back to asm code to fix SMP ftrace > a8b8812: AT91: SAM9G45 - add a separate clock entry for every single TC block > 3cf7bf5: mm: make stack guard page logic use vm_prev pointer > 901f364: mm: make the mlock() stack guard page checks stricter > 498f700: mm: make the vma list be doubly linked > e276f93c: mm: fix up some user-visible effects of the stack guard page > a487cf3: mm: fix page table unmap for stack guard page properly > 27ed5f7: mm: fix missing page table unmap for stack guard page failure case > ed313b5: mm: keep a guard page below a grow-down stack segment > bf18be0: drm: block userspace under allocating buffer and having drivers overwrite it (v2) > 3609ee7: x86-64, compat: Retruncate rax after ia32 syscall entry tracing > b2104d5: x86-64, compat: Test %rax for the syscall number, not %eax > c2841fe: compat: Make compat_alloc_user_space() incorporate the access_ok() > 85b5abf: ALSA: seq/oss - Fix double-free at error path of snd_seq_oss_open() > 5741fe4: wireless extensions: fix kernel heap content leak > 49aa1d9: net sched: fix some kernel memory leaks > cd92f99: act_nat: use stack variable > dc7dde7: tracing: Do not allow llseek to set_ftrace_filter > 2da92b6: x86: Limit 32bit PAE memory to 16G > 1389ed5: niu: Fix kernel buffer overflow for ETHTOOL_GRXCLSRLALL > 4d4ea8b: KEYS: Fix bug in keyctl_session_to_parent() if parent has no session keyring > 300f0c0: KEYS: Fix RCU no-lock warning in keyctl_session_to_parent() > 300bc74: can: add limit for nframes and clean up signed/unsigned variables > 88df886: NFS: Fix an Oops in the NFSv4 atomic open code > 00b073d: staging/comedi: Fix type in semaphore conversion > 327735e: perf: Provide kmap_atomic_direct for !CONFIG_HIGHMEM > ddeca62: perf: Use kmap_atomic_direct > d07d5cf: v2.6.33.7.1-rt29 > e6c0211: ssb: Handle alternate SSPROM location > 0bc60c2: ssb: fix NULL ptr deref when pcihost_wrapper is used > 9ab4cde: ssb: Look for SPROM at different offset on higher rev CC > 314beea: ssb: do not read SPROM if it does not exist > 4ed85ce: Revert "ssb: Handle Netbook devices where the SPROM address is changed" > d4202e4: drm/i915: Check overlay stride errata for i830 and i845 > 60853cb: KVM: MMU: flush remote tlbs when overwriting spte with different pfn > fbbddb2: mac80211: avoid scheduling while atomic in mesh_rx_plink_frame > 8d5c466: xen: drop xen_sched_clock in favour of using plain wallclock time > e4de451: CIFS: Fix compile error with __init in cifs_init_dns_resolver() definition > a9229e0: CIFS: Remove __exit mark from cifs_exit_dns_resolver() > ab006e3: slow-work: use get_ref wrapper instead of directly calling get_ref > 7485c1e: GFS2: rename causes kernel Oops > 432cfce: SCSI: enclosure: fix error path - actually return ERR_PTR() on error > 127524e: xfs: prevent swapext from operating on write-only files > ab1b2be: cfg80211: don't get expired BSSes > d377614: cfg80211: ignore spurious deauth > efce9f4: iwlwifi: fix scan abort > 8dc20bd: ath9k: fix yet another buffer leak in the tx aggregation code > 9fd8aa6: ath9k: fix TSF after reset on AR913x > 2089c7f: ath9k_hw: fix an off-by-one error in the PDADC boundaries calculation > e10e4ec: ath9k: enable serialize_regmode for non-PCIE AR9160 > cad9c43: 9p: strlen() doesn't count the terminator > d2f1f93: e1000e: 82577/82578 PHY register access issues > 8ed2a49: e1000e: don't inadvertently re-set INTX_DISABLE > 257a4e8: amd64_edac: Correct scrub rate setting > 3f5500c: amd64_edac: Fix DCT base address selector > 8c0b0d6: parisc: pass through '\t' to early (iodc) console > d7e94ae: arm/imx/gpio: add spinlock protection > 42aa826: PARISC: led.c - fix potential stack overflow in led_proc_write() > 49337d1: NFS: kswapd must not block in nfs_release_page > 7486bb3: comedi: Uncripple 8255-based DIO subdevices > 6388252: mm: fix ia64 crash when gcore reads gate area > > This is a rather large update with cherry-picks from the stable tree > and quite a few fixes for long standing problems in the rt patch. > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33 > > Gitweb: > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.7.2-rt30 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 > > Enjoy ! > > This is probably the last update to the 33-rt series. > > The next release will be based on 2.6.37, but I'm still in the middle > of a major overhaul of key compononents of the patch. This overhaul is > necessary to make progress in mainlining the missing bits and > pieces. I hope to have it ready not too long after the 2.6.37 mainline > release, but no promise. > > At this point I want to say thanks to everyone who supported the > development of the -rt patches with testing, bugfixes, stable > backports etc. in the last years. I hope that I can rely on your help > for the upcoming 37 release and the ongoing effort to merge the patch > fully into the mainline. > > I wish you all a Merry Christmas and a Happy New Year! > > Thomas > -- > To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-21 13:52 ` Thomas Gleixner ` (2 preceding siblings ...) 2010-12-21 16:39 ` Dennis Borgmann @ 2010-12-22 16:38 ` Madovsky 2010-12-22 20:20 ` Remy Bohmer 2010-12-24 22:36 ` Fernando Lopez-Lezcano 5 siblings, 0 replies; 54+ messages in thread From: Madovsky @ 2010-12-22 16:38 UTC (permalink / raw) To: rt-users > We are pleased to announce the next update to our new preempt-rt > series. > > Changes from 2.6.33.7-rt29 to 2.6.33.7.2-rt30: > > > Download locations: > > http://www.kernel.org/pub/linux/kernel/projects/rt/ > > Git release branch: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git > rt/2.6.33 > > Gitweb: > > http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33 > > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.7.2-rt30 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 > > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 > Seems to work perfectly on Fedora10 64bits. Thanks Franck ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-21 13:52 ` Thomas Gleixner ` (3 preceding siblings ...) 2010-12-22 16:38 ` Madovsky @ 2010-12-22 20:20 ` Remy Bohmer 2010-12-24 22:36 ` Fernando Lopez-Lezcano 5 siblings, 0 replies; 54+ messages in thread From: Remy Bohmer @ 2010-12-22 20:20 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users Hi Thomas, 2010/12/21 Thomas Gleixner <tglx@linutronix.de>: > > At this point I want to say thanks to everyone who supported the > development of the -rt patches with testing, bugfixes, stable > backports etc. in the last years. First of all: Thank YOU for maintaining the RT-patch and the huge amount of effort you put into it! > I hope that I can rely on your help > for the upcoming 37 release and the ongoing effort to merge the patch > fully into the mainline. >From my side: I will test this new patch next Friday on ARM/at91, and when 2.6.37-rt becomes available: I am happy to test that one also. > I wish you all a Merry Christmas and a Happy New Year! Merry Christmas and a Happy New Year to you and anyone else too! Kind regards, Remy ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-21 13:52 ` Thomas Gleixner ` (4 preceding siblings ...) 2010-12-22 20:20 ` Remy Bohmer @ 2010-12-24 22:36 ` Fernando Lopez-Lezcano 2010-12-31 19:56 ` Fernando Lopez-Lezcano 5 siblings, 1 reply; 54+ messages in thread From: Fernando Lopez-Lezcano @ 2010-12-24 22:36 UTC (permalink / raw) To: Thomas Gleixner; +Cc: LKML, rt-users On 12/21/2010 05:52 AM, Thomas Gleixner wrote: > We are pleased to announce the next update to our new preempt-rt > series. > ... > Information on the RT patch can be found at: > > http://rt.wiki.kernel.org/index.php/Main_Page > > To build the 2.6.33.7.2-rt30 tree, the following patches should be > applied: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 > http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 > > Enjoy ! I'm testing it right now and it does seem to have fixed some stuff, for example I don't see any more errors when waking up from a sleep state. Anyway, I'll let you know of any problems... Thanks a lot! (and also good to know about the plans for 2.6.37.x rt!) -- Fernando ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 2010-12-24 22:36 ` Fernando Lopez-Lezcano @ 2010-12-31 19:56 ` Fernando Lopez-Lezcano 0 siblings, 0 replies; 54+ messages in thread From: Fernando Lopez-Lezcano @ 2010-12-31 19:56 UTC (permalink / raw) To: Thomas Gleixner; +Cc: Fernando Lopez-Lezcano, LKML, rt-users On 12/24/2010 02:36 PM, Fernando Lopez-Lezcano wrote: > On 12/21/2010 05:52 AM, Thomas Gleixner wrote: >> We are pleased to announce the next update to our new preempt-rt >> series. >> ... >> Information on the RT patch can be found at: >> >> http://rt.wiki.kernel.org/index.php/Main_Page >> >> To build the 2.6.33.7.2-rt30 tree, the following patches should be >> applied: >> >> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 >> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 >> >> >> Enjoy ! > > I'm testing it right now and it does seem to have fixed some stuff, for > example I don't see any more errors when waking up from a sleep state. > Anyway, I'll let you know of any problems... So far so good... > Thanks a lot! (and also good to know about the plans for 2.6.37.x rt!) A question: I need to find out the pid of the irq process that handles a particular audio device from the information available from udev (to dynamically change its rt priority). AFAICT that is not really possible. I can find the irq number easily but if there is more than one device using that number then I'm sort of stuck. The naming of the irq processes for each card appear to be hardwired strings in the driver code that do not necessarily correspond to any other name in the driver itself. Is there a connection between the two somewhere in /sys, /proc or anywhere else that I'm missing? (ie: which interrupt process corresponds to which driver?) -- Fernando ^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [ANNOUNCE] 2.6.33.7-rt29 @ 2010-12-31 19:56 ` Fernando Lopez-Lezcano 0 siblings, 0 replies; 54+ messages in thread From: Fernando Lopez-Lezcano @ 2010-12-31 19:56 UTC (permalink / raw) To: Thomas Gleixner; +Cc: Fernando Lopez-Lezcano, LKML, rt-users On 12/24/2010 02:36 PM, Fernando Lopez-Lezcano wrote: > On 12/21/2010 05:52 AM, Thomas Gleixner wrote: >> We are pleased to announce the next update to our new preempt-rt >> series. >> ... >> Information on the RT patch can be found at: >> >> http://rt.wiki.kernel.org/index.php/Main_Page >> >> To build the 2.6.33.7.2-rt30 tree, the following patches should be >> applied: >> >> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.7.tar.bz2 >> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.7.2-rt30.bz2 >> >> >> Enjoy ! > > I'm testing it right now and it does seem to have fixed some stuff, for > example I don't see any more errors when waking up from a sleep state. > Anyway, I'll let you know of any problems... So far so good... > Thanks a lot! (and also good to know about the plans for 2.6.37.x rt!) A question: I need to find out the pid of the irq process that handles a particular audio device from the information available from udev (to dynamically change its rt priority). AFAICT that is not really possible. I can find the irq number easily but if there is more than one device using that number then I'm sort of stuck. The naming of the irq processes for each card appear to be hardwired strings in the driver code that do not necessarily correspond to any other name in the driver itself. Is there a connection between the two somewhere in /sys, /proc or anywhere else that I'm missing? (ie: which interrupt process corresponds to which driver?) -- Fernando ^ permalink raw reply [flat|nested] 54+ messages in thread
end of thread, other threads:[~2010-12-31 19:56 UTC | newest] Thread overview: 54+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner 2010-02-24 22:38 ` Peter Zijlstra 2010-02-25 22:56 ` Peter Zijlstra 2010-02-26 19:44 ` Dan Carpenter 2010-02-27 8:10 ` Thomas Gleixner 2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner 2010-02-27 9:25 ` Xavier Miller 2010-02-27 9:25 ` Xavier Miller 2010-02-27 10:10 ` GeunSik Lim 2010-02-27 11:53 ` Thomas Gleixner 2010-03-02 21:25 ` Fernando Lopez-Lezcano 2010-03-02 21:53 ` Thomas Gleixner 2010-02-27 9:50 ` GeunSik Lim 2010-02-27 9:50 ` GeunSik Lim 2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner 2010-03-12 12:17 ` 2.6.33-rt6 on Beagle Chatterjee, Amit 2010-03-15 9:20 ` Uwe Kleine-König 2010-03-15 11:23 ` What's the best way to create an embedded version of PREEMPT_RT Linux ? Armin Steinhoff 2010-03-21 11:06 ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner 2010-04-07 14:24 ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner 2010-04-27 15:52 ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner 2010-04-30 10:00 ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner 2010-05-02 19:18 ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner 2010-06-09 16:44 ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner 2010-06-09 21:31 ` Will Schmidt 2010-06-10 6:07 ` Thomas Gleixner 2010-06-10 15:56 ` Will Schmidt 2010-06-10 16:05 ` Darcy L. Watkins 2010-06-14 13:33 ` Thomas Gleixner 2010-06-14 13:34 ` Thomas Gleixner 2010-06-14 15:35 ` Will Schmidt 2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner 2010-07-13 16:52 ` Dhaval Giani 2010-07-13 18:04 ` Philipp Überbacher 2010-07-13 19:13 ` Darcy L. Watkins 2010-07-13 19:23 ` Philipp Überbacher 2010-07-14 13:47 ` Thomas Gleixner 2010-07-14 13:57 ` Ng Oon-Ee 2010-07-14 14:27 ` John Kacur [not found] ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com> 2010-07-15 5:25 ` Yang Jian 2010-07-15 11:45 ` Philipp Überbacher 2010-07-19 6:37 ` Barry Song 2010-07-19 6:37 ` Barry Song 2010-07-31 13:33 ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner 2010-08-03 9:23 ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner 2010-12-21 13:52 ` Thomas Gleixner 2010-12-21 15:01 ` Mark Knecht 2010-12-21 15:48 ` Madovsky 2010-12-21 16:39 ` Dennis Borgmann 2010-12-22 16:38 ` Madovsky 2010-12-22 20:20 ` Remy Bohmer 2010-12-24 22:36 ` Fernando Lopez-Lezcano 2010-12-31 19:56 ` Fernando Lopez-Lezcano 2010-12-31 19:56 ` Fernando Lopez-Lezcano
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.