On 10/1/18 2:35 AM, Erik Skultety wrote:
On Mon, Oct 01, 2018 at 08:04:57AM +0200, Erik Skultety wrote:
On Thu, Sep 27, 2018 at 08:25:53AM -0600, Jim Fehlig wrote:
On 9/27/18 3:29 AM, Erik Skultety wrote:
On Wed, Sep 26, 2018 at 11:31:19AM -0600, Jim Fehlig wrote:
The preferred location for s
On Mon, Oct 01, 2018 at 08:04:57AM +0200, Erik Skultety wrote:
> On Thu, Sep 27, 2018 at 08:25:53AM -0600, Jim Fehlig wrote:
> > On 9/27/18 3:29 AM, Erik Skultety wrote:
> > > On Wed, Sep 26, 2018 at 11:31:19AM -0600, Jim Fehlig wrote:
> > > > The preferred location for setting the nested CPU flag
On Thu, Sep 27, 2018 at 08:25:53AM -0600, Jim Fehlig wrote:
> On 9/27/18 3:29 AM, Erik Skultety wrote:
> > On Wed, Sep 26, 2018 at 11:31:19AM -0600, Jim Fehlig wrote:
> > > The preferred location for setting the nested CPU flag changed in
> > > Xen 4.10 and is advertised via the LIBXL_HAVE_BUILDINF
On 9/27/18 3:29 AM, Erik Skultety wrote:
On Wed, Sep 26, 2018 at 11:31:19AM -0600, Jim Fehlig wrote:
The preferred location for setting the nested CPU flag changed in
Xen 4.10 and is advertised via the LIBXL_HAVE_BUILDINFO_NESTED_HVM
define. Commit 95d19cd0 changed libxl to use the new preferre
On Wed, Sep 26, 2018 at 11:31:19AM -0600, Jim Fehlig wrote:
> The preferred location for setting the nested CPU flag changed in
> Xen 4.10 and is advertised via the LIBXL_HAVE_BUILDINFO_NESTED_HVM
> define. Commit 95d19cd0 changed libxl to use the new preferred
> location but unconditionally chang
The preferred location for setting the nested CPU flag changed in
Xen 4.10 and is advertised via the LIBXL_HAVE_BUILDINFO_NESTED_HVM
define. Commit 95d19cd0 changed libxl to use the new preferred
location but unconditionally changed the tests, causing 'make check'
failures against Xen < 4.10 that
