From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Hedi Berriche <hedi@sgi.com>, Dimitri Sivanich <sivanich@sgi.com>
Subject: Re: [PATCH 1/1] X86, UV: Update UV APIC driver check
Date: Tue, 24 Mar 2015 12:57:38 -0700 [thread overview]
Message-ID: <5511C1B2.8040706@sgi.com> (raw)
In-Reply-To: <20150324063231.GA26302@gmail.com>
On 3/23/2015 11:32 PM, Ingo Molnar wrote:
>
> * Mike Travis <travis@sgi.com> wrote:
>
>> Fix a bug in the oem check function that determines if the system
>> is a UV system and the BIOS is compatible with the kernel's UV apic
>> driver. This prevents some possibly obscure panics and guards the
>> system against being started on SGI hardware that does not have the
>> required kernel support. [...]
>
> This would be one patch ...
>
>> [...] Also add update for new UV3000 system.
>
> ... and that's a second patch.
The second one is purely cosmetic. The same UV HUB is used for
UV2000 and UV3000 so all this is doing is avoiding confusion when
someone thinks the kernel should be supporting UV3000.
> n
>> The first "OEM" check was also optimized to return faster if the
>> system is not an SGI or UV system.
>
> Looks like this mixes up with the fix and can be part of the first
> patch - although ideally it would have been good to create a 3 patch
> series to preserve the separation of the various changes.
If you think that's necessary, then I can do that. Overall the changes
are very minimal and basically guard against whatever changes will be
in UV4 or possible non-UV SGI systems (using the "SGI" OEM label in BIOS).
>
> Thanks,
>
> Ingo
>
prev parent reply other threads:[~2015-03-24 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150323172142.904806569@asylum.americas.sgi.com>
2015-03-23 17:21 ` [PATCH 1/1] X86, UV: Update UV APIC driver check Mike Travis
2015-03-24 6:32 ` Ingo Molnar
2015-03-24 19:57 ` Mike Travis [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=5511C1B2.8040706@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sivanich@sgi.com \
--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