From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, douly.fnst@cn.fujitsu.com,
joro@8bytes.org, uobergfe@redhat.com, prarit@redhat.com,
Baoquan He <bhe@redhat.com>
Subject: [PATCH v2 0/2] x86/apic/kexec: Legacy irq setting fixs in kdump kernel
Date: Thu, 25 Jan 2018 22:11:32 +0800 [thread overview]
Message-ID: <20180125141134.25053-1-bhe@redhat.com> (raw)
This is v2 post.
In v2, no code change, just improve change log of patch 1 and 2.
And drop the old patch 3 in v1, a clean up patch. The current
x86_io_apic_ops.disable() hook is still needed by irq remapping.
Baoquan He (2):
x86/apic/kexec: Enable legacy irq mode before jump to kexec/kdump
kernel
x86/apic: Set up through-local-APIC on boot CPU's LINT0 if 'noapic'
specified
arch/x86/include/asm/io_apic.h | 3 ++-
arch/x86/kernel/apic/apic.c | 2 +-
arch/x86/kernel/apic/io_apic.c | 12 ++++--------
arch/x86/kernel/crash.c | 2 +-
arch/x86/kernel/machine_kexec_32.c | 15 +++++----------
arch/x86/kernel/machine_kexec_64.c | 15 +++++----------
arch/x86/kernel/reboot.c | 2 +-
7 files changed, 19 insertions(+), 32 deletions(-)
--
2.13.6
next reply other threads:[~2018-01-25 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 14:11 Baoquan He [this message]
2018-01-25 14:11 ` [PATCH v2 1/2] x86/apic/kexec: Enable legacy irq mode before jump to kexec/kdump kernel Baoquan He
2018-02-07 17:11 ` Eric W. Biederman
2018-02-07 17:35 ` Eric W. Biederman
2018-02-07 19:48 ` Eric W. Biederman
2018-02-08 12:34 ` Baoquan He
2018-01-25 14:11 ` [PATCH v2 2/2] x86/apic: Set up through-local-APIC on boot CPU's LINT0 if 'noapic' specified Baoquan He
2018-02-02 4:04 ` [PATCH v2 0/2] x86/apic/kexec: Legacy irq setting fixs in kdump kernel Dou Liyang
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=20180125141134.25053-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=tglx@linutronix.de \
--cc=uobergfe@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
all inboxes | Powered by JetHome®