From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755963AbdKCKSA (ORCPT ); Fri, 3 Nov 2017 06:18:00 -0400 Received: from mail-wr0-f195.google.com ([209.85.128.195]:55066 "EHLO mail-wr0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755920AbdKCKRy (ORCPT ); Fri, 3 Nov 2017 06:17:54 -0400 X-Google-Smtp-Source: ABhQp+RI5Eqfwy3Sq+AGH+3SqxPGMP/kfERwTUHlnbxe8ScYnwr29wb+kkn0jWwdY0RSvLXPJoIkng== Date: Fri, 3 Nov 2017 11:17:49 +0100 From: Ingo Molnar To: Ricardo Neri Cc: Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Andy Lutomirski , Borislav Petkov , Peter Zijlstra , Andrew Morton , Brian Gerst , Chris Metcalf , Dave Hansen , Paolo Bonzini , Masami Hiramatsu , Huang Rui , Jiri Slaby , Jonathan Corbet , "Michael S. Tsirkin" , Paul Gortmaker , Vlastimil Babka , Chen Yucong , "Ravi V. Shankar" , Shuah Khan , linux-kernel@vger.kernel.org, x86@kernel.org, ricardo.neri@intel.com, Adam Buchbinder , Colin Ian King , Lorenzo Stoakes , Qiaowei Ren , Arnaldo Carvalho de Melo , Adrian Hunter , Kees Cook , Thomas Garnier , Dmitry Vyukov Subject: Re: [PATCH v10 02/13] x86/insn-eval: Compute linear address in several utility functions Message-ID: <20171103101749.tukshf4rqgbhbcmu@gmail.com> References: <1509148310-30862-1-git-send-email-ricardo.neri-calderon@linux.intel.com> <1509148310-30862-3-git-send-email-ricardo.neri-calderon@linux.intel.com> <20171102085108.pgiem4kplrcmbzh6@gmail.com> <20171103024440.GA24896@voyager> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171103024440.GA24896@voyager> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ricardo Neri wrote: > On Thu, Nov 02, 2017 at 09:51:08AM +0100, Ingo Molnar wrote: > > > > * Ricardo Neri wrote: > > > > > + /* > > > + * -EDOM means that we must ignore the address_offset. In such a case, > > > + * in 64-bit mode the effective address relative to the RIP of the > > > + * following instruction. > > > + */ > > > + if (*regoff == -EDOM) { > > > + if (user_64bit_mode(regs)) > > > + tmp = (long)regs->ip + insn->length; > > > + else > > > + tmp = 0; > > > + } else if (*regoff < 0) { > > > + return -EINVAL; > > > + } else { > > > + tmp = (long)regs_get_register(regs, *regoff); > > > + } > > > > > + else > > > + indx = (long)regs_get_register(regs, indx_offset); > > > > This and subsequent patches include a disgustly insane amount of type casts - why? > > > > For example here 'tmp' is 'long', while regs_get_register() returns > > 'unsigned long', but no type cast is necessary for that. > > > > > + ret = get_eff_addr_modrm(insn, regs, &addr_offset, > > > + &eff_addr); > > One of the goals of this series is to have the ability to compute 16-bit, 32-bit > and 64-bit addresses. I put lost of casts, between signed and unsigned types, > between 64-bit and 32-bit and 16-bit casts. After seeing your comment I have gone > through the code and I have removed most of the casts. Instead I will use masks. > I will also inspect the resulting assembly code to make sure the arithmetic is > performed in the address size pertinent to each case. Well, casts are probably fine when the goal is to zero out high bits - but the ones I quoted converted types of the same with. For register values it would also probably be cleaner to use the u8, u16, u32 and u64 types instead of char/short/int/long - this goes hand in hand with how the instructions are documented in the SDMs. Thanks, Ingo