From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Travis <travis@sgi.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Ingo Molnar <mingo@elte.hu>, Russ Anderson <rja@sgi.com>,
Dave Airlie <airlied@redhat.com>, Alex Chiang <achiang@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Robin Holt <holt@sgi.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Adam Jackson <ajax@nwnk.net>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Gaetan Nadon <memsize@videotron.ca>,
"H. Peter Anvin" <hpa@zytor.com>,
Aaron Plattner <aplattner@nvidia.com>,
Jack Steiner <steiner@sgi.com>,
Tiago Vignatti <tiago.vignatti@nokia.com>,
Cliff Wickman <cpw@sgi.com>,
Matthew Wilcox <willy@linux.intel.com>,
Christian Zander <chzander@nvidia.com>,
Yu Zhao <yu.zhao@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH 1/4] pci: Update pci_set_vga_state to call arch functions
Date: Mon, 25 Jan 2010 16:17:02 -0800 [thread overview]
Message-ID: <20100125161702.e070985e.akpm@linux-foundation.org> (raw)
In-Reply-To: <4B5E32D0.8040401@sgi.com>
On Mon, 25 Jan 2010 16:09:52 -0800
Mike Travis <travis@sgi.com> wrote:
> >
> > Still, a neater solution might be
> >
> > int arch_pci_set_vga_state(...) __weak
> > {
> > return 0;
> > }
> >
> > and then resolve it at linkage time?
> >
> >
>
> Wouldn't the linked in stronger function then need to surround
> the UV register updating with "if (uv_system)"?
If the file which implements arch_pci_set_vga_state() is present in
vmlinux on non-uv systems then yes.
Presumably that file is arch/x86/kernel/apic/x2apic_uv_x.c, although
that might later become a problem if other sub-architectures a) want to
get at this hook and b) can be linked into vmlinux along with
arch/x86/kernel/apic/x2apic_uv_x.o. But such a kernel wouldn't
actually link, so we'll need to address it at that stage.
If this is a UV-specific hack which other architectures and
sub-architectures are unlikely to need (seems that way?) then I'd be
going for something whcih is simple and minimal.
next prev parent reply other threads:[~2010-01-26 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100118183412.560438000@alcatraz.americas.sgi.com>
2010-01-18 18:34 ` [PATCH 1/4] pci: Update pci_set_vga_state to call arch functions Mike Travis
2010-01-25 23:52 ` Andrew Morton
2010-01-26 0:09 ` Mike Travis
2010-01-26 0:17 ` Andrew Morton [this message]
2010-01-18 18:34 ` [PATCH 2/4] x86_64 UV: Update UV arch to target Legacy VGA I/O correctly Mike Travis
2010-01-25 23:54 ` Andrew Morton
2010-01-26 0:05 ` Mike Travis
2010-01-26 0:22 ` H. Peter Anvin
2010-01-26 17:54 ` Mike Travis
2010-01-18 18:34 ` [PATCH 3/4] vgaarb: Fix VGA Arbiter to accept PCI Domains other than 0 Mike Travis
2010-01-18 18:34 ` [PATCH 4/4] vgaarb: Add user selectability of the number of GPUS in a system Mike Travis
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=20100125161702.e070985e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=achiang@hp.com \
--cc=airlied@redhat.com \
--cc=ajax@nwnk.net \
--cc=aplattner@nvidia.com \
--cc=benh@kernel.crashing.org \
--cc=chzander@nvidia.com \
--cc=cpw@sgi.com \
--cc=gorcunov@openvz.org \
--cc=holt@sgi.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=memsize@videotron.ca \
--cc=mingo@elte.hu \
--cc=rja@sgi.com \
--cc=rjw@sisk.pl \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=tiago.vignatti@nokia.com \
--cc=travis@sgi.com \
--cc=willy@linux.intel.com \
--cc=x86@kernel.org \
--cc=yu.zhao@intel.com \
/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