[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJu=L59=QGpWWW=ghPkFyhParXB4jMepQROiQ+5ZBh235Dmepg@mail.gmail.com>
Date: Mon, 22 Sep 2014 14:54:45 -0700
From: Andres Lagar-Cavilla <andreslc@...gle.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Gleb Natapov <gleb@...nel.org>, Radim Krcmar <rkrcmar@...hat.com>,
Rik van Riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrea Arcangeli <aarcange@...hat.com>,
Peter Feiner <pfeiner@...gle.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Andres Lagar-Cavilla <andreslc@...ogle.com>
Subject: Re: [PATCH v3] kvm: Fix page ageing bugs
On Mon, Sep 22, 2014 at 2:48 PM, Paolo Bonzini <pbonzini@...hat.com> wrote:
> Il 22/09/2014 22:26, Andres Lagar-Cavilla ha scritto:
>> + __entry->gfn = gfn;
>> + __entry->hva = ((gfn - slot->base_gfn) >>
>
> This must be <<.
Correct, thanks.
>
>> + PAGE_SHIFT) + slot->userspace_addr;
>
>> + /*
>> + * No need for _notify because we're called within an
>> + * mmu_notifier_invalidate_range_ {start|end} scope.
>> + */
>
> Why "called within"? It is try_to_unmap_cluster itself that calls
> mmu_notifier_invalidate_range_*, so "we're within an
> mmu_notifier_invalidate_range_start/end scope" sounds better, and it's
> also what you use in the commit message.
Also correct. V4...
Andres
>
> Paolo
--
Andres Lagar-Cavilla | Google Kernel Team | andreslc@...gle.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists