mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Banman <abanman@hpe.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>
Cc: <abanman@hpe.com>, <akpm@linux-foundation.org>,
	<mike.travis@hpe.com>, <rja@hpe.com>, <sivanich@hpe.com>,
	<x86@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 0/6] x86/platform/uv/BAU: UV4 message completion and initialization updates
Date: Wed, 8 Mar 2017 19:42:39 -0600	[thread overview]
Message-ID: <7b9ebd26-c623-807e-4786-8c6f79ed6909@hpe.com> (raw)
In-Reply-To: <1487369197-79054-1-git-send-email-abanman@hpe.com>

Hi Ingo and Thomas,

Are these patches acceptable to you? We want to get these upstream as soon as 
possible, so please send along any more comments you have. If you're annoyed by 
the format of the emails just let me know and I'll resubmit.

Thank you,

Andrew

On 2/17/17 4:06 PM, Andrew Banman wrote:
> The following patch series adds the necessary functionality to make the BAU
> on UV4 operational. The purpose of these patches is to implement the correct
> message completion logic on UV4. Also included is a bug fix to add a field
> to the INTD payload. This is needed to verify the source of each message.
>
> As of this patch set, the BAU operates without errors and performance tests
> show TLB shootdowns take up to 42% less time with the BAU enabled.
>
> The patches are summarized as follows:
>
> (1) Populate a message payload field to verify messages at the destination.
>     Without this verification, the destination agent triggers a HUB error,
>     resulting in an NMI.
>
>     [PATCH 1/6] x86/platform/uv/BAU: Add uv_bau_version enumerated
>     [PATCH v2 2/6] x86/platform/uv/BAU: Add payload descriptor qualifier
>
>     This bug fix is included at the start of the series to avoid conflicts
>     in a code path shared by the rest of the series.
>
> (2) Make the wait_completion routine part of the bau_operations interface,
>     and add a uv4_wait_completion routine to employ new completion logic.
>
>     The message completion logic for previous generations relies on software-
>     defined timeouts that are not implemented on UV4. Without these patches,
>     the BAU driver on UV4 erroneously identifies a UV2-WAR timeout during
>     normal operation.
>
>     [PATCH 3/6] x86/platform/uv/BAU: Cleanup bau_operations declaration
>     [PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to
>     [PATCH v2 5/6] x86/platform/uv/BAU: Add wait_completion to
>     [PATCH v2 6/6] x86/platform/uv/BAU: Implement uv4_wait_completion with
>
>
> Please see the commit messages for details on the motivation and content of
> each patch.
>
> Thank you,
>
> Andrew Banman
> HPE, Linux Kernel Engineer
> <abanman@hpe.com>
>

  parent reply	other threads:[~2017-03-09  1:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 22:06 Andrew Banman
2017-02-17 22:06 ` [PATCH 1/6] x86/platform/uv/BAU: Add uv_bau_version enumerated constants Andrew Banman
2017-02-17 22:06 ` [PATCH v2 2/6] x86/platform/uv/BAU: Add payload descriptor qualifier Andrew Banman
2017-02-17 22:06 ` [PATCH 3/6] x86/platform/uv/BAU: Cleanup bau_operations declaration and instances Andrew Banman
2017-02-17 22:06 ` [PATCH 4/6] x86/platform/uv/BAU: Add status mmr location fields to bau_control Andrew Banman
2017-02-27 19:14   ` Andrew Banman
2017-02-27 19:14     ` [PATCH v2 " Andrew Banman
2017-02-17 22:06 ` [PATCH v2 5/6] x86/platform/uv/BAU: Add wait_completion to bau_operations Andrew Banman
2017-02-27 19:26   ` Andrew Banman
2017-02-27 19:26     ` [PATCH v3 " Andrew Banman
2017-02-17 22:06 ` [PATCH v2 6/6] x86/platform/uv/BAU: Implement uv4_wait_completion with read_status Andrew Banman
2017-03-09  1:42 ` Andrew Banman [this message]
2017-03-09 13:22   ` [PATCHv2 0/6] x86/platform/uv/BAU: UV4 message completion and initialization updates Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7b9ebd26-c623-807e-4786-8c6f79ed6909@hpe.com \
    --to=abanman@hpe.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=mingo@redhat.com \
    --cc=rja@hpe.com \
    --cc=sivanich@hpe.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®