All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Qiuxu Zhuo <qiuxu.zhuo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH 1/1] iommu/vt-d: Don't print the failure message when booting non-kdump kernel
Date: Fri, 28 Apr 2017 23:39:00 +0200	[thread overview]
Message-ID: <20170428213900.GA19756@8bytes.org> (raw)
In-Reply-To: <20170427171615.78999-1-qiuxu.zhuo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

On Fri, Apr 28, 2017 at 01:16:15AM +0800, Qiuxu Zhuo wrote:
> When booting a new non-kdump kernel, we have below failure message:
> 
> [    0.004000] DMAR-IR: IRQ remapping was enabled on dmar2 but we are not in kdump mode
> [    0.004000] DMAR-IR: Failed to copy IR table for dmar2 from previous kernel
> [    0.004000] DMAR-IR: IRQ remapping was enabled on dmar1 but we are not in kdump mode
> [    0.004000] DMAR-IR: Failed to copy IR table for dmar1 from previous kernel
> [    0.004000] DMAR-IR: IRQ remapping was enabled on dmar0 but we are not in kdump mode
> [    0.004000] DMAR-IR: Failed to copy IR table for dmar0 from previous kernel
> [    0.004000] DMAR-IR: IRQ remapping was enabled on dmar3 but we are not in kdump mode
> [    0.004000] DMAR-IR: Failed to copy IR table for dmar3 from previous kernel
> 
> For non-kdump case, we no need to copy IR table from previous kernel
> so it's nonthing actually failed. To be less alarming or misleading,
> do not print "DMAR-IR: Failed to copy IR table for dmar[0-9] from
> previous kernel" messages when booting non-kdump kernel.
> 
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> ---
>  drivers/iommu/intel_irq_remapping.c | 15 ++++++---------
>  1 file changed, 6 insertions(+), 9 deletions(-)

Applied, thanks.

      parent reply	other threads:[~2017-04-28 21:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 17:16 [PATCH 1/1] iommu/vt-d: Don't print the failure message when booting non-kdump kernel Qiuxu Zhuo
     [not found] ` <20170427171615.78999-1-qiuxu.zhuo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-04-28 21:39   ` Joerg Roedel [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=20170428213900.GA19756@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=qiuxu.zhuo-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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.