From: Francois WELLENREITER <francois.wellenreiter@bull.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PCI 64-bit BAR access with qemu
Date: Wed, 12 Oct 2011 14:01:19 +0200 [thread overview]
Message-ID: <4E95818F.5050101@bull.net> (raw)
In-Reply-To: <CAMo8BfKOgiaa1e3JwamC09oVJssnza6r-=aB_5r7z2OD6jydSw@mail.gmail.com>
Hi Max,
thank you for your answer. Actually, I hadn't confused.
I already thought to your proposal but I found that it was a really ugly
solution (essentially because of the uint32_t to uint64_t silent
conversion).
Isn't there any other (current or future) development that may fix it ?
François
Le 12/10/2011 13:00, Max Filippov a écrit :
>> I've read a few days ago that it was possible to emulate PCI device with
>> 64-bit BARs and have a real 64-bit memory access.
>> Thus, I've created a virtual device named toto accessible through a 64-bit
>> BAR
> You've probably confused an ability to locate BAR anywhere in 64-bit
> address space (such BAR actually spans 2 consecutive PCI BAR registers
> and has 100 in its 3 least significant bits) and an ability to access
> BAR-mapped memory in 64 bit items.
>
> You obviously want the latter but currently it is not implemented, see e.g.
>
> static inline DATA_TYPE glue(io_read, SUFFIX)(target_phys_addr_t physaddr,
> target_ulong addr,
> void *retaddr)
>
> definition in the softmmu_template.h.
>
> And it's quite simple to fix it, you only need to change
> io_{read,write} in the softmmu_template.h and extend
> io_mem_{read,write} loops in exec.c to 4 elements, taking care that
> io_mem_{read,write}[3] can pass uint64_t.
>
prev parent reply other threads:[~2011-10-12 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 10:34 [Qemu-devel] PCI 64-bit BAR access with qemu Francois WELLENREITER
2011-10-12 11:00 ` Max Filippov
2011-10-12 12:01 ` Francois WELLENREITER [this message]
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=4E95818F.5050101@bull.net \
--to=francois.wellenreiter@bull.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.