Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1363032
| From | Heiko Carstens <heiko.carstens@de.ibm.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock |
| Date | 2016-03-22 22:50 +0100 |
| Message-ID | <rfClA-23H-11@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <rftBE-4jp-19@gated-at.bofh.it> <rfuxH-4WW-3@gated-at.bofh.it> <rfv0L-5cK-23@gated-at.bofh.it> <rfvN7-5Sf-3@gated-at.bofh.it> <rfxFg-7gW-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Mar 22, 2016 at 05:41:22PM +0100, Peter Zijlstra wrote: > On Tue, Mar 22, 2016 at 03:45:37PM +0100, Heiko Carstens wrote: > > > Sure, looks nice and makes a lot of sense. And the text looks a bit familiar > > to me ;) > > > > Could you provide From: and Signed-off-by: lines? > > Of course, find below. > > --- > Subject: s390: Clarify pagefault interrupt > From: Peter Zijlstra <peterz@infradead.org> > > While looking at set_task_state() users I stumbled over the s390 pfault > interrupt code. Since Heiko provided a great explanation on how it > worked, I figured we ought to preserve this. > > Also make a few little tweaks to the code to aid in readability and > explicitly comment the unusual blocking scheme. > > Based-on-text-by: Heiko Carstens <heiko.carstens@de.ibm.com> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> > --- > arch/s390/mm/fault.c | 44 ++++++++++++++++++++++++++++++++++++-------- > 1 file changed, 36 insertions(+), 8 deletions(-) Applied, with some whitespace changes from me. Thank you!
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Davidlohr Bueso <dave@stgolabs.net> - 2016-03-21 19:20 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Peter Zijlstra <peterz@infradead.org> - 2016-03-22 11:30 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-03-22 12:50 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Peter Zijlstra <peterz@infradead.org> - 2016-03-22 13:30 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-03-22 14:30 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Peter Zijlstra <peterz@infradead.org> - 2016-03-22 15:00 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-03-22 15:50 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Peter Zijlstra <peterz@infradead.org> - 2016-03-22 17:50 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-03-22 22:50 +0100
Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock Davidlohr Bueso <dave@stgolabs.net> - 2016-03-25 03:40 +0100
csiph-web