LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: next-20081030: voyager compile busted
Date: Thu, 30 Oct 2008 16:47:46 -0500	[thread overview]
Message-ID: <1225403266.19324.42.camel@localhost.localdomain> (raw)
In-Reply-To: <490A2A30.5040905@zytor.com>

On Thu, 2008-10-30 at 14:42 -0700, H. Peter Anvin wrote:
> James Bottomley wrote:
> > 
> > Before you advocate this, think what it would entail.  Voyager replaces
> > (and has to replace because its not apic based) the entirety of smp.c
> > and smpboot.c ... they'd all have to be abstracted through function
> > pointers.
> > 
> 
> ... or through patched direct calls, which is of course also a possibility.

Yes ... been having IRC conversations about that.  We'd need to use
runtime patching to fix the performance regressions virtualisation has
been causing us first ... but then we could use it for voyager.

James



  reply	other threads:[~2008-10-30 21:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  6:30 linux-next: Tree for October 30 Stephen Rothwell
2008-10-30 18:03 ` next-20081030: voyager compile busted Alexey Dobriyan
2008-10-30 20:24   ` James Bottomley
2008-10-30 20:52     ` Ingo Molnar
2008-10-30 20:58       ` James Bottomley
2008-10-30 21:07         ` Ingo Molnar
2008-10-30 21:21           ` James Bottomley
2008-10-30 21:42             ` H. Peter Anvin
2008-10-30 21:47               ` James Bottomley [this message]
2008-10-30 21:50                 ` H. Peter Anvin
2008-10-30 22:40                   ` Ingo Molnar
2008-10-31 17:42                     ` James Bottomley
2008-10-30 21:24       ` Alexey Dobriyan
2008-10-30 23:42   ` Tony Breeds
2008-10-30 23:55 ` linux-next: Tree for October 30 Randy Dunlap
2008-10-31  6:25   ` Greg KH
2008-10-31 16:40     ` Greg KH

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=1225403266.19324.42.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=adobriyan@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.org \
    --subject='Re: next-20081030: voyager compile busted' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).