From: Ingo Molnar <mingo@elte.hu>
To: Robin Holt <holt@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: tglx@linutronix.de, Jack Steiner <steiner@sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 0/8] x86: UV - XPC fixes with related support functionality V2.
Date: Mon, 23 Nov 2009 19:10:49 +0100 [thread overview]
Message-ID: <20091123181049.GA5220@elte.hu> (raw)
In-Reply-To: <20091123180321.GB15594@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> * Robin Holt <holt@sgi.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
next prev parent reply other threads:[~2009-11-23 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 17:31 [patch 0/8] x86: UV - XPC fixes with related support functionality V2 Robin Holt
2009-11-19 17:31 ` [patch 1/8] x86: UV - Introduce a means to translate from gpa -> socket_paddr Robin Holt
2009-11-19 17:31 ` [patch 2/8] x86: UV - XPC needs to provide an abstraction for uv_gpa Robin Holt
2009-11-19 17:32 ` [patch 3/8] x86: UV - Introduce uv_gpa_is_mmr Robin Holt
2009-11-19 17:32 ` [patch 4/8] X86: UV - Implement a gru_read_gpa kernel function Robin Holt
2009-11-19 17:32 ` [patch 5/8] x86: UV - Update XPC to handle updated BIOS interface Robin Holt
2009-11-19 17:32 ` [patch 6/8] x86: UV - XPC NULL deref when mesq becomes empty Robin Holt
2009-11-19 17:32 ` [patch 7/8] X86: UV - xpc_make_first_contact hang due to not accepting ACTIVE state Robin Holt
2009-11-19 17:32 ` [patch 8/8] X86: UV - XPC receive message reuse triggers invalid BUG_ON() Robin Holt
2009-11-23 18:03 ` [patch 0/8] x86: UV - XPC fixes with related support functionality V2 Ingo Molnar
2009-11-23 18:10 ` Ingo Molnar [this message]
2009-11-23 23:57 ` Robin Holt
2009-11-24 7:19 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-11-24 1:39 Robin Holt
2009-12-15 17:04 ` Robin Holt
2009-12-15 17:06 ` Robin Holt
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=20091123181049.GA5220@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=holt@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
/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