Re: [PATCH for Xen 4.6 2/5] tools/libxl: fix socket display error for CMT

[Dario Faggioli <dario.faggioli@citrix.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1412 bytes --]

On Mon, 2015-09-28 at 19:54 +0800, Chao Peng wrote:

> diff --git a/tools/libxl/xl_cmdimpl.c b/tools/libxl/xl_cmdimpl.c
> index 2706759..c72d3df 100644

> @@ -8228,9 +8228,9 @@ static void
> psr_cmt_print_domain_info(libxl_dominfo *dominfo,
>  
>  static int psr_cmt_show(libxl_psr_cmt_type type, uint32_t domid)
>  {
> -    uint32_t i, socketid, nr_sockets, total_rmid;
> +    uint32_t i, socketid, total_rmid;
>      uint32_t l3_cache_size;
> -    libxl_physinfo info;
> +    libxl_bitmap socketmap;
>      int rc, nr_domains;
>  
>      if (!libxl_psr_cmt_enabled(ctx)) {
> @@ -8244,41 +8244,38 @@ static int psr_cmt_show(libxl_psr_cmt_type
> type, uint32_t domid)
>          return -1;
>      }
>  
> -    libxl_physinfo_init(&info);
> -    rc = libxl_get_physinfo(ctx, &info);
> +    libxl_socket_bitmap_alloc(ctx, &socketmap, 0);
> +    rc = libxl_socket_bitmap_fill(ctx, &socketmap);
>
Shouldn't socketmap be initied with libxl_bitmap_init() before being
allocated and used?

Not doing so is certainly not an issue, in this case, but AFAIR, we
always require that for libxl types, don't we?

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel