All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xenproject.org
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Subject: Re: [PATCHv1] xen/balloon: disable memory hotplug in PV guests
Date: Mon, 09 Mar 2015 11:50:32 -0400	[thread overview]
Message-ID: <54FDC148.7040603@oracle.com> (raw)
In-Reply-To: <54FDBCD2.8040807@citrix.com>

On 03/09/2015 11:31 AM, David Vrabel wrote:
> On 09/03/15 15:25, Boris Ostrovsky wrote:
>> On 03/09/2015 11:13 AM, David Vrabel wrote:
>>> On 09/03/15 15:09, Boris Ostrovsky wrote:
>>>> On 03/09/2015 10:10 AM, David Vrabel wrote:
>>>>> Memory hotplug doesn't work with PV guests because:
>>>>>
>>>>>      a) The p2m cannot be expanded to cover the new sections.
>>>>>
>>>>>      b) add_memory() builds page tables for the new sections which means
>>>>>         the new pages must have valid p2m entries (or a BUG occurs).
>>>> Is this due to recent p2m rework?
>>> (a) is but (b) has always meant memory hotplug on PV was broken.
>> I can see why (b) should probably have prevented it from working but I
>> tried this on 4.4/3.17 and that seemed to work (it indeed does not
>> function well on newer bits).
> I tried it on 3.10 (+ some other bits and pieces) and it was definitely
> broken for reason (b).  I had to refactor the balloon driver to populate
> the sections before calling add_memory() before it would work.  But this
> can't be done now because of (a).

Could something have happened between 3.10 and 3.17 that fixed it (hard 
to believe but nevertheless)? Or this brokenness depends on Xen version 
(again, unlikely)?

In any case, I think this needs a message in the log stating that 
hotplug doesn't work for this guest (once, so that we don't into 
spamming the log like we have recently).

-boris

  parent reply	other threads:[~2015-03-09 15:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 14:10 [PATCHv1] xen/balloon: disable memory hotplug in PV guests David Vrabel
2015-03-09 15:09 ` Boris Ostrovsky
2015-03-09 15:13   ` David Vrabel
2015-03-09 15:25     ` Boris Ostrovsky
2015-03-09 15:31       ` David Vrabel
2015-03-09 15:40         ` Konrad Rzeszutek Wilk
2015-03-09 15:50         ` Boris Ostrovsky [this message]
2015-03-09 20:45         ` Daniel Kiper
2015-03-09 20:22       ` Daniel Kiper
2015-03-10 11:40 ` David Vrabel
2015-03-10 13:35   ` Boris Ostrovsky
2015-03-11 14:42     ` David Vrabel
2015-03-11 15:40       ` Boris Ostrovsky
2015-03-16  5:35         ` Juergen Gross
2015-03-16 10:03           ` Daniel Kiper
2015-03-16 10:31             ` Juergen Gross
2015-03-17 12:40               ` Daniel Kiper
2015-03-17 13:00                 ` Juergen Gross
2015-03-18 10:36               ` David Vrabel
2015-03-18 13:57                 ` Juergen Gross
2015-03-18 13:59                   ` David Vrabel
2015-03-18 15:14                     ` Daniel Kiper
2015-03-19  9:55                       ` Juergen Gross
2015-03-19 11:34                         ` Daniel Kiper
2015-03-19 13:38                           ` Juergen Gross
2015-03-19 14:21                             ` Juergen Gross

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=54FDC148.7040603@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=daniel.kiper@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=xen-devel@lists.xenproject.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.