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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 23 Nov 2009 19:10:49 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Robin Holt <holt@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	tglx@...utronix.de, Jack Steiner <steiner@....com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch 0/8] x86: UV - XPC fixes with related support
 functionality V2.


* Ingo Molnar <mingo@...e.hu> wrote:

> * Robin Holt <holt@....com> wrote:
> 
> > 
> > The UV BIOS has been updated to implement some of our interface
> > functionality differently than originally expected.  These patches
> > update us to that working bios and include a few minor bug fixes
> > which prevent us from doing significant testing on real hardware.
> > 
> > Changes from V1:
> > 
> > - Actually include the patch introducing the gru_read_gpa.  This
> >   was missed in the V1 submission.
> > 
> > - One additional BIOS change has the OS no longer passing blade
> >   to the BIOS when registering a message queue watchlist.
> 
> Note, the patches are a bit hard to review without diffstats - mind 
> generating them for future patches? Also, putting a 'summary' diffstat 
> (the total diffstat effect of all patches) into the 0/8 description mail 
> is common courtesy that is much welcome by maintainers and reviewers as 
> well.

Ah, sorry - they were there, just merged together with the patch so i 
missed them.

Regarding the patches - i still very much dislike how the code 
interfaces to the 'BIOS'. The drivers/misc/sgi-xp/ code looks rather 
messy.

Why isnt a pure hardware interface exposed, as both hpa and me suggested 
in the past?

Anyway ... these bits got merged via -mm in the past so i guess it could 
be done there in the future too - the series does not look horrible - 
but the whole concept ought to be done in a cleaner way.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ