From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suravee Suthikulpanit Subject: Re: [PART1 RFC v2 03/10] svm: Introduce new AVIC VMCB registers Date: Tue, 15 Mar 2016 19:51:39 +0700 Message-ID: <56E8055B.6030208@amd.com> References: <1457124368-2025-1-git-send-email-Suravee.Suthikulpanit@amd.com> <1457124368-2025-4-git-send-email-Suravee.Suthikulpanit@amd.com> <56DDA1CF.4080207@redhat.com> <56E66B43.1000802@amd.com> <56E6ADB4.9040700@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , , To: Paolo Bonzini , , , , , Return-path: Received: from mail-bn1bon0064.outbound.protection.outlook.com ([157.56.111.64]:22266 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755348AbcCOMwK (ORCPT ); Tue, 15 Mar 2016 08:52:10 -0400 In-Reply-To: <56E6ADB4.9040700@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 03/14/2016 07:25 PM, Paolo Bonzini wrote: > > > On 14/03/2016 08:41, Suravee Suthikulpanit wrote: >> Any particular reason why you do not recommend the use of bit field? > > 1) The current coding style is generally not using bitfields > > 2) Having to review patches that change working code unrelated to AVIC > > 3) Most of the fields are not even used when AVIC is enabled, so the > benefit of the conversion is small. > > Paolo > Ok I'll remove the bit-field stuff from patch 3 and will get rid off patch 4. Thanks, Suravee