Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	kvmarm@lists.linux.dev, Akihiko Odaki <akihiko.odaki@daynix.com>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH] KVM: arm64: Mark some VM-scoped allocations as __GFP_ACCOUNT
Date: Tue, 07 Feb 2023 09:31:16 +0000	[thread overview]
Message-ID: <86ttzxzusb.wl-maz@kernel.org> (raw)
In-Reply-To: <20230206235229.4174711-1-oliver.upton@linux.dev>

On Mon, 06 Feb 2023 23:52:29 +0000,
Oliver Upton <oliver.upton@linux.dev> wrote:
> 
> Generally speaking, any memory allocations that can be associated with a
> particular VM should be charged to the cgroup of its process.
> Nonetheless, there are a couple spots in KVM/arm64 that aren't currently
> accounted:
> 
>  - the ccsidr array containing the virtualized cache hierarchy
> 
>  - the cpumask of supported cpus, for use of the vPMU on heterogeneous
>    systems
> 
> Go ahead and set __GFP_ACCOUNT for these allocations.
> 
> Signed-off-by: Oliver Upton <oliver.upton@linux.dev>

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2023-02-07  9:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 23:52 [PATCH] KVM: arm64: Mark some VM-scoped allocations as __GFP_ACCOUNT Oliver Upton
2023-02-07  0:18 ` Akihiko Odaki
2023-02-07  5:02 ` Gavin Shan
2023-02-07  9:31 ` Marc Zyngier [this message]
2023-02-08 17:30 ` Oliver Upton

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=86ttzxzusb.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=akihiko.odaki@daynix.com \
    --cc=james.morse@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@huawei.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