From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v4 3/4] tools: add tools support for Intel CDP Date: Thu, 24 Sep 2015 13:07:42 +0100 Message-ID: <1443096462.25250.7.camel@citrix.com> References: <1442482536-12024-1-git-send-email-he.chen@linux.intel.com> <1442482536-12024-4-git-send-email-he.chen@linux.intel.com> <1443092450.10338.276.camel@citrix.com> <5603FFB302000078000A5446@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Zf5JS-0001ze-P3 for xen-devel@lists.xenproject.org; Thu, 24 Sep 2015 12:07:46 +0000 In-Reply-To: <5603FFB302000078000A5446@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , He Chen Cc: wei.liu2@citrix.com, stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xenproject.org, chao.p.peng@linux.intel.com, keir@xen.org List-Id: xen-devel@lists.xenproject.org On Thu, 2015-09-24 at 05:50 -0600, Jan Beulich wrote: > > > > On 24.09.15 at 13:00, wrote: > > On Thu, 2015-09-17 at 17:35 +0800, He Chen wrote: > > > diff --git a/tools/libxl/libxl_psr.c b/tools/libxl/libxl_psr.c > > > index 3378239..62963cf 100644 > > > --- a/tools/libxl/libxl_psr.c > > > +++ b/tools/libxl/libxl_psr.c > > > @@ -87,6 +87,9 @@ static void libxl__psr_cat_log_err_msg(libxl__gc > > > *gc, > > > int err) > > > case EEXIST: > > > msg = "The same CBM is already set to this domain"; > > > break; > > > + case EINVAL: > > > + msg = "Unable to set code or data CBM when CDP is disabled"; > > > + break; > > > > These overloading of the errno values are getting a bit thinly > > stretched. > > The more so that EINVAL has a widely used more generic meaning. > > > > Hypervisor maintainers, what is your opinion of this? > > > > Since this is a sysctl I suppose we could consider adding a new PSR > > specific error type with appropriate codes? > > I'd prefer using recognizable -E... values; _If_ the -E values somehow map sensibly onto the PSR errors, otherwise they aren't really recognisable any more. > a specific error type > to me seems to go too far. Surely out of the several dozen > possibilities a handful of not-so-common ones can be picked? I was thinking in particular EINVAL was not in the not-so-common bracket. The current code already uses 9 values FWIW. Ian.