On Mon, 14 Dec 2015, Jan Beulich wrote:
> >>> On 11.12.15 at 17:56, wrote:
> > On Fri, 2015-12-11 at 16:44 +, Stefano Stabellini wrote:
> >>
> >> It is not possible to do this at runtime. I think we should do this at
> >> compile time because in any case it is not
On Fri, 11 Dec 2015, Ian Campbell wrote:
> On Fri, 2015-12-11 at 16:44 +, Stefano Stabellini wrote:
> >
> > It is not possible to do this at runtime. I think we should do this at
> > compile time because in any case it is not supported to run a QEMU built
> > for a given Xen version on a
>>> On 11.12.15 at 17:56, wrote:
> For the original issue here, could the flag be exposed as a
> XEN_SYSCTL_PHYSCAP_
Yes, I think it could, albeit calling this a "capability" or "feature"
seems odd (since really the original behavior was bogus/buggy).
But - with
On Mon, 14 Dec 2015, Jan Beulich wrote:
> >>> On 11.12.15 at 17:56, wrote:
> > For the original issue here, could the flag be exposed as a
> > XEN_SYSCTL_PHYSCAP_
>
> Yes, I think it could, albeit calling this a "capability" or "feature"
> seems odd (since really the
On Mon, 2015-12-14 at 11:19 +, Stefano Stabellini wrote:
> On Fri, 11 Dec 2015, Ian Campbell wrote:
> > On Fri, 2015-12-11 at 16:44 +, Stefano Stabellini wrote:
> > >
> > > It is not possible to do this at runtime. I think we should do this
> > > at
> > > compile time because in any case
>>> On 11.12.15 at 17:56, wrote:
> On Fri, 2015-12-11 at 16:44 +, Stefano Stabellini wrote:
>>
>> It is not possible to do this at runtime. I think we should do this at
>> compile time because in any case it is not supported to run a QEMU built
>> for a given Xen
On Fri, 2015-12-11 at 16:44 +, Stefano Stabellini wrote:
>
> It is not possible to do this at runtime. I think we should do this at
> compile time because in any case it is not supported to run a QEMU built
> for a given Xen version on a different Xen version.
I am currently working pretty