From: Sinan Kaya <okaya@codeaurora.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Linux PCI <linux-pci@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Nate Watterson <nwatters@codeaurora.org>,
"shankerd@codeaurora.org" <shankerd@codeaurora.org>,
Vikram Sethi <vikrams@codeaurora.org>,
"Goel, Sameer" <sgoel@codeaurora.org>,
kexec@lists.infradead.org, Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: RFC on Kdump and PCIe on ARM64
Date: Fri, 2 Mar 2018 13:37:11 -0500 [thread overview]
Message-ID: <2f8e1f65-5f70-9556-5d96-c50421982f73@codeaurora.org> (raw)
In-Reply-To: <20180302180219.GB20579@arm.com>
On 3/2/2018 1:02 PM, Will Deacon wrote:
>> How about the points that Baoquan highlighted in his email regarding the
>> solution from AMD and X86?
> Which specific points do you think this proposal doesn't address?
>
No specific concerns at this moment.
>> I have not read the entire thread but, is this just a matter of following
>> what Bjorn recommended or there is more to it?
> I'm trying to say how I think Bjorn's idea can be implemented for SMMUv3.
> I basically want to avoid a situation where the SMMU driver tries to walk
> the in-memory data structures left by a previous kernel and infer the
> setup from that.
Let me know if you have something to test. We have a test case with the
crash.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-03-02 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 17:44 RFC on Kdump and PCIe on ARM64 Sinan Kaya
2018-03-01 19:05 ` Bjorn Helgaas
2018-03-01 19:19 ` Sinan Kaya
2018-03-02 0:03 ` Bjorn Helgaas
2018-03-02 10:30 ` Will Deacon
2018-03-02 14:12 ` Sinan Kaya
2018-03-02 18:02 ` Will Deacon
2018-03-02 18:37 ` Sinan Kaya [this message]
2018-03-02 14:20 ` Sinan Kaya
2018-03-02 1:44 ` Baoquan He
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=2f8e1f65-5f70-9556-5d96-c50421982f73@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=dwmw2@infradead.org \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=nwatters@codeaurora.org \
--cc=sgoel@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=vikrams@codeaurora.org \
--cc=will.deacon@arm.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).