[PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control

2017-03-09 Thread Andrew Banman
The location of the ERROR and BUSY status bits depends on the descriptor index, i.e. the CPU, of the message. Since this index does not change, there is no need to calculate the mmr and index location during message processing. The less work we do in the hot path the better. Add status_mmr and

[PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control

2017-03-09 Thread Andrew Banman
The location of the ERROR and BUSY status bits depends on the descriptor index, i.e. the CPU, of the message. Since this index does not change, there is no need to calculate the mmr and index location during message processing. The less work we do in the hot path the better. Add status_mmr and

Re: [PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control

2017-02-27 Thread Andrew Banman
The above patch has a conflict in wait_completion with the enumerated UV_BAU symbol because I let an old version of the patch creep into the set. Following is the correct version. Sorry about that! Andrew

Re: [PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control

2017-02-27 Thread Andrew Banman
The above patch has a conflict in wait_completion with the enumerated UV_BAU symbol because I let an old version of the patch creep into the set. Following is the correct version. Sorry about that! Andrew

[PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control

2017-02-17 Thread Andrew Banman
The location of the ERROR and BUSY status bits depends on the descriptor index, i.e. the CPU, of the message. Since this index does not change, there is no need to calculate the MMR and index location during message processing. The less work we do in the hot path the better. Add status_mmr and

[PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control

2017-02-17 Thread Andrew Banman
The location of the ERROR and BUSY status bits depends on the descriptor index, i.e. the CPU, of the message. Since this index does not change, there is no need to calculate the MMR and index location during message processing. The less work we do in the hot path the better. Add status_mmr and