On Tue, Aug 21, 2018 at 10:58:18AM +0100, Wei Liu wrote:
> On Mon, Aug 13, 2018 at 03:06:10PM +0200, Juergen Gross wrote:
> > Today's interface of Xen for memory ballooning is quite a mess. There
> > are some shortcomings which should be addressed somehow. After a
> > discussion on IRC there was co
On Mon, Aug 13, 2018 at 03:06:10PM +0200, Juergen Gross wrote:
> Today's interface of Xen for memory ballooning is quite a mess. There
> are some shortcomings which should be addressed somehow. After a
> discussion on IRC there was consensus we should try to design a new
> interface addressing the
On 14/08/18 09:34, Jan Beulich wrote:
On 14.08.18 at 09:19, wrote:
>> On 14/08/18 09:02, Jan Beulich wrote:
>> On 13.08.18 at 17:44, wrote:
On 13/08/18 17:29, Jan Beulich wrote:
On 13.08.18 at 16:20, wrote:
>> On 13/08/18 15:54, Jan Beulich wrote:
>> On 13.08.1
>>> On 14.08.18 at 09:19, wrote:
> On 14/08/18 09:02, Jan Beulich wrote:
> On 13.08.18 at 17:44, wrote:
>>> On 13/08/18 17:29, Jan Beulich wrote:
>>> On 13.08.18 at 16:20, wrote:
> On 13/08/18 15:54, Jan Beulich wrote:
> On 13.08.18 at 15:06, wrote:
>>> Suggested new int
On 14/08/18 09:02, Jan Beulich wrote:
On 13.08.18 at 17:44, wrote:
>> On 13/08/18 17:29, Jan Beulich wrote:
>> On 13.08.18 at 16:20, wrote:
On 13/08/18 15:54, Jan Beulich wrote:
On 13.08.18 at 15:06, wrote:
>> Suggested new interface
>> ---
>>> On 13.08.18 at 17:44, wrote:
> On 13/08/18 17:29, Jan Beulich wrote:
> On 13.08.18 at 16:20, wrote:
>>> On 13/08/18 15:54, Jan Beulich wrote:
>>> On 13.08.18 at 15:06, wrote:
> Suggested new interface
> ---
> Hypercalls, memory map(s) and ACPI tables s
On 13/08/18 17:29, Jan Beulich wrote:
On 13.08.18 at 16:20, wrote:
>> On 13/08/18 15:54, Jan Beulich wrote:
>> On 13.08.18 at 15:06, wrote:
Suggested new interface
---
Hypercalls, memory map(s) and ACPI tables should stay the same (for
compatibilit
>>> On 13.08.18 at 16:20, wrote:
> On 13/08/18 15:54, Jan Beulich wrote:
> On 13.08.18 at 15:06, wrote:
>>> Suggested new interface
>>> ---
>>> Hypercalls, memory map(s) and ACPI tables should stay the same (for
>>> compatibility reasons or because they are architectural i
On Mon, Aug 13, 2018 at 04:27:06PM +0200, Juergen Gross wrote:
> On 13/08/18 16:12, Roger Pau Monné wrote:
> > On Mon, Aug 13, 2018 at 03:06:10PM +0200, Juergen Gross wrote:
> > Currently as you say there's a difference between the xenstore target
> > and the guest memory map, because some memory i
On 13/08/18 16:12, Roger Pau Monné wrote:
> On Mon, Aug 13, 2018 at 03:06:10PM +0200, Juergen Gross wrote:
>> Today's interface of Xen for memory ballooning is quite a mess. There
>> are some shortcomings which should be addressed somehow. After a
>> discussion on IRC there was consensus we should
On 13/08/18 15:54, Jan Beulich wrote:
On 13.08.18 at 15:06, wrote:
>> Suggested new interface
>> ---
>> Hypercalls, memory map(s) and ACPI tables should stay the same (for
>> compatibility reasons or because they are architectural interfaces).
>>
>> As the main confusion i
On Mon, Aug 13, 2018 at 03:06:10PM +0200, Juergen Gross wrote:
> Today's interface of Xen for memory ballooning is quite a mess. There
> are some shortcomings which should be addressed somehow. After a
> discussion on IRC there was consensus we should try to design a new
> interface addressing the
>>> On 13.08.18 at 15:06, wrote:
> Suggested new interface
> ---
> Hypercalls, memory map(s) and ACPI tables should stay the same (for
> compatibility reasons or because they are architectural interfaces).
>
> As the main confusion in the current interface is related to the
>
Today's interface of Xen for memory ballooning is quite a mess. There
are some shortcomings which should be addressed somehow. After a
discussion on IRC there was consensus we should try to design a new
interface addressing the current and probably future needs.
Current interface
-
14 matches
Mail list logo
