On 07/11/2016 02:38 PM, Sergey Fedorov wrote:
> On 11/07/16 15:36, Christian Borntraeger wrote:
>> On 07/06/2016 11:14 PM, Sergey Fedorov wrote:
>>> From: Alex Bennée
>>>
>>> CPUState is a fairly common pointer to pass to these helpers. This means
>>> if you need other arguments for the async_run_
On 11/07/16 15:36, Christian Borntraeger wrote:
> On 07/06/2016 11:14 PM, Sergey Fedorov wrote:
>> From: Alex Bennée
>>
>> CPUState is a fairly common pointer to pass to these helpers. This means
>> if you need other arguments for the async_run_on_cpu case you end up
>> having to do a g_malloc to
On 07/06/2016 11:14 PM, Sergey Fedorov wrote:
> From: Alex Bennée
>
> CPUState is a fairly common pointer to pass to these helpers. This means
> if you need other arguments for the async_run_on_cpu case you end up
> having to do a g_malloc to stuff additional data into the routine. For
> the curr
On Thu, Jul 07, 2016 at 12:14:54AM +0300, Sergey Fedorov wrote:
> From: Alex Bennée
>
> CPUState is a fairly common pointer to pass to these helpers. This means
> if you need other arguments for the async_run_on_cpu case you end up
> having to do a g_malloc to stuff additional data into the routi
From: Alex Bennée
CPUState is a fairly common pointer to pass to these helpers. This means
if you need other arguments for the async_run_on_cpu case you end up
having to do a g_malloc to stuff additional data into the routine. For
the current users this isn't a massive deal but for MTTCG this get
