public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat•com>
To: Lan Tianyu <tianyu.lan@intel•com>,
	guangrong.xiao@linux•intel.com, agraf@suse•com,
	benh@kernel•crashing.org, gleb@kernel•org, hpa@zytor•com,
	kvm-ppc@vger•kernel.org, kvm@vger•kernel.org,
	linux-kernel@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
	mingo@redhat•com, mpe@ellerman•id.au, paulus@samba•org,
	tglx@linutronix•de, x86@kernel•org
Subject: Re: [PATCH 0/7] KVM/X86/PPC: Clear up kvm mmu memory barriers and update related comments
Date: Mon, 14 Mar 2016 14:03:12 +0100	[thread overview]
Message-ID: <56E6B690.70208@redhat.com> (raw)
In-Reply-To: <1457838631-26775-1-git-send-email-tianyu.lan@intel.com>



On 13/03/2016 04:10, Lan Tianyu wrote:
> This series is to clear up kvm mmu memory barriers.
> 1) Remove redundant barrier (PATCH 1)
> 2) Replace origin barrier functions with preferrable ones (PATCH 2, 3, 5)
> 3) Fix unpaired barriers (PATCH 4)
> 4) Update or add barrier related comments (PATCH 6, 7)

Thanks, this looks pretty good!  I will apply it for 4.6 if I have to
send two pull requests during this merge window; otherwise, it will have
to wait for the next merge window.

Paolo

      parent reply	other threads:[~2016-03-14 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-13  3:10 [PATCH 0/7] KVM/X86/PPC: Clear up kvm mmu memory barriers and update related comments Lan Tianyu
2016-03-13  3:10 ` [PATCH 7/7] KVM/PPC: update the comment of memory barrier in the kvmppc_prepare_to_enter() Lan Tianyu
2016-03-14 13:03 ` Paolo Bonzini [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=56E6B690.70208@redhat.com \
    --to=pbonzini@redhat$(echo .)com \
    --cc=agraf@suse$(echo .)com \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=gleb@kernel$(echo .)org \
    --cc=guangrong.xiao@linux$(echo .)intel.com \
    --cc=hpa@zytor$(echo .)com \
    --cc=kvm-ppc@vger$(echo .)kernel.org \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mingo@redhat$(echo .)com \
    --cc=mpe@ellerman$(echo .)id.au \
    --cc=paulus@samba$(echo .)org \
    --cc=tglx@linutronix$(echo .)de \
    --cc=tianyu.lan@intel$(echo .)com \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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