Content-Type: multipart/mixed; boundary="===============3429861115353641505=="
MIME-Version: 1.0
From: Michael S. Tsirkin <mst@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v5 05/14] KVM: X86: Implement ring-based dirty memory tracking
Date: Tue, 10 Mar 2020 02:31:55 -0400
Message-ID: <20200310022931-mutt-send-email-mst@kernel.org>
In-Reply-To: <20200309213554.GF4206@xz-x1>
List-Id: <oe-kbuild-all.lists.linux.dev>

--===============3429861115353641505==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 09, 2020 at 05:35:54PM -0400, Peter Xu wrote:
> I'll probably also
> move KVM_DIRTY_LOG_PAGE_OFFSET=3D=3D0 definition to uapi/linux/kvm.h.


IMHO KVM_DIRTY_LOG_PAGE_OFFSET is kind of pointless anyway - =

we won't be able to move data around just by changing the
uapi value since userspace isn't
recompiled when kernel changes ...


> -- =

> Peter Xu

--===============3429861115353641505==--