From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Zayd Qumsieh <zaydq@rivosinc.com>
Cc: <alison.schofield@intel.com>, <ben.widawsky@intel.com>,
<cbrowy@avery-design.com>, <dan.j.williams@intel.com>,
<f.fangjian@huawei.com>, <helgaas@kernel.org>,
<ira.weiny@intel.com>, <linux-acpi@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linuxarm@huawei.com>, <lorenzo.pieralisi@arm.com>,
<vishal.l.verma@intel.com>, Dylan Reid <dylan@rivosinc.com>
Subject: Re: [RFC PATCH 2/2] cxl/mem: Add CDAT table reading from DOE
Date: Thu, 13 Jan 2022 09:25:12 +0000 [thread overview]
Message-ID: <20220113092512.000011d6@Huawei.com> (raw)
In-Reply-To: <CAAJ9+9ct3+N0LyH+9N03ZQYUZnF23LFAyWFcnNK4bD7SvaohrQ@mail.gmail.com>
On Wed, 12 Jan 2022 14:16:18 -0800
Zayd Qumsieh <zaydq@rivosinc.com> wrote:
> Hello all,
>
> Due to issues with vger.kernel.org marking HTML emails as spam, I'll
> be resending the email in plain text:
>
>
>
> Hello all, First off, thanks for your work on implementing PCI Data
> Object Exchange in QEMU and Linux.
>
> 1. Are these patches still being worked on? If not, I’ll try to get
> them rebased and finished.
>
> 2. Are there any notes not mentioned in the emails you feel are
> important to know about?
>
> 3. I'm particularly interested in the testing framework - the emails
> mention that a lot of testing has been done through QEMU but how can I
> carry out these tests on my own? What tools did you use?
>
> Thanks,
>
> Zayd
https://lore.kernel.org/all/20211105235056.3711389-1-ira.weiny@intel.com/
Is the latest version of this. For basic testing Ben's qemu branch should
work for you.
https://gitlab.com/bwidawsk/qemu/-/commits/cxl-2.0v4/
Note there are some big questions over the approach used for integrating
this with the PCI subsystem (auxiliary bus vs library) which I'm not sure
we've reached a conclusion on yet.
One minor thing on the wish list is lspci support to at least identify the
presence of a DOE. I have patches for that and will send out fairly soon
once I've cleared a backlog of other stuff.
My main focus right now is on resolving some of the opens around the
QEMU support for CXL emul in general, but I haven't touched the DOE stuff
beyond rebasing. *fingers crossed* I should have an updated qemu tree
out sometime in next week or so.
Thanks,
Jonathan
next prev parent reply other threads:[~2022-01-13 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAJ9+9fq1=EcOaSoo3oD_5QjYNAv6PPDjKS+gC9o7XDp2p1XpQ@mail.gmail.com>
2022-01-12 22:16 ` [RFC PATCH 2/2] cxl/mem: Add CDAT table reading from DOE Zayd Qumsieh
2022-01-13 9:25 ` Jonathan Cameron [this message]
2022-01-15 0:15 ` Zayd Qumsieh
2021-03-10 18:03 [RFC PATCH 0/2] PCI Data Object Exchange support + CXL CDAT Jonathan Cameron
2021-03-10 18:03 ` [RFC PATCH 2/2] cxl/mem: Add CDAT table reading from DOE Jonathan Cameron
2021-03-10 18:14 ` Jonathan Cameron
2021-03-10 22:59 ` Chris Browy
2021-03-15 22:00 ` Dan Williams
2021-03-16 10:36 ` Jonathan Cameron
2021-03-17 1:42 ` Dan Williams
2021-03-17 1:55 ` Dan Williams
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=20220113092512.000011d6@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=cbrowy@avery-design.com \
--cc=dan.j.williams@intel.com \
--cc=dylan@rivosinc.com \
--cc=f.fangjian@huawei.com \
--cc=helgaas@kernel.org \
--cc=ira.weiny@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=vishal.l.verma@intel.com \
--cc=zaydq@rivosinc.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).