From: Paolo Bonzini <pbonzini@redhat.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Cc: linux-cxl@vger.kernel.org, linuxarm@huawei.com,
alex.bennee@linaro.org, Marcel Apfelbaum <marcel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Adam Manzanares <a.manzanares@samsung.com>,
Tong Zhang <ztong0001@gmail.com>,
Ben Widawsky <ben.widawsky@intel.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Subject: Re: [PATCH 5/8] pci/pci_expander_bridge: For CXL HB delay the HB register memory region setup.
Date: Tue, 31 May 2022 09:26:34 +0200 [thread overview]
Message-ID: <8878d03f-0576-94e5-5e4d-7133baf61372@redhat.com> (raw)
In-Reply-To: <20220530134514.31664-6-Jonathan.Cameron@huawei.com>
On 5/30/22 15:45, Jonathan Cameron via wrote:
> + /* Walk the pci busses looking for pxb busses to hook up */
> + if (bus) {
> + QLIST_FOREACH(bus, &bus->child, sibling) {
> + if (!pci_bus_is_root(bus)) {
> + continue;
> + }
> + if (pci_bus_is_cxl(bus)) {
> + if (!ms->cxl_devices_state->is_enabled) {
> + error_report("CXL host bridges present, but cxl=off");
> + exit(EXIT_FAILURE);
> + }
> + pxb_cxl_hook_up_registers(ms->cxl_devices_state, bus, &error_fatal);
> + }
> + }
> + }
Perhaps this loop can be moved to a separate function in cxl_host.h?
Otherwise looks great, thank you very much for the quick reply!
Paolo
> if (ms->cxl_devices_state) {
> cxl_fmws_link_targets(ms->cxl_devices_state, &error_fatal);
> }
next prev parent reply other threads:[~2022-05-31 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 13:45 [PATCH 0/8] hw/cxl: Move CXL emulation options and state to machines Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 1/8] hw/cxl: Make the CXL fixed memory window setup a machine parameter Jonathan Cameron via
2022-05-31 7:26 ` Paolo Bonzini
2022-06-06 17:24 ` Ben Widawsky
2022-06-07 10:02 ` Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 2/8] hw/acpi/cxl: Pass in the CXLState directly rather than MachineState Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 3/8] hw/cxl: Push linking of CXL targets into i386/pc rather than in machine.c Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 4/8] tests/acpi: Allow modification of q35 CXL CEDT table Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 5/8] pci/pci_expander_bridge: For CXL HB delay the HB register memory region setup Jonathan Cameron via
2022-05-31 7:26 ` Paolo Bonzini [this message]
2022-05-30 13:45 ` [PATCH 6/8] tests/acpi: Update q35/CEDT.cxl for new memory addresses Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 7/8] hw/cxl: Move the CXLState from MachineState to machine type specific state Jonathan Cameron via
2022-05-30 13:45 ` [PATCH 8/8] hw/machine: Drop cxl_supported flag as no longer useful 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=8878d03f-0576-94e5-5e4d-7133baf61372@redhat.com \
--to=pbonzini@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=ben.widawsky@intel.com \
--cc=imammedo@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marcel@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=ztong0001@gmail.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).