From: Davidlohr Bueso <dave@stgolabs.net>
To: Li Ming <ming.li@zohomail.com>
Cc: jonathan.cameron@huawei.com, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC Patch v1 0/3] Fix using wrong GPF DVSEC location issue
Date: Thu, 20 Mar 2025 19:14:41 -0700 [thread overview]
Message-ID: <20250321021441.vdmo5txhvb6kya3a@offworld> (raw)
In-Reply-To: <20250319035516.222054-1-ming.li@zohomail.com>
On Wed, 19 Mar 2025, Li Ming wrote:
>But I am not sure if all dports under a same port will have same
>configuration space layout, if yes, that will not be a problem. If I am
>wrong, please let me know, thanks.
Yes, when caching the dvsec was suggested, it was my assumption that the
config space would be the same.
Thanks,
Davidlohr
next prev parent reply other threads:[~2025-03-21 2:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 3:55 [RFC Patch v1 0/3] Fix using wrong GPF DVSEC location issue Li Ming
2025-03-19 3:55 ` [RFC Patch v1 1/3] cxl/core: Fix caching dport GPF DVSEC issue Li Ming
2025-03-21 7:41 ` Davidlohr Bueso
2025-03-21 12:08 ` Jonathan Cameron
2025-03-19 3:55 ` [RFC Patch v1 2/3] cxl/pci: Update Port GPF timeout only when the first EP attaching Li Ming
2025-03-21 5:40 ` Davidlohr Bueso
2025-03-21 12:07 ` Jonathan Cameron
2025-03-19 3:55 ` [RFC Patch v1 3/3] cxl/pci: Drop the parameter is_port of cxl_gpf_get_dvsec() Li Ming
2025-03-21 5:23 ` Davidlohr Bueso
2025-03-21 12:06 ` Jonathan Cameron
2025-03-21 2:14 ` Davidlohr Bueso [this message]
2025-03-21 3:59 ` [RFC Patch v1 0/3] Fix using wrong GPF DVSEC location issue Davidlohr Bueso
2025-03-21 6:55 ` Li Ming
2025-03-21 12:09 ` Jonathan Cameron
2025-03-21 17:02 ` Dan Williams
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=20250321021441.vdmo5txhvb6kya3a@offworld \
--to=dave@stgolabs.net \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox