Re: [RESEND PATCH v5 2/5] arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo

2020-02-21 Thread Amit Kachhap
Hi Bhupesh, On 1/13/20 5:44 PM, Bhupesh Sharma wrote: Hi James, On 01/11/2020 12:30 AM, Dave Anderson wrote: - Original Message - Hi Bhupesh, On 25/12/2019 19:01, Bhupesh Sharma wrote: On 12/12/2019 04:02 PM, James Morse wrote: On 29/11/2019 19:59, Bhupesh Sharma wrote: vabits_ac

more barriers: Re: [PATCH 1/2] printk: add lockless buffer

2020-02-21 Thread Petr Mladek
Hi, the new full barrier in desc_reserve() made me to think more about the existing ones. If I get it correctly, the used cmpxchg_relaxed() variants does not provide full barriers. They are just able to prevent parallel manipulation of the modified variable. Because of this, I think that we need

misc nits Re: [PATCH 1/2] printk: add lockless buffer

2020-02-21 Thread Petr Mladek
Hi, there are few more small things that catched my eyes during review. They are from the nits deparment. On Tue 2020-01-28 17:25:47, John Ogness wrote: > Introduce a multi-reader multi-writer lockless ringbuffer for storing > the kernel log messages. Readers and writers may use their API from >

RE: [PATCH] makedumpfile: cope with not-present mem section

2020-02-21 Thread 萩尾 一仁
-Original Message- > Hi, Kazu. > > For now, I would keep Pingfan's patch as is. I decided to test some other > kernels, like 3.16 and 4.9 without commit > 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4. > > So, they would be valid for the first iteration and invalid for the second, > just like