On 04/12/17 at 11:54pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Wed, Apr 12, 2017 at 09:40:56AM +0800, Baoquan He wrote:
> > Do you plan to merge this one as urgent?
> >
> > There's bug created about this issue on rhel, it would be great if it
> > can be put in next or merged so that we can back
Hi Baoquan,
On Wed, Apr 12, 2017 at 09:40:56AM +0800, Baoquan He wrote:
> Do you plan to merge this one as urgent?
>
> There's bug created about this issue on rhel, it would be great if it
> can be put in next or merged so that we can back port it.
No, I am not sending this for v4.11, because th
Hi Joerg,
Do you plan to merge this one as urgent?
There's bug created about this issue on rhel, it would be great if it
can be put in next or merged so that we can back port it.
Thanks
Baoquan
On 03/29/17 at 05:00pm, Joerg Roedel wrote:
> From: Joerg Roedel
>
> When booting into a kexec kern
On Wed, Mar 29, 2017 at 08:51:53AM -0700, Jacob Pan wrote:
> On Wed, 29 Mar 2017 17:00:39 +0200
> Joerg Roedel wrote:
> > +static void intel_disable_iommus(void)
> > +{
> > + struct intel_iommu *iommu = NULL;
> > + struct dmar_drhd_unit *drhd;
> > +
> > + for_each_iommu(iommu, drhd)
> > +
On Wed, 29 Mar 2017 17:00:39 +0200
Joerg Roedel wrote:
> From: Joerg Roedel
>
> When booting into a kexec kernel with intel_iommu=off, and
> the previous kernel had intel_iommu=on, the IOMMU hardware
> is still enabled and gets not disabled by the new kernel.
>
> This causes the boot to fail b
From: Joerg Roedel
When booting into a kexec kernel with intel_iommu=off, and
the previous kernel had intel_iommu=on, the IOMMU hardware
is still enabled and gets not disabled by the new kernel.
This causes the boot to fail because DMA is blocked by the
hardware. Disable the IOMMUs when we find
