From: Dexuan Cui <decui@microsoft.com>
To: Thomas Gleixner <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"allison@lohutok.net" <allison@lohutok.net>,
"alexios.zavras@intel.com" <alexios.zavras@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"namit@vmware.com" <namit@vmware.com>,
Michael Kelley <mikelley@microsoft.com>,
Long Li <longli@microsoft.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: RE: [RESEND][PATCH v3] x86/apic/flat64: Add back the early_param("apic", parse_apic)
Date: Mon, 7 Sep 2020 06:30:47 +0000 [thread overview]
Message-ID: <KU1P153MB01207E71069B0883E44218E4BF280@KU1P153MB0120.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87mu3ys391.fsf@nanos.tec.linutronix.de>
> From: Thomas Gleixner <tglx@linutronix.de>
> Sent: Friday, July 17, 2020 6:03 AM
> [...]
Hi, I'm very sorry for this extremely late reply -- I was sidetracked by something
else and I just had a chance to revisit the issue. Thank you tglx for the comments
and suggestions, which I think are reasonable. I realized this patch is problematic.
The good news is that the LAPIC emulation bug has been fixed in the latest version
of Hyper-V and now kdump can work reliably. I think the hypervisor fix would be
backported to old Hyper-V versions, so hopefully this won't be an issue over time.
Thanks,
-- Dexuan
prev parent reply other threads:[~2020-09-07 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 18:21 [RESEND][PATCH v3] x86/apic/flat64: Add back the early_param("apic", parse_apic) Dexuan Cui
2020-07-13 10:31 ` Wei Liu
2020-07-17 13:03 ` Thomas Gleixner
2020-09-07 6:30 ` Dexuan Cui [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=KU1P153MB01207E71069B0883E44218E4BF280@KU1P153MB0120.APCP153.PROD.OUTLOOK.COM \
--to=decui@microsoft.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--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).