On Thu, Jan 26, 2023 at 10:39:48PM -0800, Randy Dunlap wrote: > diff -- a/Documentation/mm/hmm.rst b/Documentation/mm/hmm.rst > --- a/Documentation/mm/hmm.rst > +++ b/Documentation/mm/hmm.rst > @@ -416,10 +416,10 @@ can be used to make a memory range inacc > > This replaces all mappings for pages in the given range with special swap > entries. Any attempt to access the swap entry results in a fault which is > -resovled by replacing the entry with the original mapping. A driver gets > +resolved by replacing the entry with the original mapping. A driver gets > notified that the mapping has been changed by MMU notifiers, after which point > it will no longer have exclusive access to the page. Exclusive access is > -guranteed to last until the driver drops the page lock and page reference, at > +guaranteed to last until the driver drops the page lock and page reference, at > which point any CPU faults on the page may proceed as described. > > Memory cgroup (memcg) and rss accounting > diff -- a/Documentation/mm/hwpoison.rst b/Documentation/mm/hwpoison.rst > --- a/Documentation/mm/hwpoison.rst > +++ b/Documentation/mm/hwpoison.rst > @@ -50,7 +50,7 @@ of applications. KVM support requires a > For the KVM use there was need for a new signal type so that > KVM can inject the machine check into the guest with the proper > address. This in theory allows other applications to handle > -memory failures too. The expection is that near all applications > +memory failures too. The expectation is that near all applications > won't do that, but some very specialized ones might. > > Failure recovery modes LGTM, thanks! Reviewed-by: Bagas Sanjaya <bagasdotme@xxxxxxxxx> -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
