* [Qemu-devel] [Bug 1438144] [NEW] Page sizes are not interpreted correctly for E500/E500MC
@ 2015-03-30 11:21 WGH
2015-04-07 19:22 ` Scott Wood
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: WGH @ 2015-03-30 11:21 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
http://cache.freescale.com/files/32bit/doc/ref_manual/E500CORERM.pdf - see 2.12.5.2 MAS Register 1 (MAS1), p. 2-41
http://cache.freescale.com/files/32bit/doc/ref_manual/E500MCRM.pdf - see 2.16.6.2 MAS Register 1 (MAS1), p. 2-54
According to these documents, variable page size for TLB1 is computed as
4K ** TSIZE.
However, QEMU always treats it as if it was 1K << TSIZE, even if options
like "-cpu e500mc" are supplied to qemu.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1438144
Title:
Page sizes are not interpreted correctly for E500/E500MC
Status in QEMU:
New
Bug description:
http://cache.freescale.com/files/32bit/doc/ref_manual/E500CORERM.pdf - see 2.12.5.2 MAS Register 1 (MAS1), p. 2-41
http://cache.freescale.com/files/32bit/doc/ref_manual/E500MCRM.pdf - see 2.16.6.2 MAS Register 1 (MAS1), p. 2-54
According to these documents, variable page size for TLB1 is computed
as 4K ** TSIZE.
However, QEMU always treats it as if it was 1K << TSIZE, even if
options like "-cpu e500mc" are supplied to qemu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1438144/+subscriptions
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [Bug 1438144] [NEW] Page sizes are not interpreted correctly for E500/E500MC
2015-03-30 11:21 [Qemu-devel] [Bug 1438144] [NEW] Page sizes are not interpreted correctly for E500/E500MC WGH
@ 2015-04-07 19:22 ` Scott Wood
2015-04-07 19:55 ` [Qemu-devel] [Bug 1438144] " Scott Wood
2015-04-14 17:00 ` WGH
2 siblings, 0 replies; 4+ messages in thread
From: Scott Wood @ 2015-04-07 19:22 UTC (permalink / raw)
To: Bug 1438144; +Cc: qemu-devel
On Mon, 2015-03-30 at 11:21 +0000, WGH wrote:
> Public bug reported:
>
> http://cache.freescale.com/files/32bit/doc/ref_manual/E500CORERM.pdf - see 2.12.5.2 MAS Register 1 (MAS1), p. 2-41
> http://cache.freescale.com/files/32bit/doc/ref_manual/E500MCRM.pdf - see 2.16.6.2 MAS Register 1 (MAS1), p. 2-54
>
> According to these documents, variable page size for TLB1 is computed as
> 4K ** TSIZE.
>
> However, QEMU always treats it as if it was 1K << TSIZE, even if options
> like "-cpu e500mc" are supplied to qemu.
MMU v2 (implemented in e6500) extended the TSIZE field so that 1K <<
TSIZE is correct. The extension was on the LSB side so that it works
fine as long as the low bit of the new TSIZE (which is reserved on
e500v2/mc) is zero.
-Scott
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Qemu-devel] [Bug 1438144] Re: Page sizes are not interpreted correctly for E500/E500MC
2015-03-30 11:21 [Qemu-devel] [Bug 1438144] [NEW] Page sizes are not interpreted correctly for E500/E500MC WGH
2015-04-07 19:22 ` Scott Wood
@ 2015-04-07 19:55 ` Scott Wood
2015-04-14 17:00 ` WGH
2 siblings, 0 replies; 4+ messages in thread
From: Scott Wood @ 2015-04-07 19:55 UTC (permalink / raw)
To: qemu-devel
This is not a bug. MMU v2 (implemented in e6500) extended the TSIZE field so that 1K <<
TSIZE is correct. The extension was on the LSB side so that it works
fine as long as the low bit of the new TSIZE (which is reserved on
e500v2/mc) is zero.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1438144
Title:
Page sizes are not interpreted correctly for E500/E500MC
Status in QEMU:
Invalid
Bug description:
http://cache.freescale.com/files/32bit/doc/ref_manual/E500CORERM.pdf - see 2.12.5.2 MAS Register 1 (MAS1), p. 2-41
http://cache.freescale.com/files/32bit/doc/ref_manual/E500MCRM.pdf - see 2.16.6.2 MAS Register 1 (MAS1), p. 2-54
According to these documents, variable page size for TLB1 is computed
as 4K ** TSIZE.
However, QEMU always treats it as if it was 1K << TSIZE, even if
options like "-cpu e500mc" are supplied to qemu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1438144/+subscriptions
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Qemu-devel] [Bug 1438144] Re: Page sizes are not interpreted correctly for E500/E500MC
2015-03-30 11:21 [Qemu-devel] [Bug 1438144] [NEW] Page sizes are not interpreted correctly for E500/E500MC WGH
2015-04-07 19:22 ` Scott Wood
2015-04-07 19:55 ` [Qemu-devel] [Bug 1438144] " Scott Wood
@ 2015-04-14 17:00 ` WGH
2 siblings, 0 replies; 4+ messages in thread
From: WGH @ 2015-04-14 17:00 UTC (permalink / raw)
To: qemu-devel
You're absolutely right. Sorry for bothering.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1438144
Title:
Page sizes are not interpreted correctly for E500/E500MC
Status in QEMU:
Invalid
Bug description:
http://cache.freescale.com/files/32bit/doc/ref_manual/E500CORERM.pdf - see 2.12.5.2 MAS Register 1 (MAS1), p. 2-41
http://cache.freescale.com/files/32bit/doc/ref_manual/E500MCRM.pdf - see 2.16.6.2 MAS Register 1 (MAS1), p. 2-54
According to these documents, variable page size for TLB1 is computed
as 4K ** TSIZE.
However, QEMU always treats it as if it was 1K << TSIZE, even if
options like "-cpu e500mc" are supplied to qemu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1438144/+subscriptions
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-04-14 17:11 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-30 11:21 [Qemu-devel] [Bug 1438144] [NEW] Page sizes are not interpreted correctly for E500/E500MC WGH
2015-04-07 19:22 ` Scott Wood
2015-04-07 19:55 ` [Qemu-devel] [Bug 1438144] " Scott Wood
2015-04-14 17:00 ` WGH
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).