On Thu, 22 Feb 2018 14:29:09 -0500
Matthew Rosato wrote:
> On 02/22/2018 06:13 AM, Christian Borntraeger wrote:
> >
> >
> > On 02/21/2018 06:39 PM, Cornelia Huck wrote:
> >> On Tue, 20 Feb 2018 16:05:54 +0100
> >> David Hildenbrand wrote:
> >>
> >>> On 20.02.2018 15:57, Cornelia Huck wrote
On 02/22/2018 06:13 AM, Christian Borntraeger wrote:
>
>
> On 02/21/2018 06:39 PM, Cornelia Huck wrote:
>> On Tue, 20 Feb 2018 16:05:54 +0100
>> David Hildenbrand wrote:
>>
>>> On 20.02.2018 15:57, Cornelia Huck wrote:
On Tue, 20 Feb 2018 13:16:37 +0100
David Hildenbrand wrote:
On 02/21/2018 06:39 PM, Cornelia Huck wrote:
> On Tue, 20 Feb 2018 16:05:54 +0100
> David Hildenbrand wrote:
>
>> On 20.02.2018 15:57, Cornelia Huck wrote:
>>> On Tue, 20 Feb 2018 13:16:37 +0100
>>> David Hildenbrand wrote:
>>>
On 20.02.2018 13:05, Christian Borntraeger wrote:
>
On Tue, 20 Feb 2018 16:05:54 +0100
David Hildenbrand wrote:
> On 20.02.2018 15:57, Cornelia Huck wrote:
> > On Tue, 20 Feb 2018 13:16:37 +0100
> > David Hildenbrand wrote:
> >
> >> On 20.02.2018 13:05, Christian Borntraeger wrote:
> >>>
> >>>
> >>> On 02/19/2018 06:42 PM, David Hildenbrand
On 20.02.2018 15:57, Cornelia Huck wrote:
> On Tue, 20 Feb 2018 13:16:37 +0100
> David Hildenbrand wrote:
>
>> On 20.02.2018 13:05, Christian Borntraeger wrote:
>>>
>>>
>>> On 02/19/2018 06:42 PM, David Hildenbrand wrote:
From an architecture point of view, nothing can be mapped into the a
On Tue, 20 Feb 2018 13:16:37 +0100
David Hildenbrand wrote:
> On 20.02.2018 13:05, Christian Borntraeger wrote:
> >
> >
> > On 02/19/2018 06:42 PM, David Hildenbrand wrote:
> >> From an architecture point of view, nothing can be mapped into the address
> >> space on s390x. All there is is mem
On 20.02.2018 13:05, Christian Borntraeger wrote:
>
>
> On 02/19/2018 06:42 PM, David Hildenbrand wrote:
>> From an architecture point of view, nothing can be mapped into the address
>> space on s390x. All there is is memory. Therefore there is also not really
>> an interface to communicate such
On 02/19/2018 06:42 PM, David Hildenbrand wrote:
> From an architecture point of view, nothing can be mapped into the address
> space on s390x. All there is is memory. Therefore there is also not really
> an interface to communicate such information to the guest. All we can do is
> specify the ma
On 20.02.2018 12:18, Christian Borntraeger wrote:
> Given that we have trouble modeling this properly I somewhat like the idea.
> We should have never folded this into the common code memory hotplug
> infrastructure as it is different. Instead we really should have provided
> a different interface
On 02/20/2018 12:18 PM, Christian Borntraeger wrote:
> Given that we have trouble modeling this properly I somewhat like the idea.
> We should have never folded this into the common code memory hotplug
> infrastructure as it is different. Instead we really should have provided
> a different inte
Given that we have trouble modeling this properly I somewhat like the idea.
We should have never folded this into the common code memory hotplug
infrastructure as it is different. Instead we really should have provided
a different interface and we should have build it with migration support.
If
>From an architecture point of view, nothing can be mapped into the address
space on s390x. All there is is memory. Therefore there is also not really
an interface to communicate such information to the guest. All we can do is
specify the maximum ram address and guests can probe in that range if
me
12 matches
Mail list logo