From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Jonathan Cameron via <qemu-devel@nongnu.org>,
<ira.weiny@intel.com>, <alucerop@amd.com>,
<a.manzanares@samsung.com>, <dongjoo.seo1@samsung.com>,
<mst@redhat.com>, <marcel.apfelbaum@gmail.com>,
<armbru@redhat.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate
Date: Fri, 2 Jan 2026 16:35:19 +0000 [thread overview]
Message-ID: <20260102163519.00005de4@huawei.com> (raw)
In-Reply-To: <20251230182330.upui2kkymnlylkh2@offworld>
On Tue, 30 Dec 2025 10:23:30 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Tue, 23 Dec 2025, Jonathan Cameron wrote:
>
> >On Wed, 17 Dec 2025 13:59:30 +0000
> >Jonathan Cameron via <qemu-devel@nongnu.org> wrote:
> >
> >Seems the release has been tagged, so I've just rebased and pushed
> >out a draft tree as cxl-2025-12-23-draft
> >Draft because it is very very lightly tested so far.
>
> Thank you for picking this up, 'draft' is fine with me :)
> However, I am not seeing this new branch in your tree(?)
Hi Davidlohr,
Happy new year.
Hmm. Could have sworn I pushed i out... Guess messed that up :(
Note there is a stray change in there for an unrelated tests
tree that I've tidied up in my local tree.
I'll push a new tree out next week but assuming this series
isn't otherwise messed up by me, I'd like to email this out as
something I think is ready to merge before I do that.
If you spot anything bad with this I might shuffle things around
to put the physical port commands set ahead of it.
Jonathan
>
> >
> >On that I've merged in these patches with a few tweaks + added the
> >table test updates. If you get a minute to take a look please do.
> >
> >It's behind a couple of left over series from earlier cycles but my
> >intent is to post it for reviews prior to merge shortly. That
> >may not include in the restrictions control qapi as I think that interface
> >may need more thought. For now I've added a patch that just enables
> >BI always for CFMWSes.
>
> Makes sense.
>
> Thanks,
> Davidlohr
>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Jonathan Cameron via <qemu-devel@nongnu.org>,
<ira.weiny@intel.com>, <alucerop@amd.com>,
<a.manzanares@samsung.com>, <dongjoo.seo1@samsung.com>,
<mst@redhat.com>, <marcel.apfelbaum@gmail.com>,
<armbru@redhat.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate
Date: Fri, 2 Jan 2026 16:35:19 +0000 [thread overview]
Message-ID: <20260102163519.00005de4@huawei.com> (raw)
In-Reply-To: <20251230182330.upui2kkymnlylkh2@offworld>
On Tue, 30 Dec 2025 10:23:30 -0800
Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Tue, 23 Dec 2025, Jonathan Cameron wrote:
>
> >On Wed, 17 Dec 2025 13:59:30 +0000
> >Jonathan Cameron via <qemu-devel@nongnu.org> wrote:
> >
> >Seems the release has been tagged, so I've just rebased and pushed
> >out a draft tree as cxl-2025-12-23-draft
> >Draft because it is very very lightly tested so far.
>
> Thank you for picking this up, 'draft' is fine with me :)
> However, I am not seeing this new branch in your tree(?)
Hi Davidlohr,
Happy new year.
Hmm. Could have sworn I pushed i out... Guess messed that up :(
Note there is a stray change in there for an unrelated tests
tree that I've tidied up in my local tree.
I'll push a new tree out next week but assuming this series
isn't otherwise messed up by me, I'd like to email this out as
something I think is ready to merge before I do that.
If you spot anything bad with this I might shuffle things around
to put the physical port commands set ahead of it.
Jonathan
>
> >
> >On that I've merged in these patches with a few tweaks + added the
> >table test updates. If you get a minute to take a look please do.
> >
> >It's behind a couple of left over series from earlier cycles but my
> >intent is to post it for reviews prior to merge shortly. That
> >may not include in the restrictions control qapi as I think that interface
> >may need more thought. For now I've added a patch that just enables
> >BI always for CFMWSes.
>
> Makes sense.
>
> Thanks,
> Davidlohr
>
next prev parent reply other threads:[~2026-01-02 16:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 19:52 [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 1/5] hw/pcie: Support enabling flit mode Davidlohr Bueso
2025-12-18 16:31 ` Jonathan Cameron
2025-12-18 16:31 ` Jonathan Cameron via
2025-11-03 19:52 ` [PATCH 2/5] hw/cxl: Refactor component register initialization Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 3/5] hw/cxl: Allow BI by default in Window restrictions Davidlohr Bueso
2025-12-18 9:18 ` Markus Armbruster
2025-12-18 15:48 ` Jonathan Cameron
2025-12-18 15:48 ` Jonathan Cameron via
2025-12-18 15:59 ` Markus Armbruster
2025-12-19 17:53 ` Jonathan Cameron
2025-12-19 17:53 ` Jonathan Cameron via
2025-11-03 19:52 ` [PATCH 4/5] hw/cxl: Support type3 HDM-DB Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 5/5] hw/cxl: Remove register special_ops->read() Davidlohr Bueso
2025-12-16 1:12 ` [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate Davidlohr Bueso
2025-12-17 13:59 ` Jonathan Cameron
2025-12-17 13:59 ` Jonathan Cameron via
2025-12-23 11:53 ` Jonathan Cameron
2025-12-23 11:53 ` Jonathan Cameron via
2025-12-30 18:23 ` Davidlohr Bueso
2026-01-02 16:35 ` Jonathan Cameron [this message]
2026-01-02 16:35 ` Jonathan Cameron via
2025-12-16 6:53 ` Markus Armbruster
2025-12-16 15:24 ` Davidlohr Bueso
2025-12-17 7:51 ` Markus Armbruster
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=20260102163519.00005de4@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alucerop@amd.com \
--cc=armbru@redhat.com \
--cc=dave@stgolabs.net \
--cc=dongjoo.seo1@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.