All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Daniel Kiper <daniel.kiper@oracle.com>,
	Ian Campbell <ian.campbell@citrix.com>
Cc: marco.guazzone@gmail.com, xen-users@lists.xen.org,
	xen-devel@lists.xensource.com, david.vrabel@citrix.com
Subject: Re: [Xen-users] Purpose of mem-max command
Date: Wed, 14 Oct 2015 10:25:16 +0100	[thread overview]
Message-ID: <561E1F7C.4060701@citrix.com> (raw)
In-Reply-To: <20151013211407.GM6226@olila.local.net-space.pl>

On 13/10/15 22:14, Daniel Kiper wrote:
> On Tue, Oct 13, 2015 at 11:55:09AM +0100, Ian Campbell wrote:
>> [CCing Daniel]
>>
>> Daniel, please could you advice on which Xen releases, guest types and
>> guest kernel versions are currently expected to work with memory hotplug.
> 
> Well... It worked, regardless of guest type, when it was introduced first time.
> At that time xend was Xen toolstack. Than xl appeared on the scene and it stopped
> working. I tried to fix it but I was diverted to something more important. Last
> time David (CC-ed here) fixed some memory hotplug issues in Linux kernel (please
> check for-linus-4.4 branch in git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for more details). I suppose that he manged to overcome some xl deficiencies and
> he will be able to shed some light what he did. If not or his work is not upstreamable
> then I leave this on my TODO list. I hope that I will be able to work on this next
> year. However, if somebody is up to this work I am able to mentor he/she or at
> least review relevant patch series. Here are my old patches for xl:
> http://lists.xen.org/archives/html/xen-devel/2013-04/msg03072.html This is really
> old but I think it could be good starting point for further work.

I think I had to manually fiddle with xenstore keys to persuade xl to
allow mem-max to work as expected.

David

  reply	other threads:[~2015-10-14  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AD4EF69E-4D6D-4C38-905E-88F35594632D@thehobsons.co.uk>
     [not found] ` <CABbE_O4V9CyhtgZtYZTaFEN3y_Ge=UZ2AQnZapoRn38cjhMsAw@mail.gmail.com>
     [not found]   ` <7C676D27-F31C-4B5C-AF97-3840FD33AAC6@thehobsons.co.uk>
     [not found]     ` <1444640487.1410.450.camel@citrix.com>
     [not found]       ` <CABbE_O7+qJZj06nD96Pdt2nVbU82x+T0gRC98w_q_hQDipA7Zg@mail.gmail.com>
     [not found]         ` <1444644147.1410.472.camel@citrix.com>
     [not found]           ` <CABbE_O6HaHKifgH09LydCaZwwZEAn15WfXayGVjLeJJN8Lia-A@mail.gmail.com>
     [not found]             ` <528267AF-80A5-4165-AD6E-51A3CAFC03F1@thehobsons.co.uk>
     [not found]               ` <CABbE_O4DbcAgx4v3cGuyqx+2vA=TzhMfHgCn5aZOVgpstdaysA@mail.gmail.com>
     [not found]                 ` <1444733709.23192.41.camel@citrix.com>
2015-10-13 21:14                   ` [Xen-users] Purpose of mem-max command Daniel Kiper
2015-10-14  9:25                     ` David Vrabel [this message]
2015-10-14 13:19                       ` [Xen-devel] " Marco Guazzone

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=561E1F7C.4060701@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=marco.guazzone@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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 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.