From: Jan Beulich <jbeulich@suse.com>
To: Carlo Nonato <carlo.nonato@minervasys.tech>
Cc: andrea.bastoni@minervasys.tech,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Marco Solieri <marco.solieri@minervasys.tech>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v8 07/13] xen/arm: add support for cache coloring configuration via device-tree
Date: Mon, 6 May 2024 14:11:33 +0200 [thread overview]
Message-ID: <99f6db77-23b8-4a18-b0b1-be4b9cd7f522@suse.com> (raw)
In-Reply-To: <20240502165533.319988-8-carlo.nonato@minervasys.tech>
On 02.05.2024 18:55, Carlo Nonato wrote:
> @@ -266,6 +267,47 @@ int domain_set_llc_colors(struct domain *d,
> return 0;
> }
>
> +int __init domain_set_llc_colors_from_str(struct domain *d, const char *str)
> +{
> + int err;
> + unsigned int *colors, num_colors;
> +
> + if ( !str )
> + {
> + domain_set_default_colors(d);
> + return 0;
> + }
> +
> + colors = xmalloc_array(unsigned int, max_nr_colors);
> + if ( !colors )
> + return -ENOMEM;
> +
> + err = parse_color_config(str, colors, max_nr_colors, &num_colors);
> + if ( err )
> + {
> + printk(XENLOG_ERR "Error parsing LLC color configuration");
> + xfree(colors);
> + return err;
> + }
> +
> + if ( !check_colors(colors, num_colors) )
> + {
> + printk(XENLOG_ERR "Bad LLC color config for %pd\n", d);
> + xfree(colors);
> + return -EINVAL;
> + }
> +
> + /* Adjust the size cause it was initially set to max_nr_colors */
> + colors = xrealloc_array(colors, num_colors);
> + if ( !colors )
> + return -ENOMEM;
In the error case you're leaking the (too large) array. IMO you want this to
be best effort anyway - try to shrink, but if shrinking fails use what you
already have:
d->llc_colors = xrealloc_array(colors, num_colors);
if ( !d->llc_colors )
d->llc_colors = colors;
Jan
next prev parent reply other threads:[~2024-05-06 12:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 16:55 [PATCH v8 00/13] Arm cache coloring Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 01/13] xen/common: add cache coloring common code Carlo Nonato
2024-05-06 11:54 ` Jan Beulich
2024-05-06 15:53 ` Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 02/13] xen/arm: add initial support for LLC coloring on arm64 Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 03/13] xen/arm: permit non direct-mapped Dom0 construction Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 04/13] xen/arm: add Dom0 cache coloring support Carlo Nonato
2024-05-06 12:01 ` Jan Beulich
2024-05-06 15:53 ` Carlo Nonato
2024-05-14 7:02 ` Jan Beulich
2024-05-02 16:55 ` [PATCH v8 05/13] xen: extend domctl interface for cache coloring Carlo Nonato
2024-05-06 12:05 ` Jan Beulich
2024-05-02 16:55 ` [PATCH v8 06/13] tools: add support for cache coloring configuration Carlo Nonato
2024-07-01 12:29 ` Anthony PERARD
2024-05-02 16:55 ` [PATCH v8 07/13] xen/arm: add support for cache coloring configuration via device-tree Carlo Nonato
2024-05-06 12:11 ` Jan Beulich [this message]
2024-05-02 16:55 ` [PATCH v8 08/13] xen/page_alloc: introduce preserved page flags macro Carlo Nonato
2024-05-06 12:22 ` Jan Beulich
2024-05-06 15:54 ` Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 09/13] xen: add cache coloring allocator for domains Carlo Nonato
2024-05-06 12:46 ` Jan Beulich
2024-05-02 16:55 ` [PATCH v8 10/13] xen/arm: use domain memory to allocate p2m page tables Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 11/13] xen/arm: add Xen cache colors command line parameter Carlo Nonato
2024-05-06 13:24 ` Jan Beulich
2024-05-02 16:55 ` [PATCH v8 12/13] xen/arm: make consider_modules() available for xen relocation Carlo Nonato
2024-05-02 16:55 ` [PATCH v8 13/13] xen/arm: add cache coloring support for Xen Carlo Nonato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99f6db77-23b8-4a18-b0b1-be4b9cd7f522@suse.com \
--to=jbeulich@suse.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrea.bastoni@minervasys.tech \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=carlo.nonato@minervasys.tech \
--cc=george.dunlap@citrix.com \
--cc=julien@xen.org \
--cc=marco.solieri@minervasys.tech \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.