From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752353AbcGANLZ (ORCPT ); Fri, 1 Jul 2016 09:11:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41517 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751699AbcGANLY (ORCPT ); Fri, 1 Jul 2016 09:11:24 -0400 Date: Fri, 1 Jul 2016 15:11:20 +0200 From: Radim =?utf-8?B?S3LEjW3DocWZ?= To: Paolo Bonzini Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, "Lan, Tianyu" , Igor Mammedov , Jan Kiszka , Peter Xu Subject: Re: [PATCH v1 06/11] KVM: x86: use hardware-compatible format for APIC ID register Message-ID: <20160701131119.GC27840@potion> References: <20160630205429.16480-1-rkrcmar@redhat.com> <20160630205429.16480-7-rkrcmar@redhat.com> <733b706a-f30f-3854-5fc7-402d6b5fd79a@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <733b706a-f30f-3854-5fc7-402d6b5fd79a@redhat.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 01 Jul 2016 13:11:23 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2016-07-01 10:33+0200, Paolo Bonzini: > On 30/06/2016 22:54, Radim Krčmář wrote: >> +static void __kvm_apic_state_fixup(struct kvm_vcpu *vcpu, >> + struct kvm_lapic_state *s, bool set) >> +{ >> + if (apic_x2apic_mode(vcpu->arch.apic)) { >> + u32 *id = (u32 *)(s->regs + APIC_ID); >> + if (set) >> + *id >>= 24; >> + else >> + *id <<= 24; >> + } > > When setting, this should read from the apic_base being set. So I think > you cannot use apic_x2apic_mode. apic_x2apic_mode uses apic_base MSR, so its value does not depend on LAPIC_SET/GET. I don't like the dependency much, but all combinations of values/orders should work well. > With this change, you don't need the struct kvm_vcpu argument now; add a > struct kvm argument instead in patch 10. I don't think we can use hardware-compatible format in API without knowing the x2apic mode through vcpu. (The big endian format could do without knowing apic mode.) >> @@ -2780,6 +2780,7 @@ static int kvm_vcpu_ioctl_get_lapic(struct kvm_vcpu *vcpu, >> kvm_x86_ops->sync_pir_to_irr(vcpu); >> >> memcpy(s->regs, vcpu->arch.apic->regs, sizeof *s); >> + kvm_apic_state_get_fixup(vcpu, s); > > Instead of kvm_apic_state_get/set_fixup, group the memcpy and > __kvm_apic_state_fixup in a new function kvm_apic_get_state(struct > kvm_lapic *apic, char *regs). Ok. >> return 0; >> } >> @@ -2787,6 +2788,7 @@ static int kvm_vcpu_ioctl_get_lapic(struct kvm_vcpu *vcpu, >> static int kvm_vcpu_ioctl_set_lapic(struct kvm_vcpu *vcpu, >> struct kvm_lapic_state *s) >> { >> + kvm_apic_state_set_fixup(vcpu, s); >> kvm_apic_post_state_restore(vcpu, s); > > ... and likewise merge these two in a refactored > kvm_apic_post_state_restore called kvm_apic_set_state(struct kvm_lapic > *apic, char *regs), by calling __kvm_apic_state_fixup before > kvm_apic_post_state_restore's memcpy. > > With these changes I guess there's no need for the underscores in > __kvm_apic_state_fixup. Yes, good idea. > And you can also change the struct > kvm_lapic_state pointer in the function to a char *. Ok, I'll pass just s->regs. Thanks.