[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4ff2987-df22-4338-8a78-5efa2c7c23d6@web.de>
Date: Tue, 7 May 2024 15:45:19 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Song Gao <gaosong@...ngson.cn>, loongarch@...ts.linux.dev,
kernel-janitors@...r.kernel.org, maobibo@...ngson.cn
Cc: LKML <linux-kernel@...r.kernel.org>, Huacai Chen <chenhuacai@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>, Tianrui Zhao <zhaotianrui@...ngson.cn>,
Wang Xuerui <kernel@...0n.name>
Subject: Re: [PATCH v5] LoongArch: KVM: Add PMU support
…
> - we save the host PMU CSRs into structure kvm_context.
> - If the host supports the PMU feature.
> - When entering guest mode. we save the host PMU CSRs and restore the guest PMU CSRs.
> - When exiting guest mode, we save the guest PMU CSRs and restore the host PMU CSRs.
How do you think about to use imperative wordings for improved change descriptions?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9-rc7#n94
Would you like to take another look at the usage of dots and commas
in such a changelog?
Regards,
Markus
Powered by blists - more mailing lists