From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: IO_MEM_NB_ENTRIES limit
Date: Sun, 11 May 2008 17:25:18 +0200 [thread overview]
Message-ID: <48270FDE.3040405@bellard.org> (raw)
In-Reply-To: <fb249edb0805110820l6e11d56j5594a412c6e51cc4@mail.gmail.com>
andrzej zaborowski wrote:
> On 15/04/2008, andrzej zaborowski <balrogg@gmail.com> wrote:
>> the maximum number of memory-mapped IO regions in qemu is
>> IO_MEM_NB_ENTRIES which is defined using TARGET_PAGE_BITS. Due to
>> tiny pages available on ARM, IO_MEM_NB_ENTRIES is only 64 there.
>> OMAP2 cpu has many more logical IO regions than 64 and it makes sense
>> to register them as separate.
>>
>> To be able to set IO_MEM_NB_ENTRIES higher, the io region index and
>> the address bits would have to be stored in separate fields in
>> PhysPageDesc and in CPUTLBEntry structs, instead of io index being
>> stored in the lower bits of addresses. This would double the size of
>> both structs. I'd like to hear if there are any other ideas for
>> removing the upper limit for IO_MEM_NB_ENTRIES.
>
> Here's a less hacky patch to store the IO region number in a separate
> field from the page start address, in PhysPageDesc and CPUTLBEntry,
> thus simplifying a couple of things. It's intrusive but will ease any
> further extension and I'd like to commit it some time if there are no
> better ideas. It works in my tests but there may be corner cases that
> I broke.
>
> The maximum number of IO_MEM_ROMD regions is still dependent on page
> size because the API to register these uses the same value to store
> the address and the io_index, so removing this would require api
> change that affects hw/.
> [...]
Does it work with kqemu ? Did you make benchmarks ?
Regards,
Fabrice.
next prev parent reply other threads:[~2008-05-11 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 11:35 [Qemu-devel] IO_MEM_NB_ENTRIES limit andrzej zaborowski
2008-05-11 15:20 ` [Qemu-devel] " andrzej zaborowski
2008-05-11 15:25 ` Fabrice Bellard [this message]
2008-05-11 15:59 ` Fabrice Bellard
2008-05-11 17:18 ` andrzej zaborowski
2008-05-11 17:39 ` Fabrice Bellard
2008-05-11 17:42 ` Fabrice Bellard
2008-05-11 18:45 ` 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=48270FDE.3040405@bellard.org \
--to=fabrice@bellard.org \
--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).