>>> On 13.02.15 at 19:09, wrote:
> On 13/02/15 18:03, Tamas K Lengyel wrote:
>> On Fri, Feb 13, 2015 at 6:23 PM, Andrew Cooper
>> wrote:
>>> On 13/02/15 16:33, Tamas K Lengyel wrote:
v5: Style fixes
Convert gfn to uint32_t
>>> It is perfectly possible to have guests with more memory
On Fri, Feb 13, 2015 at 7:09 PM, Andrew Cooper
wrote:
> On 13/02/15 18:03, Tamas K Lengyel wrote:
>> On Fri, Feb 13, 2015 at 6:23 PM, Andrew Cooper
>> wrote:
>>> On 13/02/15 16:33, Tamas K Lengyel wrote:
The public mem_event structures used to communicate with helper
applications via
>
On 13/02/15 18:03, Tamas K Lengyel wrote:
> On Fri, Feb 13, 2015 at 6:23 PM, Andrew Cooper
> wrote:
>> On 13/02/15 16:33, Tamas K Lengyel wrote:
>>> The public mem_event structures used to communicate with helper
>>> applications via
>>> shared rings have been used in different settings. However,
On Fri, Feb 13, 2015 at 6:23 PM, Andrew Cooper
wrote:
> On 13/02/15 16:33, Tamas K Lengyel wrote:
>> The public mem_event structures used to communicate with helper applications
>> via
>> shared rings have been used in different settings. However, the variable
>> names
>> within this structure h
On 13/02/15 16:33, Tamas K Lengyel wrote:
> The public mem_event structures used to communicate with helper applications
> via
> shared rings have been used in different settings. However, the variable names
> within this structure have not reflected this fact, resulting in the reuse of
> variable
The public mem_event structures used to communicate with helper applications via
shared rings have been used in different settings. However, the variable names
within this structure have not reflected this fact, resulting in the reuse of
variables to mean different things under different scenarios.
