mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-kernel@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCHv5] SGI UV: TLB shootdown using broadcast assist unit - v5 delta
Date: Thu, 19 Jun 2008 12:30:51 +0200	[thread overview]
Message-ID: <20080619103051.GH15228@elte.hu> (raw)
In-Reply-To: <E1K8zIG-0006Fb-Fo@eag09.americas.sgi.com>


* Cliff Wickman <cpw@sgi.com> wrote:

> From: Cliff Wickman <cpw@sgi.com>
> 
> TLB shootdown for SGI UV.
> 
> This patch brings the code in Ingo's latest (June 18,2008) to v5
> 
> v1: 6/2 original
> v2: 6/3 corrections/improvements per Ingo's review
> v3: 6/4 split atomic operations off to a separate patch (Jeremy's review)
> v4: 6/12 include <mach_apic.h> rather than <asm/mach-bigsmp/mach_apic.h>
>          (fixes a !SMP build problem)
>          fix the index on uv_table_bases[blade]
> v5: 6/18 corrections/improvements per Ingo's second and third reviews
>     (includes closing the security hole in uv_ptc_proc_write())
>     (and adds tlb_uv.o to the Makefile)
> 
> Diffed against 2.6.26-rc6

could you please send a delta patch against tip/x86/uv - or just 
tip/master? You can pick it all up from:

  http://people.redhat.com/mingo/tip.git/README

it's better to have all these delta patches in a consecutive way, as 
everything up to your previous version of v5 has already been tested 
pretty thoroughly on non-UV hardware and is ready to be pushed into 
linux-next.

I'd suggest you name the new delta patch as v6, as there's a "v5" patch 
applied already.

( Also, you might want to check whether tip/master properly works on
  your simulator - to double-check whether the integration of x86/uv 
  changes with other x86 changes went fine. )

Thanks,

	Ingo

      reply	other threads:[~2008-06-19 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 15:09 Cliff Wickman
2008-06-19 10:30 ` Ingo Molnar [this message]

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=20080619103051.GH15228@elte.hu \
    --to=mingo@elte.hu \
    --cc=cpw@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®