From: Borislav Petkov <bp@alien8.de>
To: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rric@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
saikrishna12468@gmail.com, git@amd.com,
Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v6 2/2] EDAC/zynqmp: Add EDAC support for Xilinx ZynqMP OCM
Date: Tue, 8 Nov 2022 19:39:02 +0100 [thread overview]
Message-ID: <Y2qiRoiYepte/R4W@zn.tnic> (raw)
In-Reply-To: <20221102070655.247511-3-sai.krishna.potthuri@amd.com>
On Wed, Nov 02, 2022 at 12:36:55PM +0530, Sai Krishna Potthuri wrote:
> Add EDAC support for Xilinx ZynqMP OCM Controller, this driver
So a while ago you said that this driver is for the on chip memory
controller. Is it possible for such a system to have another memory
controller too for which another EDAC driver gets loaded?
Because the EDAC core - at least on x86 - assumes that a single driver
runs on the system and I don't think I've ever had the case where we
need multiple drivers. And in such case to audit it for concurrency
issues.
So I guess the question is, can a system have zynqmp_ocm_edac and say,
synopsys_edac or some other EDAC driver loaded at the same time?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michal Simek <michal.simek@xilinx.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Robert Richter <rric@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
saikrishna12468@gmail.com, git@amd.com,
Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v6 2/2] EDAC/zynqmp: Add EDAC support for Xilinx ZynqMP OCM
Date: Tue, 8 Nov 2022 19:39:02 +0100 [thread overview]
Message-ID: <Y2qiRoiYepte/R4W@zn.tnic> (raw)
In-Reply-To: <20221102070655.247511-3-sai.krishna.potthuri@amd.com>
On Wed, Nov 02, 2022 at 12:36:55PM +0530, Sai Krishna Potthuri wrote:
> Add EDAC support for Xilinx ZynqMP OCM Controller, this driver
So a while ago you said that this driver is for the on chip memory
controller. Is it possible for such a system to have another memory
controller too for which another EDAC driver gets loaded?
Because the EDAC core - at least on x86 - assumes that a single driver
runs on the system and I don't think I've ever had the case where we
need multiple drivers. And in such case to audit it for concurrency
issues.
So I guess the question is, can a system have zynqmp_ocm_edac and say,
synopsys_edac or some other EDAC driver loaded at the same time?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-08 18:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 7:06 [PATCH v6 0/2] EDAC: Add support for Xilinx ZynqMP OCM EDAC Sai Krishna Potthuri
2022-11-02 7:06 ` Sai Krishna Potthuri
2022-11-02 7:06 ` [PATCH v6 1/2] dt-bindings: edac: Add bindings for Xilinx ZynqMP OCM Sai Krishna Potthuri
2022-11-02 7:06 ` Sai Krishna Potthuri
2022-11-10 9:10 ` (subset) " Krzysztof Kozlowski
2022-11-10 9:10 ` Krzysztof Kozlowski
2022-11-10 9:12 ` Krzysztof Kozlowski
2022-11-10 9:12 ` Krzysztof Kozlowski
2022-11-10 10:06 ` Krzysztof Kozlowski
2022-11-10 10:06 ` Krzysztof Kozlowski
2022-11-02 7:06 ` [PATCH v6 2/2] EDAC/zynqmp: Add EDAC support " Sai Krishna Potthuri
2022-11-02 7:06 ` Sai Krishna Potthuri
2022-11-08 18:39 ` Borislav Petkov [this message]
2022-11-08 18:39 ` Borislav Petkov
2022-11-09 11:21 ` Potthuri, Sai Krishna
2022-11-09 11:21 ` Potthuri, Sai Krishna
2022-11-09 18:08 ` Borislav Petkov
2022-11-09 18:08 ` Borislav Petkov
2022-11-25 15:12 ` Borislav Petkov
2022-11-25 15:12 ` Borislav Petkov
2022-12-05 10:20 ` Potthuri, Sai Krishna
2022-12-05 10:20 ` Potthuri, Sai Krishna
2022-12-05 13:16 ` Borislav Petkov
2022-12-05 13:16 ` Borislav Petkov
2022-12-05 14:49 ` Michal Simek
2022-12-05 14:49 ` Michal Simek
2022-12-05 15:19 ` Borislav Petkov
2022-12-05 15:19 ` Borislav Petkov
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=Y2qiRoiYepte/R4W@zn.tnic \
--to=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=james.morse@arm.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mchehab@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=sai.krishna.potthuri@amd.com \
--cc=saikrishna12468@gmail.com \
--cc=shubhrajyoti.datta@amd.com \
--cc=tony.luck@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.