qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Shlomo Pongratz <shlomo.pongratz@huawei.com>,
	Pavel Fedin <p.fedin@samsung.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500
Date: Tue, 12 May 2015 10:56:57 +0100	[thread overview]
Message-ID: <CAFEAcA_Hi7H1U0W287JCoZRsB9fV4x9rAm2gYCGyzGsQsOtE9Q@mail.gmail.com> (raw)
In-Reply-To: <20150512092015.GF18200@redhat.com>

On 12 May 2015 at 10:20, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Fri, May 08, 2015 at 04:09:01PM +0300, Pavel Fedin wrote:
>>  static void machvirt_machine_init(void)
>>  {
>>      type_register_static(&machvirt_info);
>> +    type_register_static(&machvirtv3_info);
>>  }
>
> If we're going to start adding new machine types for aarch64 with
> version numbers

We are not. Support for GICv2 vs v3 should be dealt with
by suitable machine properties (and by figuring out how
we handle probing for which of the two the host kernel
can provide us).

>, then I think we should we be using a versioning
> scheme that matches what we do on x86. ie, define versioned
> machine types based on the QEMU release numbers

And we're not doing that until we absolutely have to, ie we
have somebody demanding cross-version migration support and
willing to back it up with the necessary battery of testing.
That day will come, but I don't think we're ready for it yet.

thanks
-- PMM

  parent reply	other threads:[~2015-05-12  9:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 13:09 [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-05-11 11:30 ` Shlomo Pongratz
2015-05-12  9:05   ` Pavel Fedin
2015-05-12 11:29     ` Shlomo Pongratz
2015-05-12 12:33       ` Pavel Fedin
2015-05-13 10:34         ` Shlomo Pongratz
2015-05-13 13:57           ` Pavel Fedin
2015-05-14 12:01             ` Shlomo Pongratz
2015-05-14 15:27               ` Pavel Fedin
2015-05-12  9:11   ` Pavel Fedin
2015-05-12  9:20 ` Daniel P. Berrange
2015-05-12  9:32   ` Pavel Fedin
2015-05-12  9:56   ` Peter Maydell [this message]
2015-05-12 11:15     ` Pavel Fedin
2015-05-12 11:20       ` Daniel P. Berrange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFEAcA_Hi7H1U0W287JCoZRsB9fV4x9rAm2gYCGyzGsQsOtE9Q@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=berrange@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).