From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: Hendrik Wuethrich <whendrik@google.com>
Cc: <qemu-devel@nongnu.org>, <eduardo@habkost.net>,
<richard.henderson@linaro.org>, <marcel.apfelbaum@gmail.com>,
<mst@redhat.com>, <pbonzini@redhat.com>, <peternewman@google.com>
Subject: Re: [PATCH v1 3/9] Add init and realize funciontality for RDT device.
Date: Fri, 26 Jul 2024 11:41:43 +0100 [thread overview]
Message-ID: <20240726114143.0000154e@Huawei.com> (raw)
In-Reply-To: <20240719162929.1197154-4-whendrik@google.com>
On Fri, 19 Jul 2024 16:29:23 +0000
Hendrik Wuethrich <whendrik@google.com> wrote:
> From: Hendrik Wüthrich <whendrik@google.com>
>
> Add code to initialize all necessary state for the RDT device.
>
> Signed-off-by: Hendrik Wüthrich <whendrik@google.com>
> ---
> hw/i386/rdt.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/hw/i386/rdt.c b/hw/i386/rdt.c
> index cf246ab835..259dafc963 100644
> --- a/hw/i386/rdt.c
> +++ b/hw/i386/rdt.c
> @@ -62,10 +62,38 @@ static void rdt_init(Object *obj)
>
> static void rdt_realize(DeviceState *dev, Error **errp)
> {
> + CPUState *cs = first_cpu;
> +
No blank line here.
> + RDTState *rdtDev = RDT(dev);
blank line here.
> + rdtDev->rdtInstances = g_array_new(false, true, sizeof(RDTStateInstance));
> + g_array_set_size(rdtDev->rdtInstances, cs->nr_cores);
> + CPU_FOREACH(cs) {
> + RDTStateInstance *rdt = &g_array_index(rdtDev->rdtInstances, RDTStateInstance, cs->cpu_index);
> +
No blank line here. Also wrap this long line somewhere.
> + X86CPU *cpu = X86_CPU(cs);
blank line here.
> + rdt->rdtstate = rdtDev;
> + cpu->rdt = rdt;
> +
> + rdt->monitors = g_array_new(false, true, sizeof(RDTMonitor));
> + rdt->rdtstate->allocations = g_array_new(false, true, sizeof(RDTAllocation));
> +
> + g_array_set_size(rdt->monitors, rdtDev->rmids);
> + g_array_set_size(rdt->rdtstate->allocations, rdtDev->rmids);
Are these g_array's going to change size? If not, why go through this dance when
a simple pointer will do?
> + }
> }
>
> static void rdt_finalize(Object *obj)
> {
> + CPUState *cs;
> + RDTState *rdt = RDT(obj);
> +
> + CPU_FOREACH(cs) {
> + RDTStateInstance *rdtInstance = &g_array_index(rdt->rdtInstances, RDTStateInstance, cs->cpu_index);
Long line. Wrap that. Worth running checkpatch which I think
will moan about things like this.
> + g_array_free(rdtInstance->monitors, true);
> + g_array_free(rdtInstance->rdtstate->allocations, true);
> + }
> +
> + g_array_free(rdt->rdtInstances, true);
> }
>
> static void rdt_class_init(ObjectClass *klass, void *data)
next prev parent reply other threads:[~2024-07-26 10:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 16:29 [PATCH v1 0/9] target:386/ Emulate Intel RDT features needed to mount ResCtrl in Linux Hendrik Wuethrich
2024-07-19 16:29 ` [PATCH v1 1/9] Add Intel RDT device to config Hendrik Wuethrich
2024-07-26 10:24 ` Jonathan Cameron via
2024-09-04 14:14 ` Hendrik Wüthrich
2024-07-19 16:29 ` [PATCH v1 2/9] Add state for RDT device Hendrik Wuethrich
2024-07-26 10:33 ` Jonathan Cameron via
2024-07-19 16:29 ` [PATCH v1 3/9] Add init and realize funciontality " Hendrik Wuethrich
2024-07-26 10:41 ` Jonathan Cameron via [this message]
2024-07-26 10:42 ` Jonathan Cameron via
2024-07-19 16:29 ` [PATCH v1 4/9] Add RDT functionality Hendrik Wuethrich
2024-07-26 10:51 ` Jonathan Cameron via
2024-07-19 16:29 ` [PATCH v1 5/9] Add RDT device interface through MSRs Hendrik Wuethrich
2024-07-26 10:57 ` Jonathan Cameron via
2024-07-19 16:29 ` [PATCH v1 6/9] Add CPUID enumeration for RDT Hendrik Wuethrich
2024-07-26 12:09 ` Jonathan Cameron via
2024-07-19 16:29 ` [PATCH v1 7/9] Add RDT feature flags Hendrik Wuethrich
2024-07-19 16:29 ` [PATCH v1 8/9] Adjust CPUID level for RDT features Hendrik Wuethrich
2024-07-19 16:29 ` [PATCH v1 9/9] Adjust level for RDT on full_cpuid_auto_level Hendrik Wuethrich
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=20240726114143.0000154e@Huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peternewman@google.com \
--cc=richard.henderson@linaro.org \
--cc=whendrik@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).