From: Stefan Weil <sw@weilnetz.de>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Andreas Färber" <afaerber@suse.de>,
"Aurélien Jarno" <aurelien@aurel32.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-1.6] target-mips: do not raise exceptions when accessing invalid memory
Date: Mon, 29 Jul 2013 22:35:31 +0200 [thread overview]
Message-ID: <51F6D213.8040506@weilnetz.de> (raw)
In-Reply-To: <51F4345D.6080007@weilnetz.de>
Am 27.07.2013 22:58, schrieb Stefan Weil:
> Am 27.07.2013 22:43, schrieb Andreas Färber:
>> Am 27.07.2013 21:37, schrieb Stefan Weil:
>>> Am 27.07.2013 19:43, schrieb Peter Maydell:
>>>> On 27 July 2013 17:18, Hervé Poussineau <hpoussin@reactos.org> wrote:
>>>>> Another solution would be to add a big dummy memory regions on all MIPS boards
>>>>> to catch memory accesses and not raise an exception. However, this means that
>>>>> each MIPS board will have its own unassigned memory handler, different from the
>>>>> global QEMU one.
>>>> Better would be to at least provide fake RAZ/WI implementations of
>>>> devices for the boards, rather than making the dummy region cover
>>>> the whole of the address space. Not 1.6 material, though.
For MIPS Malta, Linux boot can be fixed by handling read access for two
addresses:
0x1fbf8008
0x1bc80110
The corresponding definitions in the Linux kernel code seem to be these
lines:
#define GCMP_BASE_ADDR 0x1fbf8000
#define GCMP_ADDRSPACE_SZ (256 * 1024)
#define GCMP_GCB_GCMPB_OFS 0x0008 /* Global GCMP
Base */
#define MSC01_BIU_REG_BASE 0x1bc80000
#define MSC01_BIU_ADDRSPACE_SZ (256 * 1024)
#define MSC01_SC_CFG_OFS 0x0110
=> mips_malta.c needs a handler for reads of
(GCMP_BASE_ADDR + GCMP_GCB_GCMPB_OFS) and
(MSC01_BIU_REG_BASE + MSC01_SC_CFG_OFS).
Regards,
Stefan W.
next prev parent reply other threads:[~2013-07-29 20:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 16:18 [Qemu-devel] [PATCH for-1.6] target-mips: do not raise exceptions when accessing invalid memory Hervé Poussineau
2013-07-27 16:49 ` Andreas Färber
2013-07-27 17:43 ` Peter Maydell
2013-07-27 19:37 ` Stefan Weil
2013-07-27 20:43 ` Andreas Färber
2013-07-27 20:57 ` Peter Maydell
2013-07-27 20:58 ` Stefan Weil
2013-07-29 20:35 ` Stefan Weil [this message]
2013-08-04 22:04 ` Aurélien Jarno
2013-08-04 22:37 ` Peter Maydell
2013-08-05 5:19 ` Stefan Weil
2013-08-05 12:27 ` Aurélien Jarno
2013-08-05 8:45 ` Andreas Färber
2013-08-05 8:47 ` Jan Kiszka
2013-08-05 13:31 ` Aurélien Jarno
2013-08-05 13:45 ` Andreas Färber
2013-08-05 13:53 ` Hervé Poussineau
2013-08-05 14:07 ` Aurélien Jarno
2013-08-05 14:15 ` 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=51F6D213.8040506@weilnetz.de \
--to=sw@weilnetz.de \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=hpoussin@reactos.org \
--cc=peter.maydell@linaro.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 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.