From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Christian König" <christian.koenig@amd.com>,
"Icenowy Zheng" <uwu@icenowy.me>, "Huang Rui" <ray.huang@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
bhelgaas@google.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: PCIe coherency in spec (was: [RFC PATCH 2/2] drm/ttm: downgrade cached to write_combined when snooping not available)
Date: Wed, 03 Jul 2024 16:52:30 +0800 [thread overview]
Message-ID: <4c5e0f77-b24d-47dd-86d2-31cb8e44b42a@app.fastmail.com> (raw)
In-Reply-To: <fd1d0a97-7075-4936-b58b-e99bab9afc58@app.fastmail.com>
在2024年7月2日七月 下午6:03,Jiaxun Yang写道:
> 在2024年7月2日七月 下午5:27,Christian König写道:
>> Am 02.07.24 um 11:06 schrieb Icenowy Zheng:
>>> [SNIP] However I don't think the definition of the AGP spec could apply on all
>>> PCI(e) implementations. The AGP spec itself don't apply on
>>> implementations that do not implement AGP (which is the most PCI(e)
>>> implementations today), and it's not in the reference list of the PCIe
>>> spec, so it does no help on this context.
>> No, exactly that is not correct.
>>
>> See as I explained the No-Snoop extension to PCIe was created to help
>> with AGP support and later merged into the base PCIe specification.
>>
>> So the AGP spec is now part of the PCIe spec.
Hi Bjorn & linux-pci folks,
It seems like we have some disputes on interpretation pf PCIe specification.
We are seeking your expertise on the question: Does PCIe specification mandate Cache
coherency via snoop?
There are some further context in this thread [1].
[1]: https://lore.kernel.org/all/0db974d40cd8c5dcc723d43c328bac923e0fe33a.camel@icenowy.me/
Thanks
- Jiaxun
>
> We don't really buy this theory.
>
> Keyword "AGP" doesn't appear in "PCI Express Base 4.0 Base Specification" even
> once.
>
> If PCIe is a predecessor of AGP, where does AGP specific software interface like
> AGP aperture goes? PCIe GPUs are only borrowing software concepts from AGP,
> but they didn't inherit any hardware properties.
>
> [...]
>> We seem to have a misunderstanding here, this is not a software issue.
>> The hardware platform is considered broken by the hardware vendor!
>
> It's up to the specification text to define compliance means. So far as
> per analysis
> from Icenowy of PCIe specification text itself it's not prohibited.
>
>>
>> In other words people have stitched together hardware in a way which is
>> not supported by the creator of that hardware.
>>
>> So as long as you can't convince anybody from ARM or the RISC-V team or
>> whoever created that hardware to confirm that the hardware actually
>> works you won't get any support for that.
>
> Well we are trying to support them on our own in mainline, we are not asking
> for any support.
>
> Thanks
> - Jiaxun
>>
>> Regards,
>> Christian.
>
> --
> - Jiaxun
--
- Jiaxun
next parent reply other threads:[~2024-07-03 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240629052247.2653363-1-uwu@icenowy.me>
[not found] ` <20240629052247.2653363-3-uwu@icenowy.me>
[not found] ` <a143a2c3-c6f0-4537-acc6-94f229f14639@app.fastmail.com>
[not found] ` <2760BA02-8FF8-4B29-BFE2-1322B5BFB6EC@icenowy.me>
[not found] ` <7e30177b-ff13-4fed-aa51-47a9cbd5d572@amd.com>
[not found] ` <6303afecce2dff9e7d30f67e0a74205256e0a524.camel@icenowy.me>
[not found] ` <ff1bf596-83cb-4b3e-a33a-621ac2c8171c@amd.com>
[not found] ` <b9189c97f7efbaa895198113ee5b47012bd8b4dc.camel@icenowy.me>
[not found] ` <ae7085fd-3bca-4a4a-b465-5e4941011877@amd.com>
[not found] ` <fd1d0a97-7075-4936-b58b-e99bab9afc58@app.fastmail.com>
2024-07-03 8:52 ` Jiaxun Yang [this message]
2024-07-03 21:08 ` PCIe coherency in spec (was: [RFC PATCH 2/2] drm/ttm: downgrade cached to write_combined when snooping not available) Bjorn Helgaas
2024-07-04 2:00 ` Icenowy Zheng
2024-07-04 6:11 ` Christoph Hellwig
2024-07-04 6:40 ` Icenowy Zheng
2024-07-04 6:44 ` Christoph Hellwig
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=4c5e0f77-b24d-47dd-86d2-31cb8e44b42a@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=airlied@gmail.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ray.huang@amd.com \
--cc=tzimmermann@suse.de \
--cc=uwu@icenowy.me \
/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