All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nadav Amit <namit@vmware.com>
Cc: Jason Wang <jasowang@redhat.com>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] mm/balloon_compaction: suppress allocation warnings
Date: Wed, 4 Sep 2019 06:37:15 -0400	[thread overview]
Message-ID: <20190904063703-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <D4105FF4-5DF3-4DB5-9325-855B63CD9AAD@vmware.com>

On Wed, Aug 21, 2019 at 07:44:33PM +0000, Nadav Amit wrote:
> > On Aug 21, 2019, at 12:13 PM, David Hildenbrand <david@redhat.com> wrote:
> > 
> > On 21.08.19 18:34, Nadav Amit wrote:
> >>> On Aug 21, 2019, at 9:29 AM, David Hildenbrand <david@redhat.com> wrote:
> >>> 
> >>> On 21.08.19 18:23, Nadav Amit wrote:
> >>>>> On Aug 21, 2019, at 9:05 AM, David Hildenbrand <david@redhat.com> wrote:
> >>>>> 
> >>>>> On 20.08.19 11:16, Nadav Amit wrote:
> >>>>>> There is no reason to print warnings when balloon page allocation fails,
> >>>>>> as they are expected and can be handled gracefully.  Since VMware
> >>>>>> balloon now uses balloon-compaction infrastructure, and suppressed these
> >>>>>> warnings before, it is also beneficial to suppress these warnings to
> >>>>>> keep the same behavior that the balloon had before.
> >>>>> 
> >>>>> I am not sure if that's a good idea. The allocation warnings are usually
> >>>>> the only trace of "the user/admin did something bad because he/she tried
> >>>>> to inflate the balloon to an unsafe value". Believe me, I processed a
> >>>>> couple of such bugreports related to virtio-balloon and the warning were
> >>>>> very helpful for that.
> >>>> 
> >>>> Ok, so a message is needed, but does it have to be a generic frightening
> >>>> warning?
> >>>> 
> >>>> How about using __GFP_NOWARN, and if allocation do something like:
> >>>> 
> >>>> pr_warn(“Balloon memory allocation failed”);
> >>>> 
> >>>> Or even something more informative? This would surely be less intimidating
> >>>> for common users.
> >>> 
> >>> ratelimit would make sense :)
> >>> 
> >>> And yes, this would certainly be nicer.
> >> 
> >> Thanks. I will post v2 of the patch.
> > 
> > As discussed in v2, we already print a warning in virtio-balloon, so I
> > am fine with this patch.
> > 
> > Reviewed-by: David Hildenbrand <david@redhat.com>
> 
> Michael,
> 
> If it is possible to get it to 5.3, to avoid behavioral change for VMware
> balloon users, it would be great.
> 
> Thanks,
> Nadav

Just back from vacation, I'll try.



  reply	other threads:[~2019-09-04 10:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20  9:16 [PATCH] mm/balloon_compaction: suppress allocation warnings Nadav Amit
2019-08-21 16:05 ` David Hildenbrand
2019-08-21 16:05 ` David Hildenbrand
2019-08-21 16:23   ` Nadav Amit via Virtualization
2019-08-21 16:23     ` Nadav Amit
2019-08-21 16:29     ` David Hildenbrand
2019-08-21 16:29     ` David Hildenbrand
2019-08-21 16:34       ` Nadav Amit
2019-08-21 19:13         ` David Hildenbrand
2019-08-21 19:44           ` Nadav Amit via Virtualization
2019-08-21 19:44             ` Nadav Amit
2019-09-04 10:37             ` Michael S. Tsirkin [this message]
2019-09-04 10:37             ` Michael S. Tsirkin
2019-08-21 19:13         ` David Hildenbrand
2019-08-21 16:34       ` Nadav Amit via Virtualization
  -- strict thread matches above, loose matches on Subject: below --
2019-08-20  9:16 Nadav Amit via Virtualization

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=20190904063703-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=david@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=namit@vmware.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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.