linux-kernel - Re: [PATCH 0/8] x86/platform/UV: Update UV Hubless System Support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 5 Sep 2019 10:19:14 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Mike Travis <mike.travis@....com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Borislav Petkov <bp@...en8.de>,
        Dimitri Sivanich <dimitri.sivanich@....com>,
        Russ Anderson <russ.anderson@....com>,
        Hedi Berriche <hedi.berriche@....com>,
        Steve Wahl <steve.wahl@....com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 0/8] x86/platform/UV: Update UV Hubless System Support


* Mike Travis <mike.travis@....com> wrote:

> 
> 
> On 9/3/2019 12:47 AM, Ingo Molnar wrote:
> > 
> > * Mike Travis <mike.travis@....com> wrote:
> > 
> > > 
> > > These patches support upcoming UV systems that do not have a UV HUB.
> > > 
> > > 	* Save OEM_ID from ACPI MADT probe
> > > 	* Return UV Hubless System Type
> > > 	* Add return code to UV BIOS Init function
> > > 	* Setup UV functions for Hubless UV Systems
> > > 	* Add UV Hubbed/Hubless Proc FS Files
> > > 	* Decode UVsystab Info
> > > 	* Account for UV Hubless in is_uvX_hub Ops
> > 
> > Beyond addressing Christoph's feedback, please also make sure the series
> > applies cleanly to tip:master, because right now it doesn't.
> > 
> > Thanks,
> > 
> > 	Ingo
> > 
> 
> I will do this, and retest.  Currently we are using the latest upstream
> version but obviously that thinking is flawed, since we are hoping to
> get into the next merge period.

You are really cutting it close timing-wise ... unless by 'next' you mean 
not v5.4 but v5.5?

> I also noticed that the MAINTAINERS list for UV is out of date, I will 
> tend to that too.

Thanks!

	Ingo