From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Joerg Roedel <joro@8bytes.org>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Vivek Goyal <vgoyal@redhat.com>, Dave Young <dyoung@redhat.com>,
Baoquan He <bhe@redhat.com>,
x86@kernel.org, kexec@lists.infradead.org, jroedel@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3 v3] Fix kdump failures with crashkernel=high
Date: Sun, 7 Jun 2015 15:41:36 +0200 [thread overview]
Message-ID: <20150607134136.GA27512@gmail.com> (raw)
In-Reply-To: <20150605132736.GF3679@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> > Joerg Roedel (3):
> > swiotlb: Warn on allocation failure in swiotlb_alloc_coherent
> > x86, swiotlb: Try coherent allocations with __GFP_NOWARN
> > x86, crash: Allocate enough low-mem when crashkernel=high
> >
> > arch/x86/kernel/pci-swiotlb.c | 7 +++++++
> > arch/x86/kernel/setup.c | 5 ++++-
> > lib/swiotlb.c | 11 +++++++++--
> > 3 files changed, 20 insertions(+), 3 deletions(-)
>
> Looks simple enough, all applied, thanks.
>
> hpa, Ingo, any concerns?
Modulo a couple of typos it all looks sane.
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-07 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 10:29 [PATCH 0/3 v3] Fix kdump failures with crashkernel=high Joerg Roedel
2015-06-05 10:30 ` [PATCH 1/3] swiotlb: Warn on allocation failure in swiotlb_alloc_coherent Joerg Roedel
2015-06-12 8:49 ` [tip:x86/kdump] swiotlb: Warn on allocation failure in swiotlb_alloc_coherent() tip-bot for Joerg Roedel
2015-06-05 10:30 ` [PATCH 2/3] x86, swiotlb: Try coherent allocations with __GFP_NOWARN Joerg Roedel
2015-06-12 8:50 ` [tip:x86/kdump] x86/swiotlb: " tip-bot for Joerg Roedel
2015-06-05 10:30 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
2015-06-12 8:50 ` [tip:x86/kdump] x86/crash: Allocate enough low memory " tip-bot for Joerg Roedel
2015-06-05 13:27 ` [PATCH 0/3 v3] Fix kdump failures with crashkernel=high Borislav Petkov
2015-06-07 13:41 ` Ingo Molnar [this message]
2015-06-07 14:38 ` Borislav Petkov
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=20150607134136.GA27512@gmail.com \
--to=mingo@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.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 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).