From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Markus Armbruster <armbru@redhat.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>,
"Alison Schofield" <alison.schofield@intel.com>,
"Michael Roth" <michael.roth@amd.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Dave Jiang" <dave.jiang@intel.com>,
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 v5 5/7] hw/cxl/events: Add injection of General Media Events
Date: Wed, 24 May 2023 10:11:58 +0100 [thread overview]
Message-ID: <20230524101158.0000579d@huawei.com> (raw)
In-Reply-To: <87ttw35i6q.fsf@pond.sub.org>
On Tue, 23 May 2023 14:46:37 +0200
Markus Armbruster <armbru@redhat.com> wrote:
> Jonathan Cameron <Jonathan.Cameron@Huawei.com> writes:
>
> >> >
> >> >> > +#
> >> >> > +# Inject an event record for a General Media Event (CXL r3.0 8.2.9.2.1.1)
> >> >>
> >> >> What's "CXL r3.0", and where could a reader find it?
> >> >
> >> > We have docs in docs/system/devices/cxl.rst that include the consortium
> >> > website which has download links on the front page.
> >>
> >> cxl.rst has
> >>
> >> References
> >> ----------
> >>
> >> - Consortium website for specifications etc:
> >> http://www.computeexpresslink.org
> >> - Compute Express link Revision 2 specification, October 2020
> >> - CEDT CFMWS & QTG _DSM ECN May 2021
> >>
> >> Should the second reference be updated to 3.0? Exact title seems to be
> >> "The Compute Express Link™ (CXL™) 3.0 specification". Not sure we need
> >> to bother with the "™" in a reference.
> >
> > Yes. On the todo list is to update all the references to latest released
> > specification because old ones are unobtainable to non consortium members
> > unless they grabbed a copy in the past.
> >
> > Annoyingly this will be a repeated requirement as new spec versions are released
> > but the cadence should be fairly low.
> >
> >>
> >> > I'm not sure we want to
> >> > have lots of references to the URL spread throughout QEMU. I can add one
> >> > somewhere in cxl.json if you think it is important to have one here as well.
> >>
> >> You could add an introduction right under the "# = CXL devices" heading,
> >> and include a full reference to the specification there. Suitably
> >> abbreviated references like the ones you use in this patch should then
> >> be fine.
> >
> > I tried doing that - it resulted in the index including an entry with all the text.
> > So on the webpage, the contents list to the left includes whatever text you put
> > in that block.
> >
> > I'm not sure why, or how to fix that.
>
> Show me what you tried (as a patch or something I can git-pull), and
> I'll have a look.
>
> [...]
>
Very simple to replicate the issue - see below.
Result of this is an extra
"Test text" entry in the index to the left of the html docs.
In qemu-qmp-ref.html we have
<li class="toctree-l3"><a class="reference internal" href="#qapidoc-3297">CXL devices</a><ul>
<li class="toctree-l4"><a class="reference internal" href="#qapidoc-3298">Test text</a></li>
<li class="toctree-l4"><a class="reference internal" href="#qapidoc-3301"><code class="docutils literal notranslate"><span class="pre">CxlEventLog</span></code> (Enum)</a></li>
diff --git a/qapi/cxl.json b/qapi/cxl.json
index 05c560cfe5..9f7f0485ae 100644
--- a/qapi/cxl.json
+++ b/qapi/cxl.json
@@ -3,6 +3,8 @@
##
# = CXL devices
+#
+# Test text
##
##
next prev parent reply other threads:[~2023-05-24 9:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 16:51 [PATCH v5 0/7] QEMU CXL Provide mock CXL events and irq support Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 1/7] hw/cxl/events: Add event status register Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 2/7] hw/cxl: Move CXLRetCode definition to cxl_device.h Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 3/7] hw/cxl/events: Wire up get/clear event mailbox commands Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 4/7] hw/cxl/events: Add event interrupt support Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 5/7] hw/cxl/events: Add injection of General Media Events Jonathan Cameron via
2023-05-22 7:19 ` Markus Armbruster
2023-05-22 12:57 ` Jonathan Cameron via
2023-05-22 13:53 ` Jonathan Cameron via
2023-05-23 8:10 ` Markus Armbruster
[not found] ` <20230523113543.00006a1f@Huawei.com>
2023-05-23 12:46 ` Markus Armbruster
2023-05-24 9:11 ` Jonathan Cameron via [this message]
2023-05-24 9:20 ` Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 6/7] hw/cxl/events: Add injection of DRAM events Jonathan Cameron via
2023-05-22 7:43 ` Markus Armbruster
2023-05-22 13:26 ` Jonathan Cameron via
2023-04-23 16:51 ` [PATCH v5 7/7] hw/cxl/events: Add injection of Memory Module Events Jonathan Cameron via
2023-05-19 7:06 ` Michael S. Tsirkin
2023-05-22 7:47 ` Markus Armbruster
2023-05-16 16:31 ` [PATCH v5 0/7] QEMU CXL Provide mock CXL events and irq support 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=20230524101158.0000579d@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=armbru@redhat.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=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 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).