On Tue, 2016-02-16 at 12:38 +, Daniel P. Berrange wrote:
> > > Regardless of the way it is exposed in libvirt API, when libvirt probes
> > > for capabilities it will *always* use '-m none'.
> >
> > Domain capabilities are currently derived almost entirely from data
> > taken from virQEMUCaps,
On Tue, Feb 16, 2016 at 01:27:55PM +0100, Andrea Bolognani wrote:
> On Tue, 2016-02-16 at 12:15 +, Daniel P. Berrange wrote:
> > On Tue, Feb 16, 2016 at 01:05:45PM +0100, Andrea Bolognani wrote:
> > > On Tue, 2016-02-16 at 10:15 +, Daniel P. Berrange wrote:
> > > > > Back to GIV.
On Tue, 2016-02-16 at 12:15 +, Daniel P. Berrange wrote:
> On Tue, Feb 16, 2016 at 01:05:45PM +0100, Andrea Bolognani wrote:
> > On Tue, 2016-02-16 at 10:15 +, Daniel P. Berrange wrote:
> > > > Back to GIV. Recognized values of gic-version are fixed at compile
> > > > time: 2, 3, host.
On Tue, 2016-02-16 at 12:09 +, Peter Maydell wrote:
> On 16 February 2016 at 12:05, Andrea Bolognani wrote:
> > The idea is to add this information to domain capabilities, which
> > already have virtualization type, architecture and machine type as
> > inputs.
> >
> >
On Tue, Feb 16, 2016 at 01:05:45PM +0100, Andrea Bolognani wrote:
> On Tue, 2016-02-16 at 10:15 +, Daniel P. Berrange wrote:
> > > Back to GIV. Recognized values of gic-version are fixed at compile
> > > time: 2, 3, host. Once again, QOM does things in code rather than data:
> > > the set of
On 16 February 2016 at 12:05, Andrea Bolognani wrote:
> The idea is to add this information to domain capabilities, which
> already have virtualization type, architecture and machine type as
> inputs.
>
> Since GIC is only available for the virt machine type on ARM hosts,
>
On Tue, 2016-02-16 at 10:15 +, Daniel P. Berrange wrote:
> > Back to GIV. Recognized values of gic-version are fixed at compile
> > time: 2, 3, host. Once again, QOM does things in code rather than data:
> > the set of values is defined in the setter function
> > virt_set_gic_version().
> >
Hello!
> I know Pavel Fedin was trying to revive kernel_irqchip=off once,
> but I don't know if that effort was abandoned or not.
It should work with the latest kernel, at least i posted patches and all of
them were applied. If nothing got broken during later
rewrites.
The only missing part
On Mon, Feb 15, 2016 at 09:41:57AM +, Peter Maydell wrote:
> On 15 February 2016 at 09:35, Martin Kletzander wrote:
> > So hardware itself supports some GIC version, let's say 3 for our case.
> > Does that mean it can be triggered to do v2 as well? I mean is it
> >
On Mon, Feb 15, 2016 at 10:35:39AM +0100, Martin Kletzander wrote:
> On Sun, Feb 14, 2016 at 01:41:41PM +0800, Peter Xu wrote:
> >
> >["gicv2", "gicv2-kvm", "gicv3-kvm"]
> >
> >Please help review whether the interface suits our need, also please
> >point out any error I have made.
> >
>
> This
On 15 February 2016 at 09:35, Martin Kletzander wrote:
> So hardware itself supports some GIC version, let's say 3 for our case.
> Does that mean it can be triggered to do v2 as well? I mean is it
> possible that HW supports multiple versions? If yes, then I suspect
> there
On Sun, Feb 14, 2016 at 01:41:41PM +0800, Peter Xu wrote:
For ARM platform, we still do not have any interface to query
whether current QEMU/host support specific GIC version. This
patchset is trying to add one QMP interface for that. By querying
the GIC capability using the new interface, one
12 matches
Mail list logo