From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Re: Compile files only once: some planning
Date: Wed, 24 Mar 2010 15:28:41 -0500 [thread overview]
Message-ID: <4BAA75F9.8040602@codemonkey.ws> (raw)
In-Reply-To: <f43fc5581003241324w3c90667cr5ca394db1d72e49e@mail.gmail.com>
On 03/24/2010 03:24 PM, Blue Swirl wrote:
> On 3/24/10, Michael S. Tsirkin<mst@redhat.com> wrote:
>
>> On Wed, Mar 24, 2010 at 10:05:10PM +0200, Blue Swirl wrote:
>> > On 3/24/10, Michael S. Tsirkin<mst@redhat.com> wrote:
>> > > On Tue, Mar 23, 2010 at 11:43:51PM +0200, Blue Swirl wrote:
>> > > > rtl8139.c, e1000.c: need to convert ldl/stl to cpu_physical_memory_read/write.
>> > >
>> > >
>> > > I don't see how it would help. These still get target_phys_addr_t which
>> > > is per-target. Further, a ton of devices do
>> > > cpu_register_physical_memory/qemu_register_coalesced_mmio.
>> > > These are also per target.
>> >
>> > I don't know what I was eating yesterday: there are no references to
>> > ldl/stl in either rtl8139 or e1000. In fact, the conversion is simple
>> > for the device itself, just add a property "be". The attached patch
>> > performs this part.
>> >
>> > But now there is a bigger problem, how to pass the property to the
>> > device. It's not fair to require the user to remember to set it.
>>
>>
>> I still don't fully understand how come e1000 cares about
>> target endianness.
>>
> It shouldn't. Maybe the real fix is to remove the byte swapping.
>
My previous pci memory functions patches removed the byte swapping.
The problem is that PCI devices are going to operate in little endian
mode (usually) whereas the CPU may be acting in big endian mode. We
need to do a byte swap somewhere but the better place to do it is in the
PCI bus layer.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-03-24 20:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 21:43 [Qemu-devel] Compile files only once: some planning Blue Swirl
2010-03-24 9:17 ` [Qemu-devel] " Juan Quintela
2010-03-24 17:56 ` Blue Swirl
2010-03-24 19:28 ` Juan Quintela
2010-03-24 22:47 ` Paul Brook
2010-03-24 22:57 ` Anthony Liguori
2010-03-25 3:08 ` Jamie Lokier
2010-03-25 2:54 ` Jamie Lokier
2010-03-24 9:47 ` Paolo Bonzini
2010-03-24 11:19 ` Richard Henderson
2010-03-24 14:45 ` Paolo Bonzini
2010-03-24 14:56 ` Paul Brook
2010-03-24 16:18 ` Paolo Bonzini
2010-03-24 17:27 ` Paul Brook
2010-03-24 17:07 ` Richard Henderson
2010-03-24 20:12 ` Richard Henderson
2010-03-24 18:00 ` Blue Swirl
2010-03-24 19:39 ` Michael S. Tsirkin
2010-03-24 20:05 ` Blue Swirl
2010-03-24 20:08 ` Michael S. Tsirkin
2010-03-24 20:24 ` Blue Swirl
2010-03-24 20:24 ` Michael S. Tsirkin
2010-03-24 20:32 ` Blue Swirl
2010-03-24 20:28 ` Anthony Liguori [this message]
2010-03-24 21:00 ` Aurelien Jarno
2010-03-24 22:33 ` Paul Brook
2010-03-24 22:50 ` Anthony Liguori
2010-03-24 23:05 ` Paul Brook
2010-03-24 23:07 ` Anthony Liguori
2010-03-25 8:21 ` Michael S. Tsirkin
2010-03-25 12:01 ` Paul Brook
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=4BAA75F9.8040602@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@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 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).