From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/6] qtest: add test framework
Date: Mon, 16 Jan 2012 19:08:52 +0200 [thread overview]
Message-ID: <4F1459A4.2030502@redhat.com> (raw)
In-Reply-To: <CAJSP0QXMJv+n68n8fGY9GbA2210u3QoB6wXyCU16aq36GFaR8Q@mail.gmail.com>
On 01/16/2012 06:59 PM, Stefan Hajnoczi wrote:
> > + }
> > + qtest_send_prefix(chr);
> > + qtest_send(chr, "OK 0x%04x\n", value);
>
> Endianness is a little weird here. memory.c will byteswap if target
> and device endianness differ.
>
> Imagine the case where we're on an x86 host, running a ppc guest,
> reading from PCI configuration space (little-endian). Since ppc
> (target endian) is big-endian and the device is little-endian the
> value read/written will be byteswapped. However, our qtest runs on
> the host and therefore we don't want that automatic swap (or we need
> to neutralize it by performing another byteswap on top).
>
Good catch. This is another example of how an access depends not only
on the destination, but also on the source. Here the source is not the
cpu; it's qtest.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-16 17:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 18:32 [Qemu-devel] [PATCH 1/6] qtest: add test framework Anthony Liguori
2012-01-13 18:32 ` [Qemu-devel] [PATCH 2/6] qtest: add support for -M pc Anthony Liguori
2012-01-13 18:32 ` [Qemu-devel] [PATCH 3/6] qtest: add C version of test infrastructure Anthony Liguori
2012-01-17 11:33 ` Stefan Hajnoczi
2012-01-17 13:33 ` Paolo Bonzini
2012-01-17 13:39 ` Stefan Hajnoczi
2012-01-17 16:09 ` Paolo Bonzini
2012-01-18 16:00 ` Kevin Wolf
2012-01-18 16:02 ` Paolo Bonzini
2012-01-18 16:08 ` Anthony Liguori
2012-01-13 18:32 ` [Qemu-devel] [PATCH 4/6] make: add check targets based on gtester Anthony Liguori
2012-01-16 17:16 ` Paolo Bonzini
2012-01-16 18:14 ` Anthony Liguori
2012-01-17 10:42 ` Paolo Bonzini
2012-01-17 14:04 ` Paolo Bonzini
2012-01-17 14:22 ` Anthony Liguori
2012-01-13 18:32 ` [Qemu-devel] [PATCH 5/6] rtc: split out macros into a header file and use in test case Anthony Liguori
2012-01-13 18:32 ` [Qemu-devel] [PATCH 6/6] qtest: add rtc-test test-case Anthony Liguori
2012-01-16 16:59 ` [Qemu-devel] [PATCH 1/6] qtest: add test framework Stefan Hajnoczi
2012-01-16 17:08 ` Avi Kivity [this message]
2012-01-16 17:20 ` Anthony Liguori
2012-01-16 17:08 ` Anthony Liguori
2012-01-17 11:13 ` Stefan Hajnoczi
2012-01-18 9:05 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2012-01-17 17:22 Michael Walle
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=4F1459A4.2030502@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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).