* Michael Roth (mdr...@linux.vnet.ibm.com) wrote:
> Quoting David Gibson (2018-07-17 05:50:06)
> > On Thu, Jun 21, 2018 at 03:23:21PM +0200, Greg Kurz wrote:
> > > On Thu, 21 Jun 2018 11:18:09 +1000
> > > David Gibson wrote:
> > >
> > > > On Wed, Jun 20, 2018 at 02:54:15PM +0200, Greg Kurz wrote:
Quoting David Gibson (2018-07-17 05:50:06)
> On Thu, Jun 21, 2018 at 03:23:21PM +0200, Greg Kurz wrote:
> > On Thu, 21 Jun 2018 11:18:09 +1000
> > David Gibson wrote:
> >
> > > On Wed, Jun 20, 2018 at 02:54:15PM +0200, Greg Kurz wrote:
> > > > The spapr capability framework was introduced in QEMU
On Thu, Jun 21, 2018 at 03:23:21PM +0200, Greg Kurz wrote:
> On Thu, 21 Jun 2018 11:18:09 +1000
> David Gibson wrote:
>
> > On Wed, Jun 20, 2018 at 02:54:15PM +0200, Greg Kurz wrote:
> > > The spapr capability framework was introduced in QEMU 2.12. It allows
> > > to have an explicit control on h
On Thu, 21 Jun 2018 11:18:09 +1000
David Gibson wrote:
> On Wed, Jun 20, 2018 at 02:54:15PM +0200, Greg Kurz wrote:
> > The spapr capability framework was introduced in QEMU 2.12. It allows
> > to have an explicit control on how host features are exposed to the
> > guest. This is especially neede
On Wed, Jun 20, 2018 at 02:54:15PM +0200, Greg Kurz wrote:
> The spapr capability framework was introduced in QEMU 2.12. It allows
> to have an explicit control on how host features are exposed to the
> guest. This is especially needed to handle migration between hetero-
> geneous hosts (eg, POWER8
The spapr capability framework was introduced in QEMU 2.12. It allows
to have an explicit control on how host features are exposed to the
guest. This is especially needed to handle migration between hetero-
geneous hosts (eg, POWER8 to POWER9). It is also used to expose fixes/
workarounds against s
