From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yuanchu Xie <yuanchu@google.com>
Cc: Wei Liu <liuwe@microsoft.com>,
Rob Bradford <rbradford@rivosinc.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux.dev, dev@lists.cloudhypervisor.org
Subject: Re: [PATCH v5 1/2] virt: pvmemcontrol: control guest physical memory properties
Date: Fri, 20 Dec 2024 08:21:25 +0100 [thread overview]
Message-ID: <2024122052-unsworn-haziness-ae7f@gregkh> (raw)
In-Reply-To: <CAJj2-QFSmtCcQ=dm3yMhNi9F6trbcP0rg5z8cns5V64Pmn0c9Q@mail.gmail.com>
On Thu, Dec 19, 2024 at 10:58:24AM -0800, Yuanchu Xie wrote:
> On Mon, Dec 2, 2024 at 4:24 PM Yuanchu Xie <yuanchu@google.com> wrote:
> >
> > Pvmemcontrol provides a way for the guest to control its physical memory
> > properties and enables optimizations and security features. For example,
> > the guest can provide information to the host where parts of a hugepage
> > may be unbacked, or sensitive data may not be swapped out, etc.
> Hello Greg,
>
> I addressed the feedback from you earlier at [1]. Let me know how the v5 goes.
>
> Thanks,
> Yuanchu
>
> [1] https://lore.kernel.org/linux-mm/2024102220-creed-darkening-aac0@gregkh/
Right now my review queue looks like this:
$ mdfrm -c ~/mail/todo/
2474 messages in /home/gregkh/mail/todo/
I recommend taking the time to review other patches from other people to
help reduce the maintainer review load.
thanks!
greg k-h
next prev parent reply other threads:[~2024-12-20 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 0:23 Yuanchu Xie
2024-12-03 0:23 ` [PATCH v5 2/2] virt: pvmemcontrol: add Yuanchu and Pasha as maintainers Yuanchu Xie
2024-12-19 18:58 ` [PATCH v5 1/2] virt: pvmemcontrol: control guest physical memory properties Yuanchu Xie
2024-12-20 7:21 ` Greg Kroah-Hartman [this message]
2025-01-04 9:13 ` Greg Kroah-Hartman
2025-01-04 9:15 ` Greg Kroah-Hartman
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=2024122052-unsworn-haziness-ae7f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dev@lists.cloudhypervisor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuwe@microsoft.com \
--cc=pasha.tatashin@soleen.com \
--cc=rbradford@rivosinc.com \
--cc=virtualization@lists.linux.dev \
--cc=yuanchu@google.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