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>,
	mst@redhat.com, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org
Cc: linuxarm@huawei.com, linux-cxl@vger.kernel.org,
	marcel.apfelbaum@gmail.com, "Dave Jiang" <dave.jiang@intel.com>,
	"Huang Ying" <ying.huang@intel.com>,
	"Michael Roth" <michael.roth@amd.com>,
	fan.ni@samsung.com,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [RFC qemu 1/6] hw/pci-bridge/cxl_root_port: Provide x-speed and x-width properties.
Date: Thu, 1 May 2025 23:49:45 +0200	[thread overview]
Message-ID: <1528a021-d3ec-495e-a42b-6614d60b0666@linaro.org> (raw)
In-Reply-To: <20240712122414.1448284-2-Jonathan.Cameron@huawei.com>

Hi Jonathan and Alex.

(This patch is now merged as commit 1478b560902).

On 12/7/24 14:24, Jonathan Cameron via wrote:
> Approach copied from gen_pcie_root_port.c
> Previously the link defaulted to a maximum of 2.5GT/s and 1x.  Enable setting
> it's maximum values.  The actual value after 'training' will depend on the
> downstream device configuration.
> 
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>   hw/pci-bridge/cxl_root_port.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/hw/pci-bridge/cxl_root_port.c b/hw/pci-bridge/cxl_root_port.c
> index 2dd10239bd..5e2156d7ba 100644
> --- a/hw/pci-bridge/cxl_root_port.c
> +++ b/hw/pci-bridge/cxl_root_port.c
> @@ -24,6 +24,7 @@
>   #include "hw/pci/pcie_port.h"
>   #include "hw/pci/msi.h"
>   #include "hw/qdev-properties.h"
> +#include "hw/qdev-properties-system.h"
>   #include "hw/sysbus.h"
>   #include "qapi/error.h"
>   #include "hw/cxl/cxl.h"
> @@ -206,6 +207,10 @@ static Property gen_rp_props[] = {
>                        -1),
>       DEFINE_PROP_SIZE("pref64-reserve", CXLRootPort, res_reserve.mem_pref_64,
>                        -1),
> +    DEFINE_PROP_PCIE_LINK_SPEED("x-speed", PCIESlot,
> +                                speed, PCIE_LINK_SPEED_64),
> +    DEFINE_PROP_PCIE_LINK_WIDTH("x-width", PCIESlot,
> +                                width, PCIE_LINK_WIDTH_32),

Per the documentation:

   We commonly use a ``x-`` command name prefix to make lack of
   stability obvious to human users.

Are these properties meant to be stable? You mentioned "Approach
copied from gen_pcie_root_port.c". There they were added because
of:

commit c2a490e344b4e231cf9488c67df7ee46977b1ebe
Author: Alex Williamson <alex.williamson@redhat.com>
Date:   Wed Dec 12 12:39:43 2018 -0700

     pcie: Allow generic PCIe root port to specify link speed and width

     Allow users to experimentally specify speed and width values for the
     generic PCIe root port.  Defaults remain at 2.5GT/s & x1 for
     compatiblity with the intent to only support changing defaults via
     machine types for now.

This was 6 years ago, are we still experimenting?

>       DEFINE_PROP_END_OF_LIST()
>   };
>   



  reply	other threads:[~2025-05-01 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 12:24 [RFC qemu 0/6] hw/cxl: Link speed and width control Jonathan Cameron via
2024-07-12 12:24 ` [RFC qemu 1/6] hw/pci-bridge/cxl_root_port: Provide x-speed and x-width properties Jonathan Cameron via
2025-05-01 21:49   ` Philippe Mathieu-Daudé [this message]
2024-07-12 12:24 ` [RFC qemu 2/6] hw/pci-bridge/cxl_upstream: " Jonathan Cameron via
2024-07-12 12:24 ` [RFC qemu 3/6] hw/pcie: Factor out PCI Express link register filing common to EP Jonathan Cameron via
2024-07-12 12:24 ` [RFC qemu 4/6] hw/pcie: Provide a utility function for control of EP / SW USP link Jonathan Cameron via
2024-07-12 12:24 ` [RFC qemu 5/6] hw/mem/cxl-type3: Add properties to control link speed and width Jonathan Cameron via
2024-07-12 12:24 ` [RFC qemu 6/6] hw/pci-bridge/cxl-upstream: " Jonathan Cameron via
2024-08-28 17:00 ` [RFC qemu 0/6] hw/cxl: Link speed and width control 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=1528a021-d3ec-495e-a42b-6614d60b0666@linaro.org \
    --to=philmd@linaro.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dave.jiang@intel.com \
    --cc=fan.ni@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=michael.roth@amd.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ying.huang@intel.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).