From: Pawel Moll <pawel.moll@arm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/4] virtio-mmio transport
Date: Mon, 12 Dec 2011 14:51:31 +0000 [thread overview]
Message-ID: <1323701491.2391.73.camel@hornet.cambridge.arm.com> (raw)
In-Reply-To: <201112121445.27873.paul@codesourcery.com>
On Mon, 2011-12-12 at 14:45 +0000, Paul Brook wrote:
> I suggest that the device to buffer writes to the high part, and construct the
> actual 64-bit value when the low part is written. That allows 32-bit guests
> can ignore the high part entirely.
This sounds good to me. If we define the reset value of both registers
as 0 (which is consistent with "0 = stop" condition) a 32-bit guest will
be able to behave as you are suggesting.
Cool, I will keep this in mind.
Thanks!
Paweł
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2011-12-12 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1321282528-19070-1-git-send-email-peter.maydell@linaro.org>
[not found] ` <201112091516.07644.paul@codesourcery.com>
[not found] ` <4EE22FF4.5050903@codemonkey.ws>
[not found] ` <201112120252.35295.paul@codesourcery.com>
2011-12-12 11:16 ` [Qemu-devel] [RFC 0/4] virtio-mmio transport Pawel Moll
2011-12-12 14:45 ` Paul Brook
[not found] ` <201112121445.27873.paul@codesourcery.com>
2011-12-12 14:51 ` Pawel Moll [this message]
2011-12-16 5:36 ` Rusty Russell
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=1323701491.2391.73.camel@hornet.cambridge.arm.com \
--to=pawel.moll@arm.com \
--cc=anthony@codemonkey.ws \
--cc=paul@codesourcery.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox