public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Dutile <ddutile@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 V2] iommu/amd: Add workaround for ERBT1312
Date: Wed, 24 Apr 2013 09:52:40 -0400	[thread overview]
Message-ID: <5177E3A8.5020001@redhat.com> (raw)
In-Reply-To: <20130424104616.GH17148@8bytes.org>

On 04/24/2013 06:46 AM, Joerg Roedel wrote:
> On Tue, Apr 23, 2013 at 09:22:45AM -0400, Don Dutile wrote:
>> Given other threads on this mail list (and I've seen crashes with same problem)
>> where this type of logging during a flood of IOMMU errors will lock up the machine,
>> is there something that can be done to break the do-while loop after n iterations
>> have been exec'd, so the kernel can progress during a crash ?
>
> In the case of an IOMMU error flood this loop will only run until the
> event-log/ppr-log overflows. So it should not turn into an endless loop.
>
>
> 	Joerg
>
>
Thanks for verification.


      reply	other threads:[~2013-04-24 13:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  7:07 [PATCH 1/2 V2] iommu/amd: Add workaround for ERBT1312 suravee.suthikulpanit
2013-04-18 16:02 ` Joerg Roedel
2013-04-18 16:13   ` Suravee Suthikulanit
2013-04-18 16:28     ` Joerg Roedel
2013-04-18 16:59       ` Suravee Suthikulanit
2013-04-18 18:35         ` Joerg Roedel
2013-04-18 18:56           ` Suravee Suthikulpanit
2013-04-18 20:06             ` Joerg Roedel
2013-04-22 21:43               ` Suravee Suthikulanit
2013-04-23 13:22       ` Don Dutile
2013-04-24 10:46         ` Joerg Roedel
2013-04-24 13:52           ` Don Dutile [this message]

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=5177E3A8.5020001@redhat.com \
    --to=ddutile@redhat.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suravee.suthikulpanit@amd.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