public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: hansechang@gmail.com, linux-kernel@vger.kernel.org,
	xen-devel@lists.xen.org,
	Chang Huaixin <huaixin.chx@alibaba-inc.com>,
	jinsong.liu@alibaba-inc.com, Ian.Campbell@eu.citrix.com,
	dgdegra@tycho.nsa.gov, boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [PATCH] Input: xen-kbdfront - free grant table entry in xenkbd_disconnect_backend
Date: Thu, 16 Oct 2014 13:37:19 -0700	[thread overview]
Message-ID: <20141016203719.GB38361@dtor-ws> (raw)
In-Reply-To: <543FEBC5.2050202@citrix.com>

On Thu, Oct 16, 2014 at 05:01:09PM +0100, David Vrabel wrote:
> On 16/10/14 02:46, hansechang@gmail.com wrote:
> > From: Chang Huaixin <huaixin.chx@alibaba-inc.com>
> > 
> > xenkbd_disconnect_backend doesn't free grant table entry.
> > This bug affects live migration.
> > 
> > xenkbd_disconnect_backend uses gnttab_end_foreign_access_ref
> > to handle grant table entry which doesn't really free an entry.
> > 
> > Thus every time we do xenkbd_resume, grant table entry increses
> > by one. As an grant table entry occupies 8 bytes, an grant table
> > page has at most 512 entries. Every 512 times we do xenkdb_resume,
> > grant table pages increses by one.
> > 
> > After around 3500 times of live migration, grant table pages
> > will increase by 7, causing too many pages to populate and hitting
> > max_pages limit when assigning pages.Thus assign_pages will fail,
> > so will live migration.
> 
> Acked-by: David Vrabel <david.vrabel@citrix.com>
> 
> This need to be send to the input subsystem maintainers.

Applied, thank you.

-- 
Dmitry

      reply	other threads:[~2014-10-16 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16  1:46 [PATCH] Input: xen-kbdfront - free grant table entry in xenkbd_disconnect_backend hansechang
2014-10-16 16:01 ` [Xen-devel] " David Vrabel
2014-10-16 20:37   ` Dmitry Torokhov [this message]

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=20141016203719.GB38361@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=hansechang@gmail.com \
    --cc=huaixin.chx@alibaba-inc.com \
    --cc=jinsong.liu@alibaba-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox