[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aFniQYHCyi4BKVcs@archie.me>
Date: Tue, 24 Jun 2025 06:24:49 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Alok Tiwari <alok.a.tiwari@...cle.com>, pbonzini@...hat.com,
corbet@....net, kvm@...r.kernel.org, linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH next] Documentation: KVM: fix reference for
kvm_ppc_resize_hpt and various typos
On Mon, Jun 23, 2025 at 12:11:47PM -0700, Alok Tiwari wrote:
> If this ioctl is called when a hash table has already been allocated,
> with a different order from the existing hash table, the existing hash
> -table will be freed and a new one allocated. If this is ioctl is
> -called when a hash table has already been allocated of the same order
> +table will be freed and a new one allocated. If this ioctl is called
> +when a hash table has already been allocated of the same order
Two spaces between sentences (just to be consistent), please.
> -This capability indicates that KVM supports that accesses to user defined MSRs
> +This capability indicates that KVM supports accesses to user defined MSRs
> may be rejected. With this capability exposed, KVM exports new VM ioctl
> KVM_X86_SET_MSR_FILTER which user space can call to specify bitmaps of MSR
> ranges that KVM should deny access to.
Do you mean accesses to user defined MSRs *that* may be rejected?
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists