From: "Aurélien Jarno" <aurelien@aurel32.net>
To: "Andreas Färber" <afaerber@suse.de>
Cc: "Stefan Weil" <sw@weilnetz.de>,
"Hervé Poussineau" <hpoussin@reactos.org>,
qemu-devel@nongnu.org, "Jan Kiszka" <jan.kiszka@siemens.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for-1.6] target-mips: do not raise exceptions when accessing invalid memory
Date: Mon, 5 Aug 2013 15:31:50 +0200 [thread overview]
Message-ID: <20130805133150.GE4193@ohm.aurel32.net> (raw)
In-Reply-To: <51FF662B.7080706@suse.de>
On Mon, Aug 05, 2013 at 10:45:31AM +0200, Andreas Färber wrote:
> Am 05.08.2013 00:04, schrieb Aurélien Jarno:
> > On Mon, Jul 29, 2013 at 10:35:31PM +0200, Stefan Weil wrote:
> >> 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).
> >
> > I don't think it would be correct to emulate them as this are not
> > present on the real Malta board, at least for the model emulated by
> > QEMU. Theses addresses correspond to the SMP controller, and is
> > therefore only present when an SMP daughter card is installed.
> >
> > The Linux kernel probes theses addresses, and look if they return
> > something consistent. If not the corresponding devices are latter
> > ignored.
> >
> > The real hardware probably returns all 1 or all 0 for addresses not
> > decoded to a device. This is what QEMU should model, and it should
> > not trigger a DBE or IBE exception.
> [snip]
>
> Have you tested Jan's patches limiting the new unassigned read value -1
> to PIO?
>
I have tried this patches, and they don't fix the problem.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2013-08-05 13:32 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
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 [this message]
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=20130805133150.GE4193@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=afaerber@suse.de \
--cc=hpoussin@reactos.org \
--cc=jan.kiszka@siemens.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).