From: Avi Kivity <avi@redhat.com>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, alan@linux.intel.com, agraf@suse.de,
benh@kernel.crashing.org, dcb314@hotmail.com,
mtosatti@redhat.com, paulus@samba.org,
KVM list <kvm@vger.kernel.org>
Subject: Re: + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree
Date: Wed, 25 Jul 2012 11:32:05 +0300 [thread overview]
Message-ID: <500FAF05.8010304@redhat.com> (raw)
In-Reply-To: <20120724210054.4164420004E@hpza10.eem.corp.google.com>
On 07/25/2012 12:00 AM, akpm@linux-foundation.org wrote:
> The patch titled
> Subject: ppc: e500_tlb memset clears nothing
> has been added to the -mm tree. Its filename is
> ppc-e500_tlb-memset-clears-nothing.patch
>
The kvm tree is maintained. Alex, please pick up this patch; I guess
it's 3.6 material.
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> The -mm tree is included into linux-next and is updated
> there every 3-4 working days
>
> ------------------------------------------------------
> From: Alan Cox <alan@linux.intel.com>
> Subject: ppc: e500_tlb memset clears nothing
>
> Put the parameters the right way around
>
> Addresses https://bugzilla.kernel.org/show_bug.cgi?id=44031
>
> Reported-by: David Binderman <dcb314@hotmail.com>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> Cc: Avi Kivity <avi@redhat.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: Alexander Graf <agraf@suse.de>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Paul Mackerras <paulus@samba.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> arch/powerpc/kvm/e500_tlb.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff -puN arch/powerpc/kvm/e500_tlb.c~ppc-e500_tlb-memset-clears-nothing arch/powerpc/kvm/e500_tlb.c
> --- a/arch/powerpc/kvm/e500_tlb.c~ppc-e500_tlb-memset-clears-nothing
> +++ a/arch/powerpc/kvm/e500_tlb.c
> @@ -322,11 +322,11 @@ static inline void kvmppc_e500_ref_relea
> static void clear_tlb1_bitmap(struct kvmppc_vcpu_e500 *vcpu_e500)
> {
> if (vcpu_e500->g2h_tlb1_map)
> - memset(vcpu_e500->g2h_tlb1_map,
> - sizeof(u64) * vcpu_e500->gtlb_params[1].entries, 0);
> + memset(vcpu_e500->g2h_tlb1_map, 0,
> + sizeof(u64) * vcpu_e500->gtlb_params[1].entries);
> if (vcpu_e500->h2g_tlb1_rmap)
> - memset(vcpu_e500->h2g_tlb1_rmap,
> - sizeof(unsigned int) * host_tlb_params[1].entries, 0);
> + memset(vcpu_e500->h2g_tlb1_rmap, 0,
> + sizeof(unsigned int) * host_tlb_params[1].entries);
> }
>
> static void clear_tlb_privs(struct kvmppc_vcpu_e500 *vcpu_e500)
> _
> Subject: Subject: ppc: e500_tlb memset clears nothing
>
--
error compiling committee.c: too many arguments to function
next parent reply other threads:[~2012-07-25 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120724210054.4164420004E@hpza10.eem.corp.google.com>
2012-07-25 8:32 ` Avi Kivity [this message]
2012-07-25 9:00 ` + ppc-e500_tlb-memset-clears-nothing.patch added to -mm tree Alexander Graf
2012-07-25 9:20 ` Avi Kivity
2012-07-25 10:12 ` Alan Cox
2012-07-25 10:20 ` Avi Kivity
2012-07-25 10:10 ` Alan Cox
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=500FAF05.8010304@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=dcb314@hotmail.com \
--cc=kvm@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).