All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nadav Amit <nadav.amit@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	VMware PV-Drivers Reviewers <pv-drivers@vmware.com>,
	Arnd Bergmann <arnd@arndb.de>, Nadav Amit <namit@vmware.com>
Subject: [PATCH 0/3] vmw_balloon: misc fixes and enhancements
Date: Tue, 13 Sep 2022 02:43:03 -0700	[thread overview]
Message-ID: <20220913094306.317734-1-namit@vmware.com> (raw)

From: Nadav Amit <namit@vmware.com>

Various relatively minor enhancements. Patches 1-2 address borderline
bugs. There have been no actual bug reports, and the first bug is
theoretical and the second one is a minor performance issue. We
therefore do not ask to backport them, but keep them first since we (or
distributions) might want to backport them later.

Patch 3 is doing some cleanup due to recent changes, with no expected
functional change.

Nadav Amit (3):
  vmw_balloon: access reset_required through READ/WRITE_ONCE
  vmw_balloon: exit if initalization fails
  vmw_balloon: open-code vmballoon_compaction_init()

 drivers/misc/vmw_balloon.c | 71 +++++++++++++++++---------------------
 1 file changed, 31 insertions(+), 40 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-09-13 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  9:43 Nadav Amit [this message]
2022-09-13  9:43 ` [PATCH 1/3] vmw_balloon: access reset_required through READ/WRITE_ONCE Nadav Amit
2022-09-13  9:43 ` [PATCH 2/3] vmw_balloon: exit if initalization fails Nadav Amit
2022-09-13  9:43 ` [PATCH 3/3] vmw_balloon: open-code vmballoon_compaction_init() Nadav Amit
2022-09-14 10:14   ` David Hildenbrand
2022-09-15  0:05   ` kernel test robot
2022-09-15  3:16     ` Nadav Amit
2022-09-15  3:16       ` Nadav Amit
2022-09-16  8:10   ` kernel test robot

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=20220913094306.317734-1-namit@vmware.com \
    --to=nadav.amit@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namit@vmware.com \
    --cc=pv-drivers@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.