[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH OSSTEST 1/2] exanime: test for SMT and add a host flag


  • To: Ian Jackson <ian.jackson@xxxxxxxxxx>
  • From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Date: Wed, 15 Apr 2020 15:47:22 +0200
  • Authentication-results: esa3.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=roger.pau@xxxxxxxxxx; spf=Pass smtp.mailfrom=roger.pau@xxxxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxx
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 15 Apr 2020 13:47:38 +0000
  • Ironport-sdr: peEHnSpgsP5lzsl00C1ScIXEZwpEd47Ov3D29kI8RK90Ex6aHkSs0+gYSFrh8E7oYrAFpg3XDa LNvsiFAWizHgiIGxMD8vdDdhrZgpW8kKS17eBo/mH7JCKToXjpwWbZY+OlmgwVV81ozsa3Pf0a tZKcQpLKihU7QlPy5UXlp17vFLwsPKo/oZORIEcnVEOa3gFcXwwoUm+Z8gP5xiyPUXDV+KhNaG k7SrTK8xYl2ORD0JEKuptWxRg/b0NRLla1cce8P8wJdfGO4StX3TSar0cfTCGS8ALFClVzgDJZ rsU=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Wed, Apr 15, 2020 at 02:04:35PM +0100, Ian Jackson wrote:
> Roger Pau Monne writes ("[PATCH OSSTEST 1/2] exanime: test for SMT and add a 
> host flag"):
> > Check if hosts have SMT based on the number of threads per core. A
> > value of threads per core different than 0 implies SMT support.
> ...
> > +logm("$ho->{Ident} threads per core: $threads");
> > +hostflag_putative_record($ho, "smt", !!$threads);
> 
> This code LGTM but I wonder if it would be a good idea to start
> namespacing these kind of hardware feature flags.  cpu-*, hardware-*,
> feature-* maybe ?  Would you care to make a suggestion ?

cpu-smt seems fine if we plan to do similar namespacing with other
hardware features, I could see cpu-{smt,vmx,svm} and
devices-{iommu,sriov,ats} or some such for example.

If OTOH we don't want to be that fine grained I think
hw-{smt,iommu,vmx,...} would also be fine.

Not sure whether this has helped much. I guess my vote would be for
cpu-smt namespace.

Thanks, Roger.



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.