qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	qemu-devel@nongnu.org, Michael Tsirkin <mst@redhat.com>,
	Fan Ni <fan.ni@samsung.com>,
	linux-cxl@vger.kernel.org
Cc: linuxarm@huawei.com
Subject: Re: [PATCH v2 3/3] hw/cxl: Support 4 HDM decoders at all levels of topology
Date: Thu, 7 Sep 2023 14:41:16 +0200	[thread overview]
Message-ID: <b7b7ca18-ec98-d402-9ebd-6ebaf49f7243@linaro.org> (raw)
In-Reply-To: <20230907113543.19760-4-Jonathan.Cameron@huawei.com>

On 7/9/23 13:35, Jonathan Cameron wrote:
> Support these decoders in CXL host bridges (pxb-cxl), CXL Switch USP
> and CXL Type 3 end points.
> 
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>   include/hw/cxl/cxl_component.h |  10 ++++
>   hw/cxl/cxl-component-utils.c   |  27 +++++----
>   hw/cxl/cxl-host.c              |  65 ++++++++++++++-------
>   hw/mem/cxl_type3.c             | 100 +++++++++++++++++++++++----------
>   4 files changed, 140 insertions(+), 62 deletions(-)

If you ever have to respin, please split the 'hdm_inc' introduction
in a preliminary patch, to reduce the number of changes and the
probability of missing a bug.


  reply	other threads:[~2023-09-07 12:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 11:35 [PATCH v2 0/3] hw/cxl: Support emulating 4 HDM decoders throughout topology Jonathan Cameron via
2023-09-07 11:35 ` [PATCH v2 1/3] hw/cxl: Push cxl_decoder_count_enc() and cxl_decode_ig() into .c Jonathan Cameron via
2023-09-07 12:33   ` Philippe Mathieu-Daudé
2023-09-07 11:35 ` [PATCH v2 2/3] hw/cxl: Add utility functions decoder interleave ways and target count Jonathan Cameron via
2023-09-07 12:35   ` Philippe Mathieu-Daudé
2023-09-07 11:35 ` [PATCH v2 3/3] hw/cxl: Support 4 HDM decoders at all levels of topology Jonathan Cameron via
2023-09-07 12:41   ` Philippe Mathieu-Daudé [this message]
2023-09-11 11:40     ` 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=b7b7ca18-ec98-d402-9ebd-6ebaf49f7243@linaro.org \
    --to=philmd@linaro.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=fan.ni@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linuxarm@huawei.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 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).