All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: qemu-devel@nongnu.org, "Michael Tsirkin" <mst@redhat.com>,
	"Fan Ni" <fan.ni@samsung.com>,
	linux-cxl@vger.kernel.org, linuxarm@huawei.com,
	"Ira Weiny" <ira.weiny@intel.com>,
	"Michael Roth" <michael.roth@amd.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Dave Jiang" <dave.jiang@intel.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Mike Maslenkin" <mike.maslenkin@gmail.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v8 7/7] hw/cxl/events: Add injection of Memory Module Events
Date: Sat, 27 May 2023 07:48:40 +0200	[thread overview]
Message-ID: <87wn0u4953.fsf@pond.sub.org> (raw)
In-Reply-To: <20230526171304.1613-8-Jonathan.Cameron@huawei.com> (Jonathan Cameron's message of "Fri, 26 May 2023 18:13:04 +0100")

Jonathan Cameron <Jonathan.Cameron@huawei.com> writes:

> These events include a copy of the device health information at the
> time of the event. Actually using the emulated device health would
> require a lot of controls to manipulate that state.  Given the aim
> of this injection code is to just test the flows when events occur,
> inject the contents of the device health state as well.
>
> Future work may add more sophisticate device health emulation
> including direct generation of these records when events occur
> (such as a temperature threshold being crossed).  That does not
> reduce the usefulness of this more basic generation of the events.
>
> Acked-by: Markus Armbruster <armbru@redhat.com>
> Reviewed-by: Fan Ni <fan.ni@samsung.com>
> Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>  qapi/cxl.json               | 53 +++++++++++++++++++++++++++++++
>  include/hw/cxl/cxl_events.h | 19 ++++++++++++
>  hw/mem/cxl_type3.c          | 62 +++++++++++++++++++++++++++++++++++++
>  hw/mem/cxl_type3_stubs.c    | 12 +++++++
>  4 files changed, 146 insertions(+)
>
> diff --git a/qapi/cxl.json b/qapi/cxl.json
> index 36bf9fa202..a2e1280573 100644
> --- a/qapi/cxl.json
> +++ b/qapi/cxl.json
> @@ -140,6 +140,59 @@
>              '*column': 'uint16', '*correction-mask': [ 'uint64' ]
>             }}
>  
> +##
> +# @cxl-inject-memory-module-event:
> +#
> +# Inject an event record for a Memory Module Event (CXL r3.0
> +# 8.2.9.2.1.3). This event includes a copy of the Device Health

Two spaces between sentences for consistency, please.

> +# info at the time of the event.
> +#
> +# @path: CXL type 3 device canonical QOM path
> +#
> +# @log: Event Log to add the event to
> +#
> +# @flags: Event Record Flags.  See CXL r3.0 Table 8-42 Common Event
> +#     Record Format, Event Record Flags for subfield definitions.
> +#
> +# @type: Device Event Type.  See CXL r3.0 Table 8-45 Memory Module
> +#     Event Record for bit definitions for bit definiions.
> +#
> +# @health-status: Overall health summary bitmap.  See CXL r3.0 Table
> +#     8-100 Get Health Info Output Payload, Health Status for bit
> +#     definitions.
> +#
> +# @media-status: Overall media health summary.  See CXL r3.0 Table
> +#     8-100 Get Health Info Output Payload, Media Status for bit
> +#     definitions.
> +#
> +# @additional-status: See CXL r3.0 Table 8-100 Get Health Info Output
> +#     Payload, Additional Status for subfield definitions.
> +#
> +# @life-used: Percentage (0-100) of factory expected life span.
> +#
> +# @temperature: Device temperature in degrees Celsius.
> +#
> +# @dirty-shutdown-count: Number of times the device has been unable
> +#     to determine whether data loss may have occurred.
> +#
> +# @corrected-volatile-error-count: Total number of correctable errors
> +#     in volatile memory.
> +#
> +# @corrected-persistent-error-count: Total number correctable errors

Total number of correctable errors

> +#     in persistent memory
> +#
> +# Since: 8.1
> +##
> +{ 'command': 'cxl-inject-memory-module-event',
> +  'data': { 'path': 'str', 'log': 'CxlEventLog', 'flags' : 'uint8',
> +            'type': 'uint8', 'health-status': 'uint8',
> +            'media-status': 'uint8', 'additional-status': 'uint8',
> +            'life-used': 'uint8', 'temperature' : 'int16',
> +            'dirty-shutdown-count': 'uint32',
> +            'corrected-volatile-error-count': 'uint32',
> +            'corrected-persistent-error-count': 'uint32'
> +            }}
> +
>  ##
>  # @cxl-inject-poison:
>  #

Neither these nitpicks nor the one on PATCH 5 calls for a respin.
Simply fix them in the PR.  Thanks!

[...]



  reply	other threads:[~2023-05-27  5:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 17:12 [PATCH v8 0/7] QEMU CXL Provide mock CXL events and irq support Jonathan Cameron
2023-05-26 17:12 ` Jonathan Cameron via
2023-05-26 17:12 ` [PATCH v8 1/7] hw/cxl/events: Add event status register Jonathan Cameron
2023-05-26 17:12   ` Jonathan Cameron via
2023-05-26 17:12 ` [PATCH v8 2/7] hw/cxl: Move CXLRetCode definition to cxl_device.h Jonathan Cameron
2023-05-26 17:12   ` Jonathan Cameron via
2023-05-26 17:13 ` [PATCH v8 3/7] hw/cxl/events: Wire up get/clear event mailbox commands Jonathan Cameron
2023-05-26 17:13   ` Jonathan Cameron via
2023-05-26 17:13 ` [PATCH v8 4/7] hw/cxl/events: Add event interrupt support Jonathan Cameron
2023-05-26 17:13   ` Jonathan Cameron via
2023-05-26 17:13 ` [PATCH v8 5/7] hw/cxl/events: Add injection of General Media Events Jonathan Cameron
2023-05-26 17:13   ` Jonathan Cameron via
2023-05-27  5:47   ` Markus Armbruster
2023-05-26 17:13 ` [PATCH v8 6/7] hw/cxl/events: Add injection of DRAM events Jonathan Cameron
2023-05-26 17:13   ` Jonathan Cameron via
2023-05-26 17:13 ` [PATCH v8 7/7] hw/cxl/events: Add injection of Memory Module Events Jonathan Cameron
2023-05-26 17:13   ` Jonathan Cameron via
2023-05-27  5:48   ` Markus Armbruster [this message]
2023-05-30 13:33     ` Jonathan Cameron
2023-05-30 13:33       ` Jonathan Cameron via

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=87wn0u4953.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=berrange@redhat.com \
    --cc=dave.jiang@intel.com \
    --cc=eblake@redhat.com \
    --cc=fan.ni@samsung.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mike.maslenkin@gmail.com \
    --cc=mst@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 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.