From: Davidlohr Bueso <dave@stgolabs.net>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-acpi@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Robert Moore <robert.moore@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
a.manzanares@samsung.com
Subject: Re: [PATCH v5 0/3] PCI/ACPI: add support for CXL _OSC
Date: Fri, 8 Apr 2022 08:22:36 -0700 [thread overview]
Message-ID: <20220408152236.d6bcs7ktdoy6lzeg@offworld> (raw)
In-Reply-To: <20220406023746.2807328-1-vishal.l.verma@intel.com>
On Tue, 05 Apr 2022, Vishal Verma wrote:
>Changes since v4[1]:
>- Collect an ack for patch 1 (Rafael)
>- Fix commit subject wording in patch 2 (Rafael)
>- Fix a debug print in patch 2 (Rafael)
>- Document the reasoning behind calculation of cxl hotplug support (David)
>- A few definition and variable name changes to make the new _OSC DWORDS
> generic instead of CXL specific (Rafael)
>
>Add support for using the CXL definition of _OSC where applicable, and
>negotiating CXL specific support and control bits.
>
>Patch 1 is a preliminary cleanup that replaces open-coded pointer
>arithmetic to retrieve the Control DWORD with an inline helper.
>
>Patch 2 adds the new CXL _OSC UUID, and uses it instead of the PCI UUID
>when a root port is CXL enabled. It provides a fallback method for
>CXL-1.1 platforms that may not implement the CXL-2.0 _OSC.
>
>Patch 3 performs negotiation for the CXL specific _OSC support and
>control bits.
>
>I've tested these against a custom qemu[2], which adds the CXL _OSC (in
>addition to other CXL support). Specifically, _OSC support is added
>here[3].
For the series, feel free to add my:
Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
prev parent reply other threads:[~2022-04-08 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 2:37 [PATCH v5 0/3] PCI/ACPI: add support for CXL _OSC Vishal Verma
2022-04-06 2:37 ` [PATCH v5 1/3] PCI/ACPI: add a helper for retrieving _OSC Control DWORDs Vishal Verma
2022-04-08 20:14 ` Adam Manzanares
2022-04-12 19:23 ` Rafael J. Wysocki
2022-04-06 2:37 ` [PATCH v5 2/3] PCI/ACPI: Prefer CXL _OSC instead of PCIe _OSC for CXL host bridges Vishal Verma
2022-04-12 19:21 ` Rafael J. Wysocki
2022-04-06 2:37 ` [PATCH v5 3/3] PCI/ACPI: negotiate CXL _OSC Vishal Verma
2022-04-12 19:20 ` Rafael J. Wysocki
2022-04-08 15:22 ` Davidlohr Bueso [this message]
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=20220408152236.d6bcs7ktdoy6lzeg@offworld \
--to=dave@stgolabs.net \
--cc=Jonathan.Cameron@Huawei.com \
--cc=a.manzanares@samsung.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=vishal.l.verma@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 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.