From: Scott Wood <scottwood@freescale.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
kvm-devel <kvm@vger.kernel.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"Patch Tracking" <patches@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH v2] KVM: Specify byte order for KVM_EXIT_MMIO
Date: Fri, 24 Jan 2014 20:04:19 -0600 [thread overview]
Message-ID: <1390615459.24905.748.camel@snotra.buserror.net> (raw)
In-Reply-To: <20140125015641.GA3750@cbox>
On Fri, 2014-01-24 at 17:56 -0800, Christoffer Dall wrote:
> On Sat, Jan 25, 2014 at 12:24:08AM +0000, Peter Maydell wrote:
> > Finally, I think it's a bit confusing in that "as if the guest had
> > accessed memory" is assigning implicit semantics to memory
> > in the emulated system, when memory is actually kind of outside
> > KVM's purview because it's not part of the CPU.
> >
>
> The "as if the guest had accessed memory", would imply that user space
> needs to look at the settings of the CPU (in the case of ARM the E-bit)
> to understand which value the CPU intended for the memory transaction.
No, it doesn't, just as userspace doesn't need to do that to interpret
DMA descriptors.
-Scott
next prev parent reply other threads:[~2014-01-25 2:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 23:39 [PATCH v2] KVM: Specify byte order for KVM_EXIT_MMIO Christoffer Dall
2014-01-24 23:51 ` Scott Wood
2014-01-25 0:05 ` Victor Kamensky
2014-01-25 0:24 ` Peter Maydell
2014-01-25 1:56 ` Christoffer Dall
2014-01-25 2:04 ` Scott Wood [this message]
2014-01-25 2:16 ` Alexander Graf
2014-01-25 1:58 ` Scott Wood
2014-01-25 2:15 ` Alexander Graf
2014-01-25 2:34 ` Christoffer Dall
2014-01-25 9:13 ` Alexander Graf
2014-01-25 2:37 ` Victor Kamensky
2014-01-25 9:20 ` Alexander Graf
2014-01-25 15:36 ` Victor Kamensky
2014-01-25 16:12 ` Alexander Graf
2014-01-25 16:23 ` Peter Maydell
2014-01-25 18:31 ` Christoffer Dall
2014-01-26 3:46 ` Victor Kamensky
2014-01-26 5:43 ` Victor Kamensky
2014-01-27 7:52 ` Alexander Graf
2014-01-27 9:42 ` Peter Maydell
2014-01-27 7:41 ` Alexander Graf
2014-01-28 1:59 ` Scott Wood
2014-01-28 8:55 ` Peter Maydell
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=1390615459.24905.748.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.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