From: Ingo Molnar <mingo@kernel.org>
To: Alex Thorlton <athorlton@sgi.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Matt Fleming <matt@codeblueprint.co.uk>,
Dimitri Sivanich <sivanich@sgi.com>, Hedi Berriche <hedi@sgi.com>,
Mike Travis <travis@sgi.com>, Len Brown <len.brown@intel.com>,
linux-efi@vger.kernel.org
Subject: Re: [PATCH] Remove EFI memmap quirk for UV2+
Date: Tue, 19 Jan 2016 11:57:41 +0100 [thread overview]
Message-ID: <20160119105741.GA9122@gmail.com> (raw)
In-Reply-To: <20151214182053.GL164416@stormcage.americas.sgi.com>
* Alex Thorlton <athorlton@sgi.com> wrote:
> On Mon, Dec 14, 2015 at 09:41:58AM +0100, Ingo Molnar wrote:
> > * Alex Thorlton <athorlton@sgi.com> wrote:
> > Ok, this looks good to me and I'll apply it if it looks good to Matt as well.
>
> Cool! Thanks, Ingo.
>
> > Btw., can UV1 users fix this via a BIOS update?
>
> Unfortunately, no. This fix was put into UV2+ BIOS a while back, but we haven't
> spun a new UV1 BIOS for several years, and don't intend to release another
> version. This issue is likely going to follow UV1s to their grave :(
That's ok! We are responsible for past decisions/compromises/mistakes, as long as
the systems keep working, there's no problem with that.
Thanks,
Ingo
next prev parent reply other threads:[~2016-01-19 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 20:59 [PATCHv2] Remove EFI memmap quirk for UV Alex Thorlton
2015-12-11 20:59 ` [PATCH] Remove EFI memmap quirk for UV2+ Alex Thorlton
2015-12-14 8:41 ` Ingo Molnar
2015-12-14 15:56 ` Matt Fleming
2015-12-14 18:20 ` Alex Thorlton
2016-01-19 10:57 ` Ingo Molnar [this message]
2016-01-19 13:38 ` [tip:x86/urgent] x86/platform/UV: " tip-bot for Alex Thorlton
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=20160119105741.GA9122@gmail.com \
--to=mingo@kernel.org \
--cc=athorlton@sgi.com \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.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