Durrant, Paul writes ("RE: [PATCH v6 1/6] libxl: add infrastructure to track
and query 'recent' domids"):
> Not being co-located makes this somewhat tricky; I think it will basically
> still come down to me writing some code and then you saying whether that's
> what you meant... unless you can
> -Original Message-
> From: Ian Jackson
> Sent: 20 February 2020 16:46
> To: Durrant, Paul
> Cc: xen-devel@lists.xenproject.org; Wei Liu ; Anthony Perard
>
> Subject: RE: [PATCH v6 1/6] libxl: add infrastructure to track and query
> 'recent' domids
>
> Durrant, Paul writes ("RE:
> -Original Message-
> From: Ian Jackson
> Sent: 20 February 2020 16:20
> To: Durrant, Paul
> Cc: xen-devel@lists.xenproject.org; Wei Liu ; Anthony Perard
>
> Subject: Re: [PATCH v6 1/6] libxl: add infrastructure to track and query
> 'recent' domids
>
> Paul Durrant writes ("[PATCH v6
Durrant, Paul writes ("RE: [PATCH v6 1/6] libxl: add infrastructure to track
and query 'recent' domids"):
> [Ian:]
> > IMO the reuse timeout call and the clock_gettime call should be put in
> > libxl__open_domid_history; and the time filtering check should be
> > folded into libxl__read_recent.
>
Paul Durrant writes ("[PATCH v6 1/6] libxl: add infrastructure to track and
query 'recent' domids"):
> A domid is considered recent if the domain it represents was destroyed
> less than a specified number of seconds ago. For debugging and/or testing
> purposes the number can be set using the
A domid is considered recent if the domain it represents was destroyed
less than a specified number of seconds ago. For debugging and/or testing
purposes the number can be set using the environment variable
LIBXL_DOMID_REUSE_TIMEOUT. If the variable does not exist then a default
value of 60s is
