From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752205AbcAMXdS (ORCPT ); Wed, 13 Jan 2016 18:33:18 -0500 Received: from mail-oi0-f50.google.com ([209.85.218.50]:35419 "EHLO mail-oi0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107AbcAMXdR (ORCPT ); Wed, 13 Jan 2016 18:33:17 -0500 MIME-Version: 1.0 In-Reply-To: <20160111105105.GB29448@gmail.com> References: <20160111105105.GB29448@gmail.com> From: Andy Lutomirski Date: Wed, 13 Jan 2016 15:32:56 -0800 Message-ID: Subject: Re: [RFC 09/13] x86/mm: Disable interrupts when flushing the TLB using CR3 To: Ingo Molnar Cc: Linus Torvalds , Oleg Nesterov , X86 ML , Dave Hansen , Borislav Petkov , Linux Kernel Mailing List , "linux-mm@kvack.org" , Brian Gerst Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 11, 2016 at 2:51 AM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> >> Or is there some reason you wanted the odd flags version? If so, that >> >> should be documented. >> > >> > What do you mean "odd"? >> >> It's odd because it makes no sense for non-pcid (christ, I wish Intel had just >> called it "asid" instead, "pcid" always makes me react to "pci"), and I think it >> would make more sense to pair up the pcid case with the invpcid rather than have >> those preemption rules here. > > The naming is really painful, so a trivial suggestion: could we just name all the > Linux side bits 'asid' or 'ctx_id' (even in x86 arch code) and only use 'PCID' > nomenclature in the very lowest level code? I'd be okay with "pctx_id" or "pctxid" for this, I think. I'd like to at least make it somewhat obvious how it maps back to hardware. FWIW, I'd guess that Intel deviated from convention because their actual address space id is (vpid, pcid), and calling it (vpid, asid) might have been slightly confusing. Or not. --Andy