Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-07 Thread Steven Sistare
On 10/7/2024 11:36 AM, Peter Xu wrote: On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: diff --git a/system/trace-events b/system/trace-events index 074d001..4669411 100644 --- a/system/trace-events +++ b/system/trace-events @@ -47,3 +47,6 @@ dirtylimit_vcpu_execute(int cpu_index,

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-07 Thread Peter Xu
On Mon, Oct 07, 2024 at 06:23:26PM +0200, David Hildenbrand wrote: > > Yes I thought it could be unconditionally. We can discuss downside below, > > I think we can still use a new flag otherwise, but the idea would be the > > same, where I want the flag to be explicit in the callers not implicitly

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-07 Thread David Hildenbrand
On 04.10.24 15:24, Peter Xu wrote: On Fri, Oct 04, 2024 at 02:54:38PM +0200, David Hildenbrand wrote: On 04.10.24 14:33, Peter Xu wrote: On Fri, Oct 04, 2024 at 12:14:35PM +0200, David Hildenbrand wrote: On 03.10.24 18:14, Peter Xu wrote: On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistar

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-07 Thread Peter Xu
On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: > diff --git a/system/trace-events b/system/trace-events > index 074d001..4669411 100644 > --- a/system/trace-events > +++ b/system/trace-events > @@ -47,3 +47,6 @@ dirtylimit_vcpu_execute(int cpu_index, int64_t > sleep_time_us) "CPU[%

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-04 Thread Peter Xu
On Fri, Oct 04, 2024 at 02:54:38PM +0200, David Hildenbrand wrote: > On 04.10.24 14:33, Peter Xu wrote: > > On Fri, Oct 04, 2024 at 12:14:35PM +0200, David Hildenbrand wrote: > > > On 03.10.24 18:14, Peter Xu wrote: > > > > On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: > > > > > Al

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-04 Thread David Hildenbrand
On 04.10.24 14:33, Peter Xu wrote: On Fri, Oct 04, 2024 at 12:14:35PM +0200, David Hildenbrand wrote: On 03.10.24 18:14, Peter Xu wrote: On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: Allocate anonymous memory using mmap MAP_ANON or memfd_create depending on the value of the an

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-04 Thread Peter Xu
On Fri, Oct 04, 2024 at 12:14:35PM +0200, David Hildenbrand wrote: > On 03.10.24 18:14, Peter Xu wrote: > > On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: > > > Allocate anonymous memory using mmap MAP_ANON or memfd_create depending > > > on the value of the anon-alloc machine prope

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-04 Thread David Hildenbrand
On 03.10.24 18:14, Peter Xu wrote: On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: Allocate anonymous memory using mmap MAP_ANON or memfd_create depending on the value of the anon-alloc machine property. This option applies to memory allocated as a side effect of creating various

Re: [PATCH V2 01/13] machine: alloc-anon option

2024-10-03 Thread Peter Xu
On Mon, Sep 30, 2024 at 12:40:32PM -0700, Steve Sistare wrote: > Allocate anonymous memory using mmap MAP_ANON or memfd_create depending > on the value of the anon-alloc machine property. This option applies to > memory allocated as a side effect of creating various devices. It does > not apply to

[PATCH V2 01/13] machine: alloc-anon option

2024-09-30 Thread Steve Sistare
Allocate anonymous memory using mmap MAP_ANON or memfd_create depending on the value of the anon-alloc machine property. This option applies to memory allocated as a side effect of creating various devices. It does not apply to memory-backend-objects, whether explicitly specified on the command li