From: Will Deacon <will.deacon@arm.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Vikram Sethi <vikrams@codeaurora.org>,
"shankerd@codeaurora.org" <shankerd@codeaurora.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Joerg Roedel <joro@8bytes.org>,
kexec@lists.infradead.org, iommu@lists.linux-foundation.org,
Bjorn Helgaas <helgaas@kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
"Goel, Sameer" <sgoel@codeaurora.org>,
David Woodhouse <dwmw2@infradead.org>,
Nate Watterson <nwatters@codeaurora.org>
Subject: Re: RFC on Kdump and PCIe on ARM64
Date: Fri, 2 Mar 2018 18:02:20 +0000 [thread overview]
Message-ID: <20180302180219.GB20579@arm.com> (raw)
In-Reply-To: <84121a8d-5294-0567-6c6b-f57e85dc4961@codeaurora.org>
On Fri, Mar 02, 2018 at 09:12:29AM -0500, Sinan Kaya wrote:
> On 3/2/2018 5:30 AM, Will Deacon wrote:
> >> Do you really have to reset the IOMMU? Can you just give it new page
> >> tables that start out with all IOVAs from all devices being invalid,
> >> then add valid mappings as drivers need them (presumably after the
> >> driver has done whatever it needs to so the device stops using the old
> >> DMA addresses)?
> > We already have the option to do that via the command line using the
> > disable_bypass option, so it just sounds like we need to take this into
> > account when resetting the SMMU to take care that GBPA is configured so
> > that transactions are terminated when SMMUEN=0.
>
> 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?
> 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.
Will
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Sinan Kaya <okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: Vikram Sethi <vikrams-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
"shankerd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
<shankerd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Linux PCI <linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Bjorn Helgaas <helgaas-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-arm Mailing List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"Goel, Sameer" <sgoel-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: RFC on Kdump and PCIe on ARM64
Date: Fri, 2 Mar 2018 18:02:20 +0000 [thread overview]
Message-ID: <20180302180219.GB20579@arm.com> (raw)
In-Reply-To: <84121a8d-5294-0567-6c6b-f57e85dc4961-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On Fri, Mar 02, 2018 at 09:12:29AM -0500, Sinan Kaya wrote:
> On 3/2/2018 5:30 AM, Will Deacon wrote:
> >> Do you really have to reset the IOMMU? Can you just give it new page
> >> tables that start out with all IOVAs from all devices being invalid,
> >> then add valid mappings as drivers need them (presumably after the
> >> driver has done whatever it needs to so the device stops using the old
> >> DMA addresses)?
> > We already have the option to do that via the command line using the
> > disable_bypass option, so it just sounds like we need to take this into
> > account when resetting the SMMU to take care that GBPA is configured so
> > that transactions are terminated when SMMUEN=0.
>
> 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?
> 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.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Sinan Kaya <okaya@codeaurora.org>
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 18:02:20 +0000 [thread overview]
Message-ID: <20180302180219.GB20579@arm.com> (raw)
In-Reply-To: <84121a8d-5294-0567-6c6b-f57e85dc4961@codeaurora.org>
On Fri, Mar 02, 2018 at 09:12:29AM -0500, Sinan Kaya wrote:
> On 3/2/2018 5:30 AM, Will Deacon wrote:
> >> Do you really have to reset the IOMMU? Can you just give it new page
> >> tables that start out with all IOVAs from all devices being invalid,
> >> then add valid mappings as drivers need them (presumably after the
> >> driver has done whatever it needs to so the device stops using the old
> >> DMA addresses)?
> > We already have the option to do that via the command line using the
> > disable_bypass option, so it just sounds like we need to take this into
> > account when resetting the SMMU to take care that GBPA is configured so
> > that transactions are terminated when SMMUEN=0.
>
> 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?
> 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.
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC on Kdump and PCIe on ARM64
Date: Fri, 2 Mar 2018 18:02:20 +0000 [thread overview]
Message-ID: <20180302180219.GB20579@arm.com> (raw)
In-Reply-To: <84121a8d-5294-0567-6c6b-f57e85dc4961@codeaurora.org>
On Fri, Mar 02, 2018 at 09:12:29AM -0500, Sinan Kaya wrote:
> On 3/2/2018 5:30 AM, Will Deacon wrote:
> >> Do you really have to reset the IOMMU? Can you just give it new page
> >> tables that start out with all IOVAs from all devices being invalid,
> >> then add valid mappings as drivers need them (presumably after the
> >> driver has done whatever it needs to so the device stops using the old
> >> DMA addresses)?
> > We already have the option to do that via the command line using the
> > disable_bypass option, so it just sounds like we need to take this into
> > account when resetting the SMMU to take care that GBPA is configured so
> > that transactions are terminated when SMMUEN=0.
>
> 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?
> 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.
Will
next prev parent reply other threads:[~2018-03-02 18:02 UTC|newest]
Thread overview: 39+ 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 17:44 ` Sinan Kaya
2018-03-01 17:44 ` Sinan Kaya
2018-03-01 19:05 ` Bjorn Helgaas
2018-03-01 19:05 ` Bjorn Helgaas
2018-03-01 19:05 ` Bjorn Helgaas
2018-03-01 19:05 ` Bjorn Helgaas
2018-03-01 19:19 ` Sinan Kaya
2018-03-01 19:19 ` Sinan Kaya
2018-03-01 19:19 ` Sinan Kaya
2018-03-01 19:19 ` Sinan Kaya
2018-03-02 0:03 ` Bjorn Helgaas
2018-03-02 0:03 ` Bjorn Helgaas
2018-03-02 0:03 ` Bjorn Helgaas
2018-03-02 0:03 ` Bjorn Helgaas
2018-03-02 10:30 ` Will Deacon
2018-03-02 10:30 ` Will Deacon
2018-03-02 10:30 ` Will Deacon
2018-03-02 10:30 ` Will Deacon
2018-03-02 14:12 ` Sinan Kaya
2018-03-02 14:12 ` Sinan Kaya
2018-03-02 14:12 ` Sinan Kaya
2018-03-02 14:12 ` Sinan Kaya
2018-03-02 18:02 ` Will Deacon [this message]
2018-03-02 18:02 ` Will Deacon
2018-03-02 18:02 ` Will Deacon
2018-03-02 18:02 ` Will Deacon
2018-03-02 18:37 ` Sinan Kaya
2018-03-02 18:37 ` Sinan Kaya
2018-03-02 18:37 ` Sinan Kaya
2018-03-02 18:37 ` Sinan Kaya
2018-03-02 14:20 ` Sinan Kaya
2018-03-02 14:20 ` Sinan Kaya
2018-03-02 14:20 ` Sinan Kaya
2018-03-02 14:20 ` Sinan Kaya
2018-03-02 1:44 ` Baoquan He
2018-03-02 1:44 ` Baoquan He
2018-03-02 1:44 ` Baoquan He
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=20180302180219.GB20579@arm.com \
--to=will.deacon@arm.com \
--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=okaya@codeaurora.org \
--cc=sgoel@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=vikrams@codeaurora.org \
/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.