qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Yuquan Wang <wangyuquan1236@phytium.com.cn>
Cc: <dave.jiang@intel.com>, <fan.ni@samsung.com>,
	<ira.weiny@intel.com>, <linux-cxl@vger.kernel.org>,
	<linuxarm@huawei.com>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v9 0/7]  QEMU CXL Provide mock CXL events and irq support
Date: Fri, 15 Mar 2024 10:24:15 +0000	[thread overview]
Message-ID: <20240315102415.00004476@Huawei.com> (raw)
In-Reply-To: <20240315015228.307512-1-wangyuquan1236@phytium.com.cn>

On Fri, 15 Mar 2024 09:52:28 +0800
Yuquan Wang <wangyuquan1236@phytium.com.cn> wrote:

> Hello, Jonathan
> 
> When during the test of qmps of CXL events like "cxl-inject-general-media-event", 
> I am confuesd about the argument "flags". According to "qapi/cxl.json" in qemu, 
> this argument represents "Event Record Flags" in Common Event Record Format.
> However, it seems like the specific 'Event Record Severity' in this field can be
> different from the value of 'Event Status' in "Event Status Register". 
> 
> For instance (take an injection example in the coverlatter):
> 
> { "execute": "cxl-inject-general-media-event",
>     "arguments": {
>         "path": "/machine/peripheral/cxl-mem0",
>         "log": "informational",
>         "flags": 1,
>         "dpa": 1000,
>         "descriptor": 3,
>         "type": 3,
>         "transaction-type": 192,
>         "channel": 3,
>         "device": 5,
>         "component-id": "iras mem"
>     }}
> 
> In my understanding, the 'Event Status' is informational and the 
> 'Event Record Severity' is Warning event, which means these two arguments are
> independent of each other. Is my understanding correct?

The event status registers dictates the notification path (which log).
So I think that's "informational" here.

Whereas flags is about the specific error. One case where they might be
different is where the Related Event Record Handle is set.
An error might be reported as
1) Several things that were non fatal (each with their own record)
2) In combination they result in a fatal situation (also has it's own record).

The QEMU injection shouldn't restrict these combinations more than the spec
does (which is not at all!).

This same disconnect in error severity is seen in UEFI CPER records for example
where there is a containing record with one severity field, but more specific
parts of record can have lower (or in theory higher) severity.

Jonathan


> 
> Many thanks
> Yuquan
> 



      reply	other threads:[~2024-03-15 10:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 13:35 [PATCH v9 0/7] QEMU CXL Provide mock CXL events and irq support Jonathan Cameron via
2023-05-30 13:35 ` [PATCH v9 1/7] hw/cxl/events: Add event status register Jonathan Cameron via
2023-05-30 13:35 ` [PATCH v9 2/7] hw/cxl: Move CXLRetCode definition to cxl_device.h Jonathan Cameron via
2023-05-30 13:35 ` [PATCH v9 3/7] hw/cxl/events: Wire up get/clear event mailbox commands Jonathan Cameron via
2023-05-30 13:36 ` [PATCH v9 4/7] hw/cxl/events: Add event interrupt support Jonathan Cameron via
2023-05-30 13:36 ` [PATCH v9 5/7] hw/cxl/events: Add injection of General Media Events Jonathan Cameron via
2023-05-30 13:36 ` [PATCH v9 6/7] hw/cxl/events: Add injection of DRAM events Jonathan Cameron via
2023-05-30 13:36 ` [PATCH v9 7/7] hw/cxl/events: Add injection of Memory Module Events Jonathan Cameron via
2024-03-15  1:52 ` [PATCH v9 0/7] QEMU CXL Provide mock CXL events and irq support Yuquan Wang
2024-03-15 10:24   ` Jonathan Cameron via [this message]

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=20240315102415.00004476@Huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=dave.jiang@intel.com \
    --cc=fan.ni@samsung.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=wangyuquan1236@phytium.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).