[Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Peter Maydell]

Hi; I noticed today that the virt board doesn't have a virt-2.10
machine type defined. Do we need to add it before release?

(I don't know if there have in fact been any changes between
2.9 and 2.10 that would be compatibility issues.)

thanks
-- PMM

Re: [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Dr. David Alan Gilbert]

* Peter Maydell (peter.maydell@linaro.org) wrote:
> Hi; I noticed today that the virt board doesn't have a virt-2.10
> machine type defined. Do we need to add it before release?
> 
> (I don't know if there have in fact been any changes between
> 2.9 and 2.10 that would be compatibility issues.)

I think there's two sub questions:
  a) The virt-2.9 needs to pick up HW_COMPAT_2_9 if anything
  in it is relevant for ARM

  b) If anything is relevant in it for ARM then you probably
  want a virt-2.10 so that you can take advantage of whatever
  was changed that needed compatibility adding in HW_COMPAT_2_9

(The other thing is figuring out what we missed in HW_COMPAT_2_9,
we normally miss something).

Dave

> thanks
> -- PMM
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

Re: [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Peter Maydell]

On 4 August 2017 at 18:48, Dr. David Alan Gilbert <dgilbert@redhat.com> wrote:
> * Peter Maydell (peter.maydell@linaro.org) wrote:
>> Hi; I noticed today that the virt board doesn't have a virt-2.10
>> machine type defined. Do we need to add it before release?
>>
>> (I don't know if there have in fact been any changes between
>> 2.9 and 2.10 that would be compatibility issues.)
>
> I think there's two sub questions:
>   a) The virt-2.9 needs to pick up HW_COMPAT_2_9 if anything
>   in it is relevant for ARM
>
>   b) If anything is relevant in it for ARM then you probably
>   want a virt-2.10 so that you can take advantage of whatever
>   was changed that needed compatibility adding in HW_COMPAT_2_9

...and also, do we as policy want to define a virt-X.Y for
every X.Y release even if it happens that there are no
changes between X.Y-1 and X.Y ? From a user point of view
it seems a bit odd for one to be missing.

thanks
-- PMM

Re: [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Paolo Bonzini]

On 04/08/2017 19:48, Dr. David Alan Gilbert wrote:
>>
>> (I don't know if there have in fact been any changes between
>> 2.9 and 2.10 that would be compatibility issues.)
> I think there's two sub questions:
>   a) The virt-2.9 needs to pick up HW_COMPAT_2_9 if anything
>   in it is relevant for ARM

Except for intel-iommu, everything else in HW_COMPAT_2_9 is relevant for
virt-2.9.  This implies that a virt-2.10 would be useful too.

Paolo

>   b) If anything is relevant in it for ARM then you probably
>   want a virt-2.10 so that you can take advantage of whatever
>   was changed that needed compatibility adding in HW_COMPAT_2_9

Re: [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Andrew Jones]

On Fri, Aug 04, 2017 at 06:42:54PM +0100, Peter Maydell wrote:
> Hi; I noticed today that the virt board doesn't have a virt-2.10
> machine type defined. Do we need to add it before release?
> 
> (I don't know if there have in fact been any changes between
> 2.9 and 2.10 that would be compatibility issues.)
> 
> thanks
> -- PMM
>

Yes, we should have separately posted that to make sure it
got in. Eric posted it, but as part of an RFC series:

 https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg00045.html

Eric, would you like to post a separate patch for the 2.10
machine type that doesn't include no_iommu?

Thanks,
drew

Re: [Qemu-devel] Do we need a "virt-2.10" machine type before the 2.10 release?

[Auger Eric]

Hi Drew,
On 07/08/2017 09:06, Andrew Jones wrote:
> On Fri, Aug 04, 2017 at 06:42:54PM +0100, Peter Maydell wrote:
>> Hi; I noticed today that the virt board doesn't have a virt-2.10
>> machine type defined. Do we need to add it before release?
>>
>> (I don't know if there have in fact been any changes between
>> 2.9 and 2.10 that would be compatibility issues.)
>>
>> thanks
>> -- PMM
>>
> 
> Yes, we should have separately posted that to make sure it
> got in. Eric posted it, but as part of an RFC series:
> 
>  https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg00045.html
> 
> Eric, would you like to post a separate patch for the 2.10
> machine type that doesn't include no_iommu?

Yes I can send it. However is it really mandated as I don't think we
have changes between 2.9 and 2.10?

Thanks

Eric
> 
> Thanks,
> drew
>