From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Sakkinen Subject: Re: [PATCH v13 04/13] x86/sgx: Architectural structures Date: Wed, 5 Sep 2018 20:32:48 +0300 Message-ID: <20180905173248.GD11368@linux.intel.com> References: <20180827185507.17087-1-jarkko.sakkinen@linux.intel.com> <20180827185507.17087-5-jarkko.sakkinen@linux.intel.com> <83f5ec5f-1b31-15eb-7341-84ee9c7977e2@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <83f5ec5f-1b31-15eb-7341-84ee9c7977e2@intel.com> Sender: linux-kernel-owner@vger.kernel.org To: Dave Hansen Cc: Andy Shevchenko , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Platform Driver , sean.j.christopherson@intel.com, nhorman@redhat.com, npmccallum@redhat.com, linux-sgx@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Linux Kernel Mailing List List-Id: platform-driver-x86.vger.kernel.org On Tue, Sep 04, 2018 at 09:04:44AM -0700, Dave Hansen wrote: > On 09/03/2018 06:16 AM, Andy Shevchenko wrote: > >> + EBLOCK = 0x9, > >> + EPA = 0xA, > >> + EWB = 0xB, > >> + ETRACK = 0xC, > >> + EAUG = 0xD, > >> + EMODPR = 0xE, > >> + EMODT = 0xF, > >> +}; > > Hmm... This E prefix confuses me with (system wide) error codes. Has > > it been discussed before? If so, can you point on the conclusion why > > the current format is good? > > Making them SGX_EWHATEVER isn't a horrible idea. OK, going with that. /Jarkko