Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 26 Oct 2020 16:29:21 +0000
From:   Wei Liu <wei.liu@kernel.org>
To:     Michael Kelley <mikelley@microsoft.com>
Cc:     linux-kernel@vger.kernel.org, tglx@linutronix.de,
        peterz@infradead.org, kys@microsoft.com, sthemmin@microsoft.com,
        wei.liu@kernel.org, mingo@redhat.com, bp@alien8.de, x86@kernel.org,
        hpa@zytor.com, linux-hyperv@vger.kernel.org
Subject: Re: [PATCH 1/1] x86/hyperv: Clarify comment on x2apic mode
Message-ID: <20201026162921.4kj47twy2wl43jji@liuwe-devbox-debian-v2>
References: <1603723972-81303-1-git-send-email-mikelley@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1603723972-81303-1-git-send-email-mikelley@microsoft.com>
User-Agent: NeoMutt/20180716
Precedence: bulk

On Mon, Oct 26, 2020 at 07:52:52AM -0700, Michael Kelley wrote:
> The comment about Hyper-V accessors is unclear regarding their
> potential use in x2apic mode, as is the associated commit message
> in e211288b72f1.  Clarify that while the architectural and
> synthetic MSRs are equivalent in x2apic mode, the full set of xapic
> accessors cannot be used because of register layout differences.
> 
> Fixes: e211288b72f1 ("x86/hyperv: Make vapic support x2apic mode")
> Signed-off-by: Michael Kelley <mikelley@microsoft.com>

Applied to hyperv-fixes. Thanks.