All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <dslutz@verizon.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
	Don Slutz <dslutz@verizon.com>
Subject: Re: [Qemu-devel] [PATCH for 2.3 v2 1/1] xen-hvm: increase maxmem before calling xc_domain_populate_physmap
Date: Tue, 13 Jan 2015 15:11:55 -0500	[thread overview]
Message-ID: <54B57C0B.9020105@terremark.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501131806310.28492@kaball.uk.xensource.com>

On 01/13/15 13:07, Stefano Stabellini wrote:
> On Mon, 12 Jan 2015, Stefano Stabellini wrote:
>> On Wed, 3 Dec 2014, Don Slutz wrote:
>>> From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>>
>>> Increase maxmem before calling xc_domain_populate_physmap_exact to
>>> avoid the risk of running out of guest memory. This way we can also
>>> avoid complex memory calculations in libxl at domain construction
>>> time.
>>>
>>> This patch fixes an abort() when assigning more than 4 NICs to a VM.
>>>
>>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>> Signed-off-by: Don Slutz <dslutz@verizon.com>
>>> ---
>>> v2: Changes by Don Slutz
>>>   Switch from xc_domain_getinfo to xc_domain_getinfolist
>>>   Fix error check for xc_domain_getinfolist
>>>   Limit increase of maxmem to only do when needed:
>>>     Add QEMU_SPARE_PAGES (How many pages to leave free)
>>>     Add free_pages calculation
>>>
>>>  xen-hvm.c | 19 +++++++++++++++++++
>>>  1 file changed, 19 insertions(+)
>>>
>>> diff --git a/xen-hvm.c b/xen-hvm.c
>>> index 7548794..d30e77e 100644
>>> --- a/xen-hvm.c
>>> +++ b/xen-hvm.c
>>> @@ -90,6 +90,7 @@ static inline ioreq_t *xen_vcpu_ioreq(shared_iopage_t *shared_page, int vcpu)
>>>  #endif
>>>  
>>>  #define BUFFER_IO_MAX_DELAY  100
>>> +#define QEMU_SPARE_PAGES 16
>>
>> We need a big comment here to explain why we have this parameter and
>> when we'll be able to get rid of it.
>>
>> Other than that the patch is fine.
>>
>> Thanks!
>>
> 
> Actually I'll just go ahead and add the comment and commit, if for you
> is OK.
> 

That would be fine with me.  I was still working on a good wording.
   -Don Slutz

> Cheers,
> 
> Stefano
> 

WARNING: multiple messages have this Message-ID (diff)
From: Don Slutz <dslutz@verizon.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org,
	Don Slutz <dslutz@verizon.com>
Subject: Re: [PATCH for 2.3 v2 1/1] xen-hvm: increase maxmem before calling xc_domain_populate_physmap
Date: Tue, 13 Jan 2015 15:11:55 -0500	[thread overview]
Message-ID: <54B57C0B.9020105@terremark.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501131806310.28492@kaball.uk.xensource.com>

On 01/13/15 13:07, Stefano Stabellini wrote:
> On Mon, 12 Jan 2015, Stefano Stabellini wrote:
>> On Wed, 3 Dec 2014, Don Slutz wrote:
>>> From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>>
>>> Increase maxmem before calling xc_domain_populate_physmap_exact to
>>> avoid the risk of running out of guest memory. This way we can also
>>> avoid complex memory calculations in libxl at domain construction
>>> time.
>>>
>>> This patch fixes an abort() when assigning more than 4 NICs to a VM.
>>>
>>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>>> Signed-off-by: Don Slutz <dslutz@verizon.com>
>>> ---
>>> v2: Changes by Don Slutz
>>>   Switch from xc_domain_getinfo to xc_domain_getinfolist
>>>   Fix error check for xc_domain_getinfolist
>>>   Limit increase of maxmem to only do when needed:
>>>     Add QEMU_SPARE_PAGES (How many pages to leave free)
>>>     Add free_pages calculation
>>>
>>>  xen-hvm.c | 19 +++++++++++++++++++
>>>  1 file changed, 19 insertions(+)
>>>
>>> diff --git a/xen-hvm.c b/xen-hvm.c
>>> index 7548794..d30e77e 100644
>>> --- a/xen-hvm.c
>>> +++ b/xen-hvm.c
>>> @@ -90,6 +90,7 @@ static inline ioreq_t *xen_vcpu_ioreq(shared_iopage_t *shared_page, int vcpu)
>>>  #endif
>>>  
>>>  #define BUFFER_IO_MAX_DELAY  100
>>> +#define QEMU_SPARE_PAGES 16
>>
>> We need a big comment here to explain why we have this parameter and
>> when we'll be able to get rid of it.
>>
>> Other than that the patch is fine.
>>
>> Thanks!
>>
> 
> Actually I'll just go ahead and add the comment and commit, if for you
> is OK.
> 

That would be fine with me.  I was still working on a good wording.
   -Don Slutz

> Cheers,
> 
> Stefano
> 

  reply	other threads:[~2015-01-13 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 13:15 [Qemu-devel] [PATCH for 2.3 v2 1/1] xen-hvm: increase maxmem before calling xc_domain_populate_physmap Don Slutz
2014-12-03 13:15 ` Don Slutz
2014-12-23 14:35 ` [Qemu-devel] " Don Slutz
2014-12-23 14:35   ` Don Slutz
2015-01-09 16:32   ` [Qemu-devel] " Don Slutz
2015-01-09 16:32     ` Don Slutz
2015-01-12 11:20 ` [Qemu-devel] " Stefano Stabellini
2015-01-12 11:20   ` Stefano Stabellini
2015-01-13 18:07   ` [Qemu-devel] " Stefano Stabellini
2015-01-13 18:07     ` Stefano Stabellini
2015-01-13 20:11     ` Don Slutz [this message]
2015-01-13 20:11       ` Don Slutz
2015-01-14 11:30       ` [Qemu-devel] " Stefano Stabellini
2015-01-14 11:30         ` Stefano Stabellini

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=54B57C0B.9020105@terremark.com \
    --to=dslutz@verizon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.