From: David Gibson <david@gibson.dropbear.id.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [RFC PATCH] spapr_vio/spapr_iommu: Move VIO bypass where it belongs
Date: Wed, 14 Jan 2015 13:40:48 +1100 [thread overview]
Message-ID: <20150114024048.GS3654@voom.BigPond> (raw)
In-Reply-To: <54AFD0AD.1000707@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Fri, Jan 09, 2015 at 01:59:25PM +0100, Paolo Bonzini wrote:
>
>
> On 09/01/2015 13:53, Alexey Kardashevskiy wrote:
> >> > I think the minimum version should be 2 as well, because migrating from
> >> > version 1 will not set the bypass field correctly.
> > This why the patch is "RFC" :)
> >
> > I can keep the flag in TCETable which would be a bit ugly but won't break
> > migration. Is there any better way to keep compatibility?
>
> No, I don't think so.
Alas, there doesn't seem to be. I have the same thing with my RTC
patches, where I have to keep the rtc_offset field in the
sPAPREnvironment just to grab it on migration from an older version
and stuff it into the new device instead.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-14 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 1:02 [Qemu-devel] [RFC PATCH] spapr_vio/spapr_iommu: Move VIO bypass where it belongs Alexey Kardashevskiy
2015-01-09 10:05 ` Paolo Bonzini
2015-01-09 12:53 ` Alexey Kardashevskiy
2015-01-09 12:59 ` Paolo Bonzini
2015-01-14 2:40 ` David Gibson [this message]
2015-01-14 2:42 ` David Gibson
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=20150114024048.GS3654@voom.BigPond \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.