All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Avi Kivity <avi@qumranet.com>,
	linux-next@vger.kernel.org,
	Kumar Gala <galak@kernel.crashing.org>
Subject: Re: linux-next: manual merge of the kvm tree
Date: Mon, 22 Dec 2008 16:03:42 -0600	[thread overview]
Message-ID: <1229983422.7181.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1229982095.4360.19.camel@pasglop>

On Tue, 2008-12-23 at 08:41 +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2008-12-22 at 15:39 -0600, Hollis Blanchard wrote:
> > On Mon, 2008-12-22 at 16:13 +1100, Benjamin Herrenschmidt wrote:
> > > On Mon, 2008-12-22 at 14:52 +1100, Stephen Rothwell wrote:
> > > > 
> > > > The former patch changes the _tlbia() to _tlbil_all() in
> > > > kvm_arch_vcpu_put().  The latter restructures this code.
> > > > 
> > > > I don't know enough to fix this up, so for today I have merely used the
> > > > kvm tree version.  Please come up with something better (if needed) and I
> > > > can use that as a merge resolution.
> > > 
> > > Hollis, can you have a look ? I suspect whatever is in the kvm tree is
> > > ok, provided it doesn't use the old names such as _tlbia() or _tlbie()
> > > which don't exist anymore for nohash...
> > 
> > I've stopped calling _tlbia() in KVM, so I think the easiest solution
> > would be to drop the KVM part of your patch, Ben.
> 
> Patch is in Paulus -next already so we'll have to do a manual resolve.

Who has to do it? My code should "win".

> Also, you'll need to include ../mm/mmu_decl.h to get to _tlbil_* ..
> sorry about that.

I don't want _tlb anything; I was only using _tlbia(), and I'm not any
more.

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2008-12-22 22:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  3:52 linux-next: manual merge of the kvm tree Stephen Rothwell
2008-12-22  5:13 ` Benjamin Herrenschmidt
2008-12-22 21:39   ` Hollis Blanchard
2008-12-22 21:41     ` Benjamin Herrenschmidt
2008-12-22 22:03       ` Hollis Blanchard [this message]
2008-12-22 22:11         ` Benjamin Herrenschmidt
2008-12-22 22:29         ` Paul Mackerras
2008-12-22 22:44           ` Hollis Blanchard
2008-12-23  0:07             ` Paul Mackerras
2008-12-23  1:02               ` Hollis Blanchard
2008-12-23  1:38                 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2009-06-12  2:57 Stephen Rothwell
2009-06-12  7:19 ` Avi Kivity
2009-01-02  0:44 Stephen Rothwell
2008-12-29  5:11 Stephen Rothwell
2008-11-25  6:49 Stephen Rothwell
2008-10-29  2:58 Stephen Rothwell
2008-10-29  9:55 ` Avi Kivity
2008-10-29 10:35   ` Stephen Rothwell
2008-10-15  5:27 Stephen Rothwell
2008-09-17  5:50 Stephen Rothwell
2008-09-17  5:24 Stephen Rothwell
2008-09-15  0:14 Stephen Rothwell
2008-09-15  6:53 ` Ingo Molnar
2008-09-12 19:50 Stephen Rothwell
2008-09-12 19:53 ` Arjan van de Ven
2008-09-12 19:59 ` Stephen Rothwell
2008-08-26  4:45 Stephen Rothwell
2008-08-26  7:39 ` Avi Kivity
2008-08-26  7:41   ` Stephen Rothwell
2008-08-15  4:46 Stephen Rothwell
2008-08-04  3:13 Stephen Rothwell
2008-07-22  3:43 Stephen Rothwell

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=1229983422.7181.7.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.