On 01/15/2016 02:56 AM, Ian Campbell wrote:
> On Thu, 2016-01-14 at 11:31 -0700, Jim Fehlig wrote:
>> Ian Campbell wrote:
>>> On Mon, 2016-01-11 at 10:00 -0700, Jim Fehlig wrote:
On 01/07/2016 10:13 AM, Ian Campbell wrote:
> On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
>> This
On Thu, 2016-01-14 at 11:31 -0700, Jim Fehlig wrote:
> Ian Campbell wrote:
> > On Mon, 2016-01-11 at 10:00 -0700, Jim Fehlig wrote:
> > > On 01/07/2016 10:13 AM, Ian Campbell wrote:
> > > > On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
> > > > > This allows code elsewhere in libxl to find o
Ian Campbell wrote:
> On Mon, 2016-01-11 at 10:00 -0700, Jim Fehlig wrote:
>> On 01/07/2016 10:13 AM, Ian Campbell wrote:
>>> On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
This allows code elsewhere in libxl to find out what options a device
model executable supports. This is don
On Mon, 2016-01-11 at 10:00 -0700, Jim Fehlig wrote:
> On 01/07/2016 10:13 AM, Ian Campbell wrote:
> > On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
> > > This allows code elsewhere in libxl to find out what options a device
> > > model executable supports. This is done by searching the us
On 01/07/2016 10:13 AM, Ian Campbell wrote:
> On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
>> This allows code elsewhere in libxl to find out what options a device
>> model executable supports. This is done by searching the usage
>> message for fixed strings.
> Has anyone (ever, not neces
Ian Campbell writes ("Re: [PATCH 03/28] libxl: Provide libxl__dm_support_*"):
> On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
> > This allows code elsewhere in libxl to find out what options a device
> > model executable supports. This is done by searching the usage
> > message for fixed s
This allows code elsewhere in libxl to find out what options a device
model executable supports. This is done by searching the usage
message for fixed strings.
Because this involves calling fork, callers must use the async
machinery. To make this easier, and to avoid repeatedly invoking the
dm,
