From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Alok Tiwari <alok.a.tiwari@oracle.com>,
pbonzini@redhat.com, corbet@lwn.net, kvm@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] Documentation: KVM: fix reference for kvm_ppc_resize_hpt and various typos
Date: Tue, 24 Jun 2025 06:24:49 +0700 [thread overview]
Message-ID: <aFniQYHCyi4BKVcs@archie.me> (raw)
In-Reply-To: <20250623191152.44118-1-alok.a.tiwari@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-23 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 19:11 [PATCH next] Documentation: KVM: fix reference for kvm_ppc_resize_hpt and various typos Alok Tiwari
2025-06-23 23:24 ` Bagas Sanjaya [this message]
2025-06-24 12:42 ` Jonathan Corbet
2025-06-24 13:45 ` Bagas Sanjaya
2025-06-25 14:00 ` ALOK TIWARI
2025-06-25 14:15 ` Bagas Sanjaya
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=aFniQYHCyi4BKVcs@archie.me \
--to=bagasdotme@gmail.com \
--cc=alok.a.tiwari@oracle.com \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).