> >>> The alternative would be that we just release a fork (or just
> >>> the patches) and walk away.
> >>> If the Xen community wants to make the
> >>> announcement that only code that will have long term support and is
> >>> "stable" is accepted upstream that's IMHO drastically going to reduce
On Thu, Dec 19, 2019 at 9:58 AM Julien Grall wrote:
>
> Hi,
>
> On 19/12/2019 16:11, Tamas K Lengyel wrote:
> >>> Well, this is only an experimental system that's completely disabled
> >>> by default. Making the assumption that people who make use of it will
> >>> know what they are doing I think
On 19/12/2019 17:23, Tamas K Lengyel wrote:
On Thu, Dec 19, 2019 at 9:58 AM Julien Grall wrote:
Hi,
On 19/12/2019 16:11, Tamas K Lengyel wrote:
Well, this is only an experimental system that's completely disabled
by default. Making the assumption that people who make use of it will
know
Hi,
On 19/12/2019 16:11, Tamas K Lengyel wrote:
Well, this is only an experimental system that's completely disabled
by default. Making the assumption that people who make use of it will
know what they are doing I think is fair.
I assume that if you submit to upstream this new hypercall then
> > Well, this is only an experimental system that's completely disabled
> > by default. Making the assumption that people who make use of it will
> > know what they are doing I think is fair.
>
> I assume that if you submit to upstream this new hypercall then there is
> longer plan to have more
On Thu, Dec 19, 2019 at 4:05 AM Jan Beulich wrote:
>
> On 19.12.2019 01:15, Tamas K Lengyel wrote:
> > On Wed, Dec 18, 2019 at 4:02 PM Julien Grall wrote:
> >> On 18/12/2019 22:33, Tamas K Lengyel wrote:
> >>> On Wed, Dec 18, 2019 at 3:00 PM Julien Grall wrote:
> You also have multiple
On 19.12.2019 01:15, Tamas K Lengyel wrote:
> On Wed, Dec 18, 2019 at 4:02 PM Julien Grall wrote:
>> On 18/12/2019 22:33, Tamas K Lengyel wrote:
>>> On Wed, Dec 18, 2019 at 3:00 PM Julien Grall wrote:
You also have multiple loop on the page_list in this function. Given the
number of
Hi Tamas,
On 19/12/2019 00:15, Tamas K Lengyel wrote:
On Wed, Dec 18, 2019 at 4:02 PM Julien Grall wrote:
Hi,
On 18/12/2019 22:33, Tamas K Lengyel wrote:
On Wed, Dec 18, 2019 at 3:00 PM Julien Grall wrote:
Hi Tamas,
On 18/12/2019 19:40, Tamas K Lengyel wrote:
Implement hypercall that
On Wed, Dec 18, 2019 at 4:02 PM Julien Grall wrote:
>
> Hi,
>
> On 18/12/2019 22:33, Tamas K Lengyel wrote:
> > On Wed, Dec 18, 2019 at 3:00 PM Julien Grall wrote:
> >>
> >> Hi Tamas,
> >>
> >> On 18/12/2019 19:40, Tamas K Lengyel wrote:
> >>> Implement hypercall that allows a fork to shed all
Hi,
On 18/12/2019 22:33, Tamas K Lengyel wrote:
On Wed, Dec 18, 2019 at 3:00 PM Julien Grall wrote:
Hi Tamas,
On 18/12/2019 19:40, Tamas K Lengyel wrote:
Implement hypercall that allows a fork to shed all memory that got allocated
for it during its execution and re-load its vCPU context
On Wed, Dec 18, 2019 at 3:00 PM Julien Grall wrote:
>
> Hi Tamas,
>
> On 18/12/2019 19:40, Tamas K Lengyel wrote:
> > Implement hypercall that allows a fork to shed all memory that got allocated
> > for it during its execution and re-load its vCPU context from the parent VM.
> > This allows the
Hi Tamas,
On 18/12/2019 19:40, Tamas K Lengyel wrote:
Implement hypercall that allows a fork to shed all memory that got allocated
for it during its execution and re-load its vCPU context from the parent VM.
This allows the forked VM to reset into the same state the parent VM is in a
faster way
12 matches
Mail list logo
