qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>, Fan Ni <fan.ni@samsung.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	<linux-cxl@lore.kernel.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1 1/2] hw/cxl/device: read from register values in mdev_reg_read()
Date: Thu, 30 Nov 2023 16:32:53 +0000	[thread overview]
Message-ID: <20231130163253.00002140@Huawei.com> (raw)
In-Reply-To: <20231127202702.zkqomoapz2iprpra@offworld>

On Mon, 27 Nov 2023 12:27:02 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:

> On Mon, 27 Nov 2023, Hyeonggon Yoo wrote:
> 
> >In the current mdev_reg_read() implementation, it consistently returns
> >that the Media Status is Ready (01b). This was fine until commit
> >25a52959f99d ("hw/cxl: Add support for device sanitation") because the
> >media was presumed to be ready.
> >
> >However, as per the CXL 3.0 spec "8.2.9.8.5.1 Sanitize (Opcode 4400h)",
> >during sanitation, the Media State should be set to Disabled (11b). The
> >mentioned commit correctly sets it to Disabled, but mdev_reg_read()
> >still returns Media Status as Ready.
> >
> >To address this, update mdev_reg_read() to read register values instead
> >of returning dummy values.
> >
> >Fixes: commit 25a52959f99d ("hw/cxl: Add support for device sanitation")
> >Signed-off-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>  
> 
> Looks good, thanks.
> 
> Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
> 
> In addition how about the following to further robustify?
>    - disallow certain incoming cci cmd when media is disabled
>    - deal with memory reads/writes when media is disabled
>    - make __toggle_media() a nop when passed value is already set
>    - play nice with arm64 uses little endian reads and writes (this
>      should be extended to all of mbox/cci of course).
This one you've lost me on.  Arm64 and x86 both little endian.

If you mean generally harden the code we haven't fixed up for
big endian systems then fair enough - that indeed needs doing.
Tricky to be sure we got it all right though unless we have a big
endian arch to test on...

Jonathan



  parent reply	other threads:[~2023-11-30 16:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 10:58 [PATCH v1 0/2] A Fixup for "QEMU: CXL mailbox rework and features (Part 1)" Hyeonggon Yoo
2023-11-27 10:58 ` [PATCH v1 1/2] hw/cxl/device: read from register values in mdev_reg_read() Hyeonggon Yoo
2023-11-27 20:27   ` Davidlohr Bueso
2023-11-28  0:42     ` Hyeonggon Yoo
2023-11-28  5:42       ` Davidlohr Bueso
2023-11-30 16:32     ` Jonathan Cameron via [this message]
2023-12-04  3:38       ` Davidlohr Bueso
2023-11-27 10:58 ` [PATCH v1 2/2] hw/mem/cxl_type3: allocate more vectors for MSI-X Hyeonggon Yoo
2023-11-27 17:53   ` Davidlohr Bueso
2023-11-28  0:27     ` Hyeonggon Yoo
2023-11-28 12:46       ` Jonathan Cameron via
2023-11-30  5:53         ` Hyeonggon Yoo
2023-11-28  7:31 ` [PATCH v1 0/2] A Fixup for "QEMU: CXL mailbox rework and features (Part 1)" Michael S. Tsirkin
2023-11-29  7:40   ` Hyeonggon Yoo

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=20231130163253.00002140@Huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=42.hyeyoo@gmail.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.com \
    --cc=linux-cxl@lore.kernel.org \
    --cc=mst@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 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).