Hi Jan,
On 04/06/2021 14:23, Jan Beulich wrote:
On 03.06.2021 11:39, Julien Grall wrote:
On 27/05/2021 14:58, Jan Beulich wrote:
On 27.05.2021 15:06, Julien Grall wrote:
On 27/05/2021 13:33, Jan Beulich wrote:
@@ -1046,12 +1051,14 @@ static struct page_info *alloc_heap_page
if ( firs
On 03.06.2021 11:39, Julien Grall wrote:
> On 27/05/2021 14:58, Jan Beulich wrote:
>> On 27.05.2021 15:06, Julien Grall wrote:
>>> On 27/05/2021 13:33, Jan Beulich wrote:
@@ -1046,12 +1051,14 @@ static struct page_info *alloc_heap_page
if ( first_dirty != INVALID_DIRTY_IDX ||
Hi Jan,
On 27/05/2021 14:58, Jan Beulich wrote:
On 27.05.2021 15:06, Julien Grall wrote:
On 27/05/2021 13:33, Jan Beulich wrote:
Especially when dealing with large amounts of memory, memset() may not
be very efficient; this can be bad enough that even for debug builds a
custom function is warr
On 27.05.2021 15:06, Julien Grall wrote:
> On 27/05/2021 13:33, Jan Beulich wrote:
>> Especially when dealing with large amounts of memory, memset() may not
>> be very efficient; this can be bad enough that even for debug builds a
>> custom function is warranted. We additionally want to distinguish
Hi Jan,
On 27/05/2021 13:33, Jan Beulich wrote:
Especially when dealing with large amounts of memory, memset() may not
be very efficient; this can be bad enough that even for debug builds a
custom function is warranted. We additionally want to distinguish "hot"
and "cold" cases.
Do you have an
Especially when dealing with large amounts of memory, memset() may not
be very efficient; this can be bad enough that even for debug builds a
custom function is warranted. We additionally want to distinguish "hot"
and "cold" cases.
Keep the default fallback to clear_page_*() in common code; this m
