qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Shlomo Pongratz <shlomo.pongratz@huawei.com>,
	Pavel Fedin <p.fedin@samsung.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Ashok Kumar <ashoks@broadcom.com>
Subject: Re: [Qemu-devel] [PATCH] Use Aff1 with mpidr
Date: Tue, 2 Jun 2015 17:54:28 +0200	[thread overview]
Message-ID: <20150602175428.7f24de2f@nial.brq.redhat.com> (raw)
In-Reply-To: <CAFEAcA_eA=xUQ+n-A=sqAvc9C-6_yr34bbxoFMQF+nXdejcmRQ@mail.gmail.com>

On Tue, 2 Jun 2015 16:42:31 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:

> On 2 June 2015 at 16:32, Igor Mammedov <imammedo@redhat.com> wrote:
> > On Fri, 29 May 2015 16:41:01 +0300
> > Pavel Fedin <p.fedin@samsung.com> wrote:
> >
> >>  Hello!
> >>
> >> > Well KVM side should be fixed instead of driving us along wrong route.
> >>
> >>  It can be fixed... Perhaps... If kernel developers acknowledge this is a problem, which
> >> might not happen.
> >>  But still we will have older kernels, and what? Don't you want 64-bit ARM KVM work on
> >> them?
> > I think arm target is not counted as stable  yet, so we don't have to keep
> > compatibility layer yet.
> 
> We don't want to break running KVM on older kernels on ARM.
> It's OK if an older kernel means you don't get access to shiny
> new features (like GICv3 support, maybe), but QEMU binaries
> and configurations that used to work on those kernels should
> continue to work on those kernels.
perhaps we would need to start using machine types then like we do for x86
or something like this.

> 
> thanks
> -- PMM

  reply	other threads:[~2015-06-02 15:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 10:32 [Qemu-devel] [PATCH] Use Aff1 with mpidr Pavel Fedin
2015-05-28 14:57 ` Shlomo Pongratz
2015-05-29  6:45   ` Pavel Fedin
2015-05-31 11:03     ` Shlomo Pongratz
2015-06-01  6:34       ` Pavel Fedin
2015-06-01  9:03       ` Pavel Fedin
2015-06-01 14:26         ` Shlomo Pongratz
2015-06-02  6:29           ` Pavel Fedin
2015-06-02 15:37       ` Igor Mammedov
2015-05-29  8:36 ` Igor Mammedov
2015-05-29  8:53   ` Pavel Fedin
2015-05-29  9:18     ` Igor Mammedov
2015-05-29 12:26       ` Pavel Fedin
2015-05-29 13:03         ` Igor Mammedov
2015-05-29 13:41           ` Pavel Fedin
2015-06-02 15:32             ` Igor Mammedov
2015-06-02 15:42               ` Peter Maydell
2015-06-02 15:54                 ` Igor Mammedov [this message]
2015-05-29 17:37           ` Pavel Fedin
2015-05-30  2:30             ` Shannon Zhao

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=20150602175428.7f24de2f@nial.brq.redhat.com \
    --to=imammedo@redhat.com \
    --cc=ashoks@broadcom.com \
    --cc=p.fedin@samsung.com \
    --cc=peter.maydell@linaro.org \
    --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).