Ian Campbell writes:
> On Thu, 2015-05-28 at 15:41 +0200, Vitaly Kuznetsov wrote:
>> > I.e. what you currently implement is David's model without Konrad's
>> > later alternative really having been explored? Iiuc David's main
>> > reservation (which I share) was against a myriad of reset-this and
On Thu, 2015-05-28 at 15:41 +0200, Vitaly Kuznetsov wrote:
> > I.e. what you currently implement is David's model without Konrad's
> > later alternative really having been explored? Iiuc David's main
> > reservation (which I share) was against a myriad of reset-this and
> > reset-that hypercalls, w
"Jan Beulich" writes:
On 28.05.15 at 14:27, wrote:
>> "Jan Beulich" writes:
>>
>> On 27.05.15 at 17:25, wrote:
This patch series provides x86 PVHVM domains with an ability to perform
kexec/kdump-style operations.
>>>
>>> Before I get to look at this latest version, may I go
>>> On 28.05.15 at 14:27, wrote:
> "Jan Beulich" writes:
>
> On 27.05.15 at 17:25, wrote:
>>> This patch series provides x86 PVHVM domains with an ability to perform
>>> kexec/kdump-style operations.
>>
>> Before I get to look at this latest version, may I go a step back and
>> ask for clar
"Jan Beulich" writes:
On 27.05.15 at 17:25, wrote:
>> This patch series provides x86 PVHVM domains with an ability to perform
>> kexec/kdump-style operations.
>
> Before I get to look at this latest version, may I go a step back and
> ask for clarification whether all of these (seemingly fr
>>> On 27.05.15 at 17:25, wrote:
> This patch series provides x86 PVHVM domains with an ability to perform
> kexec/kdump-style operations.
Before I get to look at this latest version, may I go a step back and
ask for clarification whether all of these (seemingly fragile)
manipulations are actuall
