From: Rusty Russell <rusty@rustcorp.com.au>
To: Pawel Moll <pawel.moll@arm.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Marc Zyngier <Marc.Zyngier@arm.com>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm\@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm\@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/3] virtio-mmio: handle BE guests on LE hosts
Date: Tue, 15 Oct 2013 09:32:47 +1030 [thread overview]
Message-ID: <877gdfbgmg.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1381747859.3247.33.camel@hornet>
Pawel Moll <pawel.moll@arm.com> writes:
> On Mon, 2013-10-14 at 11:46 +0100, Michael S. Tsirkin wrote:
>> What I meant is that under the proposed scheme, users with
>> existing v1 drivers must configure a v1 device explicitly.
>>
>> According to the plan, drivers will be updated so they can
>> work with both v1 devices and new v2 devices.
>>
>> But if you configure a v2 device, old drivers
>> will not work.
>
> That's correct, yes. If qemu 2015(16? 17?).01 will provide v2 devices
> only, kernel 3.11 is not going to recognize any of them.
>
> What will happen in reality, though, is that the implementation of the
> Linux v1/v2 driver will pre-date *any* v2 device by far. First
> implementation of v1 devices appeared almost 2 years after the driver
> appeared. It will take year for people to upgrade to v2, and probably
> only after they experience problems with page-based addressing mode.
>
> I think I can live with this.
Yes, this makes sense. In particular, MMIO doesn't have any users you
don't control at this point.
I expect it to be less than 2 years to get into qemu, but there'll be no
compelling reason to use v2 devices for at least that long.
Cheers,
Rusty.
next prev parent reply other threads:[~2013-10-14 23:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 14:36 [PATCH 0/3] virtio-mmio: handle BE guests on LE hosts Marc Zyngier
2013-10-11 14:36 ` [PATCH 1/3] virtio: let the guest report its endianess if advertized by the host Marc Zyngier
2013-10-11 14:36 ` [PATCH 2/3] virtio: mmio: fix signature checking for BE guests Marc Zyngier
2013-10-14 8:46 ` Pawel Moll
2013-10-14 9:11 ` Rusty Russell
2013-11-05 3:36 ` Rusty Russell
2013-11-05 10:45 ` Pawel Moll
2013-11-07 0:36 ` Rusty Russell
2013-10-11 14:36 ` [PATCH 3/3] virtio: mmio: access configuration space as little-endian Marc Zyngier
2013-10-14 8:44 ` Pawel Moll
2013-10-12 18:28 ` [PATCH 0/3] virtio-mmio: handle BE guests on LE hosts Michael S. Tsirkin
2013-10-14 8:24 ` Marc Zyngier
2013-10-14 8:59 ` Michael S. Tsirkin
2013-10-14 9:04 ` Pawel Moll
2013-10-14 10:46 ` Michael S. Tsirkin
2013-10-14 10:50 ` Pawel Moll
2013-10-14 23:02 ` Rusty Russell [this message]
2013-10-14 9:13 ` Rusty Russell
2013-10-14 8:21 ` Rusty Russell
2013-10-14 12:36 ` Marc Zyngier
2013-10-14 12:51 ` Michael S. Tsirkin
2013-10-17 0:27 ` Rusty Russell
2013-10-14 13:03 ` Paolo Bonzini
2013-10-14 13:10 ` Alexander Graf
2013-10-14 13:13 ` Paolo Bonzini
2013-10-14 13:24 ` Marc Zyngier
2013-10-14 13:29 ` Paolo Bonzini
2013-10-14 13:39 ` Alexander Graf
2013-10-14 13:49 ` Marc Zyngier
2013-10-14 14:05 ` Michael S. Tsirkin
2013-10-14 14:13 ` Marc Zyngier
2013-10-14 14:16 ` Alexander Graf
2013-10-14 14:52 ` Marc Zyngier
2013-10-14 14:56 ` Paolo Bonzini
2013-10-14 15:12 ` Marc Zyngier
2013-10-14 15:22 ` Paolo Bonzini
2013-10-14 15:36 ` Marc Zyngier
2013-10-14 16:50 ` Paolo Bonzini
2013-10-14 17:10 ` Michael S. Tsirkin
2013-10-14 23:23 ` Rusty Russell
2013-10-15 6:38 ` Michael S. Tsirkin
2013-10-15 9:19 ` Marc Zyngier
2013-10-14 15:45 ` Anup Patel
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=877gdfbgmg.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=Marc.Zyngier@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mst@redhat.com \
--cc=pawel.moll@arm.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